ai.firmbrain/x402-services
REMOTE · X402-SERVICES-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 24
The only x402 MCP server for Robinhood Chain (chainId 4663) - 147 onchain, trading & AI tools.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 159 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 16304 tokens (~102/item across 159 items; 159 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pubsub_publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 159 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 ai.firmbrain/x402-services MCP server?
ai.firmbrain/x402-services is a hosted endpoint at https://x402-services-production.up.railway.app/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 · x402-services-production.up.railway.app
claude mcp add --transport http ai-firmbrain-x402-services 'https://x402-services-production.up.railway.app/mcp'
{
"mcpServers": {
"ai-firmbrain-x402-services": {
"url": "https://x402-services-production.up.railway.app/mcp"
}
}
} {
"servers": {
"ai-firmbrain-x402-services": {
"type": "http",
"url": "https://x402-services-production.up.railway.app/mcp"
}
}
} [mcp_servers.ai-firmbrain-x402-services] url = "https://x402-services-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-firmbrain-x402-services": {
"type": "remote",
"url": "https://x402-services-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add ai-firmbrain-x402-services --url 'https://x402-services-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
ai-firmbrain-x402-services:
url: "https://x402-services-production.up.railway.app/mcp" {
"McpServers": {
"ai-firmbrain-x402-services": {
"Transport": "http",
"Url": "https://x402-services-production.up.railway.app/mcp"
}
}
} assistant mcp add ai-firmbrain-x402-services -t streamable-http -u 'https://x402-services-production.up.railway.app/mcp'
{
"mcpServers": {
"ai-firmbrain-x402-services": {
"type": "http",
"url": "https://x402-services-production.up.railway.app/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.
- 26 Aug 26 78
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 24 Sept 2026 · Probed https://x402-services-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402-services-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | 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://x402-services-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://x402-services-production.up.railway.app/mcp | HTTPS enforced | 301 | https://x402-services-production.up.railway.app/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 →
ton_dns ~63
Resolve a .ton DNS name to its wallet address + expiry. Send { domain } e.g. foundation.ton. [x402 paid tool — price $0.002; POST /api/ton/dns]
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A .ton domain |
No output schema declared.
No examples provided.
ton_gram ~70
GRAM/TON network snapshot: GRAM price + USD₮-on-TON stablecoin footprint (holders, supply) — the size of the 1B-user Telegram economy. Send {}. [x402 paid tool — price $0.002; POST /api/ton/gram]
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ton_jetton ~75
TON jetton master intelligence (defaults USD₮): supply, holders, decimals, mintability, admin. Send { jetton? }. [x402 paid tool — price $0.002; POST /api/ton/jetton]
| Name | Type | Req | Description |
|---|---|---|---|
| jetton | string | – | Jetton master (default USD₮) |
No output schema declared.
No examples provided.
ton_jetton_holders ~92
Top holders of a TON jetton (default USD₮): concentration signal for the Telegram economy. Send { jetton?, limit? }. [x402 paid tool — price $0.005; POST /api/ton/jetton-holders]
| Name | Type | Req | Description |
|---|---|---|---|
| jetton | string | – | Jetton master (default USD₮) |
| limit | number | – | Max holders 1-50 |
No output schema declared.
No examples provided.
ton_nfts ~75
NFTs held by a TON address — includes Telegram usernames & anonymous numbers traded onchain. Send { address, limit? }. [x402 paid tool — price $0.005; POST /api/ton/nfts]
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | TON address |
| limit | number | – | Max items 1-50 |
No output schema declared.
No examples provided.
ton_price ~68
TON/GRAM and jetton spot prices in USD with 24h change. Send { tokens? } (default ton). [x402 paid tool — price $0.001; POST /api/ton/price]
| Name | Type | Req | Description |
|---|---|---|---|
| tokens | string | – | Comma tokens/addresses (default ton) |
No output schema declared.
No examples provided.
ton_transfers ~72
Recent activity/transfers for a TON address (events + action types). Send { address, limit? }. [x402 paid tool — price $0.005; POST /api/ton/transfers]
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | TON address |
| limit | number | – | Max events 1-50 |
No output schema declared.
No examples provided.
ton_tx ~57
TON transaction status by hash: success, exit code, fees, account. Send { hash }. [x402 paid tool — price $0.005; POST /api/ton/tx]
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | TON transaction hash |
No output schema declared.
No examples provided.
wallet_reputation ~69
Wallet reputation: objective on-chain trust signals for an EVM address (vet a counterparty before dealing). Send { address }. [x402 paid tool — price $0.003; POST /api/wallet/reputation]
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x EVM address to score |
No output schema declared.
No examples provided.
What is the ai.firmbrain/x402-services MCP server?
ai.firmbrain/x402-services is an MCP server listed in the public MCP registry as ai.firmbrain/x402-services. The only x402 MCP server for Robinhood Chain (chainId 4663) - 147 onchain, trading & AI tools. This page covers its hosted endpoint (https://x402-services-production.up.railway.app/mcp).
Is the ai.firmbrain/x402-services MCP server safe to use?
ai.firmbrain/x402-services scores 78 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 ai.firmbrain/x402-services MCP server expose?
ai.firmbrain/x402-services exposes 159 tools: markdown, extract, read, read_structured, memory_set, and 154 more. Their descriptions and schemas cost roughly 16,304 tokens of context every time the server is loaded.
Does the ai.firmbrain/x402-services MCP server require authentication?
No. We connected to ai.firmbrain/x402-services without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.firmbrain/x402-services MCP server still maintained?
ai.firmbrain/x402-services is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.