sipi.bot — Spend Firewall for AI Agents
REMOTE · SIPI.BOT · SCANNED SEP 20
Pre-spend firewall for AI agents. Approves, blocks, flags transactions against policy rules.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 138 tokens (~46/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the sipi.bot — Spend Firewall for AI Agents MCP server?
sipi.bot — Spend Firewall for AI Agents is a hosted endpoint at https://sipi.bot/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sipi.bot
claude mcp add --transport http kindrat86-sipi-bot-spend-firewall 'https://sipi.bot/api/mcp'
{
"mcpServers": {
"kindrat86-sipi-bot-spend-firewall": {
"url": "https://sipi.bot/api/mcp"
}
}
} {
"servers": {
"kindrat86-sipi-bot-spend-firewall": {
"type": "http",
"url": "https://sipi.bot/api/mcp"
}
}
} [mcp_servers.kindrat86-sipi-bot-spend-firewall] url = "https://sipi.bot/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kindrat86-sipi-bot-spend-firewall": {
"type": "remote",
"url": "https://sipi.bot/api/mcp",
"enabled": true
}
}
} openclaw mcp add kindrat86-sipi-bot-spend-firewall --url 'https://sipi.bot/api/mcp' --transport streamable-http
mcp_servers:
kindrat86-sipi-bot-spend-firewall:
url: "https://sipi.bot/api/mcp" {
"McpServers": {
"kindrat86-sipi-bot-spend-firewall": {
"Transport": "http",
"Url": "https://sipi.bot/api/mcp"
}
}
} assistant mcp add kindrat86-sipi-bot-spend-firewall -t streamable-http -u 'https://sipi.bot/api/mcp'
{
"mcpServers": {
"kindrat86-sipi-bot-spend-firewall": {
"type": "http",
"url": "https://sipi.bot/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://sipi.bot/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sipi.bot | CN=YE1,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 665baff997e28e375593d168c843175e0f3 |
| SANs: sipi.bot | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sipi.bot. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| bot. | present | 58741 | 8 | Verified |
| sipi.bot. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sipi.bot/api/mcp | Verified | 200 | |
| http (plaintext) | http://sipi.bot/api/mcp | HTTPS enforced | 301 | https://sipi.bot/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_spend_rule ~58
Add a rule to the authenticated API key's isolated workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| label | string | – | – |
| params | object | yes | – |
| priority | integer | – | – |
| rule_type | string | yes | – |
No output schema declared.
No examples provided.
evaluate_spend ~62
Check whether an autonomous agent is allowed to make a purchase BEFORE spending. Returns APPROVED, BLOCKED, or FLAGGED.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| category | string | – | – |
| description | string | – | – |
| merchant | string | – | – |
No output schema declared.
No examples provided.
firewall_status ~18
Get private firewall stats for the authenticated API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the sipi.bot — Spend Firewall for AI Agents MCP server?
sipi.bot — Spend Firewall for AI Agents is an MCP server listed in the public MCP registry as io.github.kindrat86/sipi-bot-spend-firewall. Pre-spend firewall for AI agents. Approves, blocks, flags transactions against policy rules. This page covers its hosted endpoint (https://sipi.bot/api/mcp).
Is the sipi.bot — Spend Firewall for AI Agents MCP server safe to use?
sipi.bot — Spend Firewall for AI Agents scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the sipi.bot — Spend Firewall for AI Agents MCP server expose?
sipi.bot — Spend Firewall for AI Agents exposes 3 tools: evaluate_spend, add_spend_rule, firewall_status. Their descriptions and schemas cost roughly 138 tokens of context every time the server is loaded.
Does the sipi.bot — Spend Firewall for AI Agents MCP server require authentication?
No. We connected to sipi.bot — Spend Firewall for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the sipi.bot — Spend Firewall for AI Agents MCP server still maintained?
sipi.bot — Spend Firewall for AI Agents is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.