Finance · Remote MCP server
Ziggs
Ziggs delegate MCP: chat, agreements, context, payments via OAuth or operator key.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ZiggsAI/ziggs- Version
- 0.34.1
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- ZiggsAI (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ZiggsAI) · how
- Website
- ziggsai.com/docs#connect-assistant
- Repository
- github.com/ZiggsAI/agentplus
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.ziggsai.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @ziggs-ai/ziggs-mcp | 0.34.1 | stdio |
How to connect Ziggs
Ziggs is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.ziggsai.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @ziggs-ai/ziggs-mcp version 0.34.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @ziggs-ai/ziggs-mcp@0.34.1. It reads the environment variable ZIGGS_OPERATOR_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"ziggs": {
"command": "npx",
"args": [
"-y",
"@ziggs-ai/ziggs-mcp@0.34.1"
],
"env": {
"ZIGGS_OPERATOR_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| Zero Core IntelDrainBrain token safety, CORTEX trading signals, social trends. Zero Core Intel. | Remote & Local · HTTPLive check: ✓ handshake |
| ZERO MCPRead-only MCP inspection for ZERO paper autonomous onchain operations. | Local · stdio |
| ZeroAcquirePrices a small acquisition two ways, least buyer cash or an SBA 7(a) loan, and lists ten structures. | Remote · HTTPLive check: ✓ handshake |
| zFinia IntelligenceMachine-economy newswire and paid changes-since for agents. MCP is challenge-handoff, not a wallet. | Remote · HTTPLive check: ✓ handshake |
| ZippMulti-language crypto news with editorial sentiment + importance scoring; cites original publisher. | Remote · HTTPLive check: ✓ handshake |
| Ziptax Sales Tax APIReal-time US and Canadian sales and use tax rates by address or geo coordinates. | Remote · SSELive check: ✗ no handshake |
| ZkverifyCryptographically verifiable blockchain data with Merkle proofs + ECDSA signing. | Local · stdio |
| Zola MCPZola wedding planning for Claude - vendors, budget, guests, seating, registry, and RSVPs. | Local · stdio |