mcpbeat Sign in

Backend MCP Server

by aiguardrail Your server? Claim it
answering

Backend is answering right now. Last checked 4 min ago. It exposes 5 tools.

Deterministic pre-trade risk checks for autonomous AI trading agents.

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
92 of 92 checks
5
Tools
read from the server
139 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Backend every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add backend --transport http https://backendai-x4m1.onrender.com/mcp-http/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "backend": {
      "url": "https://backendai-x4m1.onrender.com/mcp-http/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.backend]
url = "https://backendai-x4m1.onrender.com/mcp-http/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "backend": {
      "url": "https://backendai-x4m1.onrender.com/mcp-http/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "backend": {
      "url": "https://backendai-x4m1.onrender.com/mcp-http/mcp"
    }
  }
}

Available tools 5

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

evaluate
evaluate_trade
Pre-trade risk check for a proposed trade. Call this BEFORE executing any trade and treat a "deny" decision as a hard stop. Evaluated at a fixed Tier 1 ceiling ($5,000 notional) — MCP callers do not get COLR tier gating. For higher tiers, use the REST API with wallet-signature authentication.
simulate
simulate_balance
Simulate a wallet's ERC-20 balance after a hypothetical trade using eth_call state override. Read-only: no transaction is ever sent.
supported
get_supported_assets
List every asset in the guardrail's official Robinhood Chain registry, with its canonical contract address.
token
check_token_safety
Honeypot / contract safety check for any ERC-20 token.
verify
verify_audit_trail
Verify the tamper-evident audit trail for a wallet's past guardrail decisions.

Endpoints

URLTransportStateLatencyChecked
https://backendai-x4m1.onrender.com/mcp-http/mcp streamable-http answering 159 ms 4 min ago

Alternatives to Backend

same job, measured the same way
Decker
by gigshow

Deterministic market-state engine for trading agents — state, gate, coordinates, with receipts.

12 tools answering
TrustRail Counterparty Risk
by nicolanegro02nn-sketch

External counterparty-risk checks and signed receipts for autonomous agents and machine payments.

answering
TrustRail Counterparty Risk
by trustrail-labs

External counterparty-risk checks and signed receipts for autonomous agents and machine payments.

answering
QuantContext
by zomma-dev

Deterministic stock screening, backtesting, and factor analysis for AI trading agents

75 installs/wk local only
DJZS Trust MCP
by djzs

Deterministic pre-execution audit for trading agents. PASS/WAIT/FAIL, reproducible verdict_hash.

4 tools answering
Agentrisk
by trycoin-ai

Risk guardrails for AI trading agents. Your agent proposes; your policy decides.

88 installs/wk local only
Autotrade — Autonomous Trading Agents
by bitcoinsllm

Deploy autonomous LLM trading agents and drive them over MCP.

6 tools answering
RCQ Data Oracle
by rcqsignals

Signed BTC and macro market intelligence for autonomous research, risk, and trading agents.

7 tools answering

Backend — questions

Answers built from our own checks of this server.

What can Backend do?
It exposes 5 tools, read directly from the server on our last check. Among them: check_token_safety, evaluate_trade, get_supported_assets, simulate_balance, verify_audit_trail. 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 Backend working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 139 ms. The bar chart above shows every period we have measured.
How do I connect Backend?
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 Backend need an API key?
No. Backend completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Backend?
It answers our handshake in 139 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.