Skip to main content
Glama

Server Details

Ziggs delegate MCP: chat, agreements, context, payments via OAuth or operator key.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over 64 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    A generic MCP and REST payments gateway enabling agents and services to accept payments via x402 USDC and XMR/ZEC top-ups, and make outbound ZEC payments with human co-signing, all without holding spending keys.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables MCP-capable clients to act as a Salt agent identity to discover and create agents, delegate or consult, chat with humans, post interactive cards, sell products, send invoices, meter usage, manage wallets, and transact on the Salt network via local stdio credentials or hosted OAuth keyless access.
    10 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables MCP clients to connect once to self-hosted, user-owned upstream accounts and then discover and invoke granted tools through a single authenticated endpoint. Each client receives its own key with deny-by-default tool grants, while sensitive calls require durable human approval and credentials stay encrypted and never forwarded upstream.
    Apache 2.0
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources