Remote MCP · Endpoint

sipi.bot — Spend Firewall for AI Agents MCP server

No. sipi.bot — Spend Firewall for AI Agents answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://sipi.bot/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.kindrat86/sipi-bot-spend-firewall
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
38 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Pre-spend firewall for AI agents. Approves, blocks, flags transactions against policy rules.
Listing
From the official MCP registry (active).
Recent checks of sipi.bot — Spend Firewall for AI Agents
CheckedResultHandshake
1 hour agoHandshake completed38 ms
1 day agoHandshake completed35 ms
2 days agoHandshake completed160 ms
3 days agoHandshake completed40 ms
4 days agoHandshake completed37 ms
5 days agoHandshake completed34 ms
6 days agoHandshake completed43 ms
9 days agoHandshake completed31 ms
11 days agoHandshake completed32 ms
14 days agoHandshake completed33 ms
16 days agoHandshake completed31 ms
18 days agoHandshake completed42 ms
20 days agoHandshake completed37 ms
22 days agoHandshake completed48 ms
24 days agoHandshake completed50 ms
26 days agoHandshake completed32 ms
27 days agoHandshake completed46 ms
29 days agoHandshake completed33 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with sipi.bot — Spend Firewall for AI Agents and makes no claim about it beyond what these checks measured.