io.github.aiguardrail/backend
REMOTE · API.COLLARGUARDRAIL.COM · SCANNED SEP 20
Deterministic pre-trade risk checks for autonomous AI trading agents.
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 459 tokens (~91/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.aiguardrail/backend MCP server?
io.github.aiguardrail/backend is a hosted endpoint at https://api.collarguardrail.com/mcp-http/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 · api.collarguardrail.com
claude mcp add --transport http aiguardrail-backend 'https://api.collarguardrail.com/mcp-http/mcp'
{
"mcpServers": {
"aiguardrail-backend": {
"url": "https://api.collarguardrail.com/mcp-http/mcp"
}
}
} {
"servers": {
"aiguardrail-backend": {
"type": "http",
"url": "https://api.collarguardrail.com/mcp-http/mcp"
}
}
} [mcp_servers.aiguardrail-backend] url = "https://api.collarguardrail.com/mcp-http/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aiguardrail-backend": {
"type": "remote",
"url": "https://api.collarguardrail.com/mcp-http/mcp",
"enabled": true
}
}
} openclaw mcp add aiguardrail-backend --url 'https://api.collarguardrail.com/mcp-http/mcp' --transport streamable-http
mcp_servers:
aiguardrail-backend:
url: "https://api.collarguardrail.com/mcp-http/mcp" {
"McpServers": {
"aiguardrail-backend": {
"Transport": "http",
"Url": "https://api.collarguardrail.com/mcp-http/mcp"
}
}
} assistant mcp add aiguardrail-backend -t streamable-http -u 'https://api.collarguardrail.com/mcp-http/mcp'
{
"mcpServers": {
"aiguardrail-backend": {
"type": "http",
"url": "https://api.collarguardrail.com/mcp-http/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
- Stability: unverified → 0.03 ▲ functional
- 19 Sept 26 72
First indexed and scored.
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://api.collarguardrail.com/mcp-http/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.collarguardrail.com | CN=WE1,O=Google Trust Services,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 163a1d13ebcba140135be8d0b1b84525 |
| SANs: api.collarguardrail.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.collarguardrail.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| collarguardrail.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.collarguardrail.com/mcp-http/mcp | Verified | 200 | |
| http (plaintext) | http://api.collarguardrail.com/mcp-http/mcp | HTTPS enforced | 301 | https://api.collarguardrail.com/mcp-http/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 →
check_token_safety Check Token Safety ~39
Honeypot / contract safety check for any ERC-20 token.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_address | string | yes | Token contract address (0x...). |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | If present, the check failed. Do not assume 'safe'. |
| risk_factors | array | – | Specific issues detected. |
| sell_simulation_ok | – | – | Whether a simulated sell succeeded. |
| severity | string | yes | Overall classification. |
No examples provided.
evaluate_trade Evaluate Trade ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Quantity in token units — NOT a pre-computed USD value. |
| asset | string | yes | Asset symbol, e.g. NVDA, AAPL, TSLA, USDG. |
| contract_address | string | yes | Token contract address (0x...). Must match the official registry address for that symbol, or the trade is denied as a suspected fake token. |
| max_slippage_bps | integer | – | Max slippage in basis points (default 100). |
| request_id | – | – | Optional idempotency key. |
| side | string | yes | "buy" or "sell". |
| wallet | string | yes | EVM wallet address (0x...) the trade would execute from. |
| Name | Type | Req | Description |
|---|---|---|---|
| audit_hash | – | – | SHA-256 hash chaining this decision. |
| audit_seq | – | – | Monotonic sequence number of this decision. |
| calculated_notional_usd | number | yes | USD value of the proposed trade. |
| decision | string | yes | Final verdict. 'deny' is a hard stop. |
| error | – | – | If present, no verdict was produced. Treat as a hard stop; do not execute the trade. |
| max_trade_usd | number | yes | USD ceiling for this tier. |
| price_source | string | yes | Where the price came from. |
| price_usd | number | yes | Asset price used for the valuation. |
| reasons | array | yes | Human-readable reasons. Entries prefixed with 'ADVISORY:' are non-blocking context; all other entries drove the decision. |
| request_id | – | – | Echoed idempotency key, if provided. |
| risk_score | integer | yes | Composite risk score from 0 (safe) to 100 (blocked). |
| tier | integer | yes | Tier the wallet was evaluated at (1-3). |
No examples provided.
get_supported_assets Get Supported Assets ~29
List every asset in the guardrail's official Robinhood Chain registry, with its canonical contract address.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | – | Registered assets. |
| error | – | – | If present, the registry was unreachable. |
No examples provided.
simulate_balance Simulate Balance ~97
Simulate a wallet's ERC-20 balance after a hypothetical trade using eth_call state override. Read-only: no transaction is ever sent.
| Name | Type | Req | Description |
|---|---|---|---|
| decimals | integer | – | Token decimals (default 18). |
| delta | number | yes | Signed amount (negative = spend). |
| holder | string | yes | Wallet address whose balance is simulated (0x...). |
| token_address | string | yes | ERC-20 contract address (0x...). |
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | Balance after. |
| before | – | – | Balance before. |
| delta | – | – | Signed change. |
| error | – | – | If present, the simulation failed. |
No examples provided.
verify_audit_trail Verify Audit Trail ~68
Verify the tamper-evident audit trail for a wallet's past guardrail decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many recent records to verify (1-1000, default 100). |
| wallet | string | yes | EVM wallet address (0x...). |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | If present, verification could not run. |
| first_broken_seq | – | – | Sequence number of the first broken link, if any. |
| healthy | boolean | yes | True only if every record's hash matches and the chain is unbroken. |
| records_checked | integer | – | Number of records verified. |
No examples provided.
What is the io.github.aiguardrail/backend MCP server?
io.github.aiguardrail/backend is an MCP server listed in the public MCP registry as io.github.aiguardrail/backend. Deterministic pre-trade risk checks for autonomous AI trading agents. This page covers its hosted endpoint (https://api.collarguardrail.com/mcp-http/mcp).
Is the io.github.aiguardrail/backend MCP server safe to use?
io.github.aiguardrail/backend 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 io.github.aiguardrail/backend MCP server expose?
io.github.aiguardrail/backend exposes 5 tools: evaluate_trade, check_token_safety, simulate_balance, get_supported_assets, verify_audit_trail. Their descriptions and schemas cost roughly 459 tokens of context every time the server is loaded.
Does the io.github.aiguardrail/backend MCP server require authentication?
No. We connected to io.github.aiguardrail/backend without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.aiguardrail/backend MCP server still maintained?
io.github.aiguardrail/backend 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.