Security & Testing
sipi.bot
Manages spend policies and rules for autonomous agents to approve or block purchases.
ENDPOINT 1
https://sipi.bot/api/mcp
MCP server metadata
- Name
- sipibot-mcp
- Version
- 1.0.0
Known tools 3
evaluate_spendCheck whether an autonomous agent is allowed to make a purchase BEFORE spending.
Potential side effectsfirewall_statusGet current firewall stats: spend approved/blocked today, pending approvals, active agents.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.sipibot-mcp]
url = "https://sipi.bot/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"sipibot-mcp": {
"type": "http",
"url": "https://sipi.bot/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: sipibot-mcp
Remote MCP URL: https://sipi.bot/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"sipibot-mcp": {
"url": "https://sipi.bot/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"sipibot-mcp": {
"type": "http",
"url": "https://sipi.bot/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "sipibot-mcp",
"transport": "streamable-http",
"url": "https://sipi.bot/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.