Collar Guardrail — Pre-Trade Risk Layer MCP Server

by aiguardrail Your server? Claim it

not responding

Collar Guardrail — Pre-Trade Risk Layer is listed as active in the registry but did not answer our last check. It exposes 6 tools. Last commit 6 Oct 2026.

Deterministic pre-trade risk checks for AI agents on Robinhood Chain. Returns allow/warn/deny.

Uptime history 48 days of history · worst day 93%

48 days agonow

98.9%

Uptime 24h

180 of 182 checks

Tools

read from the server

129 ms

Response time

average over 24h

Stars

last commit 6 Oct 2026

What changed 9

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 20 September 2026. No other catalogue keeps this.

25 Oct a tool changed version2 times that day

20 Oct a tool changed version2 times that day

12 Oct a tool description was rewritten check_token_safety

5 Oct a tool changed version2 times that day

20 Sep a tool appeared evaluate_trade_paid

20 Sep a tool description was rewritten evaluate_trade

and 3 more, back to 20 September 2026

Collar Guardrail — Pre-Trade Risk Layer missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

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.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add backend --transport http https://backendai-x4m1.onrender.com/mcp-http/mcp

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "backend": {
      "type": "http",
      "url": "https://backendai-x4m1.onrender.com/mcp-http/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 6

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). For higher limits, use `evaluate_trade_paid` (Tier 2, $25,000) which settles an x402 payment on-chain.

evaluate_trade_paid

Pre-trade risk check gated by an x402 payment. Evaluated as COLR Tier 2: $25,000 notional ceiling, 10/25 per-minute rate limits. No COLR holdings are required — the on-chain payment is the credential. FLOW ---- 1. Call WITHOUT payment_proof → the tool returns a `PaymentRequiredOutput` describing the on-chain payment (network, asset, amount, payTo, resource). 2. Settle the payment on-chain using an x402-capable client. The facilitator returns a proof string. 3. Call again with `payment_proof=<proof>` → the tool forwards the proof to the guardrail's x402-paid endpoint and returns a full `EvaluateTradeOutput` with `tier=2`.

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. Returns a severity classification (safe / warn / danger), the specific risk factors detected, and the result of a simulated sell. When severity=danger, the next `evaluate_trade` for the same contract is automatically denied regardless of any other checks. This is a heuristic bytecode + simulation check, not a formal audit. Use it before trading unknown tokens, memecoins, or any contract that is absent from the official Robinhood Chain registry. It is safe to call repeatedly; no transaction is ever sent.

verify

verify_audit_trail

Verify the tamper-evident audit trail for a wallet's past guardrail decisions.

Endpoints

URL	Transport	State	Latency	Checked
https://backendai-x4m1.onrender.com/mcp-http/mcp	streamable-http	answering	81 ms	9 min ago
https://api.collarguardrail.com/mcp-http/mcp	streamable-http	answering	149 ms	9 min ago

Alternatives to Collar Guardrail — Pre-Trade Risk Layer

same job, measured the same way

Smolabot

by arison8

Deterministic decision guardrail for AI agents and bots. Verifies pre-trade economics (long-only).

1 tools answering

Guardrail MCP

by kadopi

Deterministic preflight checks for credentials, fund transfers, writes, and prompt overrides.

2 tools answering

Mandateguard

by ezequiellich44-cmd

Deterministic payment policy guardrail for AI agents - budgets, allowlists, signed mandates.

local only

PumpPill — token safety and measured outcomes

by pumppill

Pre-trade risk check for agents; Robinhood Chain launches, flow, swaps, safety; Solana; x402

39 tools answering

Hood MCP

by nirholas

Robinhood Chain data + guarded trading for AI agents: Stock Token quotes, portfolios, launches

59 installs/wk local only

Tokyo Futuro

by tokyofuturo

Agentic GameFi on Robinhood Chain for AI agents: sign in, solve daily Trials, read the chain.

93 installs/wk 140 tools answering

Haltproof

by rudrendupaul

Fail-closed deterministic checks and hash-chained receipts for AI agent outputs via MCP.

75 installs/wk local only

Moneo

by moneolabs

A guarded wallet for AI agents on Robinhood Chain: a spending policy runs before every signature.

66 installs/wk local only

Collar Guardrail — Pre-Trade Risk Layer — questions

Answers built from our own checks of this server.

What can Collar Guardrail — Pre-Trade Risk Layer do?

It exposes 6 tools, read directly from the server on our last check. Among them: check_token_safety, evaluate_trade, evaluate_trade_paid, 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 Collar Guardrail — Pre-Trade Risk Layer working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 180 of 182 checks got a reply (98.9%), average response time 129 ms. The bar chart above shows every period we have measured.

The registry lists Collar Guardrail — Pre-Trade Risk Layer as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Collar Guardrail — Pre-Trade Risk Layer?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Collar Guardrail — Pre-Trade Risk Layer need an API key?

No. Collar Guardrail — Pre-Trade Risk Layer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Collar Guardrail — Pre-Trade Risk Layer?

It answers our handshake in 129 ms on average, which is faster than 86% 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.

Is Collar Guardrail — Pre-Trade Risk Layer open source?

The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at backendai-x4m1.onrender.com, which runs on its operator's own terms.