mcpbeat

sipi.bot — Spend Firewall for AI Agents MCP Server

io.github.kindrat86/sipi-bot-spend-firewall
answering

sipi.bot — Spend Firewall for AI Agents is answering right now. Last checked 9 min ago. It exposes 3 tools.

Pre-spend firewall for AI agents. Approves, blocks, flags transactions against policy rules.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
300 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add sipi-bot-spend-firewall --transport http https://sipi.bot/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "sipi-bot-spend-firewall": {
      "url": "https://sipi.bot/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.sipi-bot-spend-firewall]
url = "https://sipi.bot/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sipi-bot-spend-firewall": {
      "url": "https://sipi.bot/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "sipi-bot-spend-firewall": {
      "url": "https://sipi.bot/api/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

evaluate
evaluate_spend
Check whether an autonomous agent is allowed to make a purchase BEFORE spending. Returns APPROVED, BLOCKED, or FLAGGED.
firewall
firewall_status
Get private firewall stats for the authenticated API key.
spend
add_spend_rule
Add a rule to the authenticated API key's isolated workspace.

Endpoints

URLTransportStateLatencyChecked
https://sipi.bot/api/mcp streamable-http answering 300 ms 9 min ago

sipi.bot — Spend Firewall for AI Agents — questions

Answers built from our own checks of this server.

What can sipi.bot — Spend Firewall for AI Agents do?
It exposes 3 tools, read directly from the server on our last check. Among them: add_spend_rule, evaluate_spend, firewall_status. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is sipi.bot — Spend Firewall for AI Agents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 300 ms. The bar chart above shows every period we have measured.
How do I connect sipi.bot — Spend Firewall for AI Agents?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does sipi.bot — Spend Firewall for AI Agents need an API key?
No. sipi.bot — Spend Firewall for AI Agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is sipi.bot — Spend Firewall for AI Agents?
It answers our handshake in 300 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.