SatGate – Economic Firewall for AI Agents
by SatGate-ioio.github.SatGate-io/satgatev0.5.0
Budget, payment and audit controls for AI agent API calls and MCP tool calls.
- Remote endpoint
- No known advisories
- MIT
Uptime
Checked · every hour
100%from 5 days of checks
Up without downtime on 5 of 5 days with data.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
How far each check got
- Reached the address 100%
- Completed the handshake 0.0%
- Listed its tools 0.0%
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 3 Nov (today) | No downtime | 19of 19 | – |
| 2 Nov | No downtime | 24of 24 | – |
| 1 Nov | No downtime | 24of 24 | – |
| 31 Oct | No downtime | 24of 24 | – |
| 30 Oct | No downtime | 3of 2 | – |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://satgate-mcp-saas.fly.dev/sse This server needs a header that the connector form cannot set; use Claude Code, Cursor or VS Code for it.
Run in a terminal:
claude mcp add --transport sse satgate https://satgate-mcp-saas.fly.dev/sse --header 'Authorization: YOUR_AUTHORIZATION' Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"satgate": {
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"satgate": {
"type": "sse",
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"satgate": {
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
{
"mcpServers": {
"satgate": {
"type": "sse",
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "satgate"
type: sse
url: "https://satgate-mcp-saas.fly.dev/sse" This server needs a header, and Continue's documentation shows no way to send one to a remote server; use another client for it.
Add to ~/.config/goose/config.yaml:
extensions:
"satgate":
type: streamable_http
name: "satgate"
enabled: true
uri: "https://satgate-mcp-saas.fly.dev/sse"
headers: { "Authorization": "YOUR_AUTHORIZATION" }
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.codex/config.toml:
[mcp_servers.satgate]
url = "https://satgate-mcp-saas.fly.dev/sse"
http_headers = { "Authorization" = "YOUR_AUTHORIZATION" } This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"satgate": {
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"satgate": {
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"satgate": {
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
} Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"satgate": {
"type": "sse",
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
} This server needs a header, and Augment Code's documentation shows no way to send one to a remote server; use another client for it.
Replace YOUR_AUTHORIZATION with your own value.
For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server SatGate – Economic Firewall for AI Agents (`io.github.SatGate-io/satgate`)
Its page: https://plug.directory/servers/io.github.SatGate-io/satgate
It runs on the publisher's servers; the client connects to its URL.
Ask the person for `YOUR_AUTHORIZATION` and put it in place of the placeholder; never invent a value.
Use the section for the person's client.
## Claude Desktop
This server needs a header that the connector form cannot set; use Claude Code, Cursor or VS Code for it.
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse satgate https://satgate-mcp-saas.fly.dev/sse --header 'Authorization: YOUR_AUTHORIZATION'
```
## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
```json
{
"mcpServers": {
"satgate": {
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"satgate": {
"type": "sse",
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
}
```
## Zed
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Cline, AnythingLLM
Merge into the place for the person's client:
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
```json
{
"mcpServers": {
"satgate": {
"type": "sse",
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
}
```
## Continue
This server needs a header, and Continue's documentation shows no way to send one to a remote server; use another client for it.
## Goose
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Codex
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"satgate": {
"url": "https://satgate-mcp-saas.fly.dev/sse",
"headers": { "Authorization": "YOUR_AUTHORIZATION" }
}
}
}
```
## Augment Code
This server needs a header, and Augment Code's documentation shows no way to send one to a remote server; use another client for it.
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
Known advisories
None known for its packages.
Checked 2026-10-28 against OSV.dev and deps.dev.
From the publisher's entry in the Official MCP Registry (the registry entry)and from npm. Report a problem