Finance · Remote MCP server
SatGate - Economic Firewall for AI Agents
Budget, payment and audit controls for AI agent API calls and MCP tool calls.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.SatGate-io/satgate- Version
- 0.5.0
- Status
- Active
- Category
- finance
- Transport
- SSE (HTTP + Server-Sent Events), stdio (local process)
- Package
- npm
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- SatGate-io (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/SatGate-io) · how
- Website
- satgate.io
- Repository
- github.com/SatGate-io/satgate
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| SSE (HTTP + Server-Sent Events) | https://satgate-mcp-saas.fly.dev/sse | Authorization (required, secret) |
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 200)
- SSE stream
- Opened and named its message endpoint (not used further)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | satgate-mcp-bridge | 1.0.5 | stdio |
How to connect SatGate - Economic Firewall for AI Agents
SatGate - Economic Firewall for AI Agents is a remote MCP server reached over the older SSE transport, at https://satgate-mcp-saas.fly.dev/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: satgate-mcp-bridge version 1.0.5. 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 satgate-mcp-bridge@1.0.5. It reads these environment variables: SATGATE_URL (required) and SATGATE_TOKEN (required, secret); set them 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": {
"satgate": {
"command": "npx",
"args": [
"-y",
"satgate-mcp-bridge@1.0.5"
],
"env": {
"SATGATE_URL": "<value>",
"SATGATE_TOKEN": "<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 |
|---|---|
| SantimentCrypto market intelligence: social sentiment, on-chain, trending narratives & analyst insights. | Remote · HTTPLive check: ✓ handshake |
| santyvv-data - market & on-chain dataMarket and on-chain crypto data for AI agents. Pay per call in USDC on Base (x402). | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| SAP MCP ServerSolana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Sarb ZaSouth African Reserve Bank (SARB) Web API MCP. Keyless. | Remote · HTTPLive check: ✓ handshake |
| Sati GrumpyMCP commerce surface for refurbished datacenter hardware, with x402 agent-payment discovery. | Remote · HTTPLive check: ✓ handshake |
| Sato Hub: Onchain AgentsSearch scored onchain-agent tooling: frameworks, MCP servers, wallets, x402 rails, deploy specs. | Remote · HTTPLive check: ✓ handshake |
| Sato KitPrepare -> execute for onchain agent actions: policy pre-flight, simulation, receipt log. | Local · stdio |
| SatoshiAPI - Bitcoin Intelligence via LightningBitcoin intelligence API. Pay per call via L402 Lightning (10-200 sats). No accounts needed. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |