mcp-registry/xyz.scanhood/mcp · v1.0.0
Also listed as glama/cassh100k/scanhood-mcp-server
As of 2026-10-23 18:07 UTC, the Scanhood MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 31 outages in 90 days, with a median recovery of 3 minutes.
On-chain honeypot/rug scanner, market data, and launch tools for Robinhood Chain (EVM 4663).
Claude Code
claude mcp add --transport http scanhood-mcp-server https://scanhood.xyz/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"scanhood-mcp-server": {
"type": "http",
"url": "https://scanhood.xyz/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
22 of 22 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
4 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~2,199 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fxyz.scanhood%2Fmcp/fixes
{
"name": "get_bots_claim_prefs",
"description": "Per-token preferences for automatic trading-fee claiming.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get fee auto-claim preferences"
}{
"name": "get_bots_stats",
"description": "Stats from ScanHood's own arbitrage and fee-claim bots.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get ScanHood bot activity stats"
}{
"name": "get_bridge_quote",
"description": "Read-only quote (no execution) for bridging native ETH/BNB between Robinhood Chain and Ethereum, Base, Arbitrum, or BNB Chain, via relay.link — the same route ScanHood's own Bridge tab uses. No ScanHood fee. Returns amountOut, an ETA in seconds, relay's own fee in USD, and the raw unsigned deposit tx (to/value/data) for the caller's own wallet to sign and send on the fromChain — ScanHood never holds funds or keys.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"fromChain",
"toChain",
"amount"
],
"properties": {
"user": {
"type": "string",
"description": "wallet address that will send the bridge — improves quote accuracy, optional"
},
"amount": {
"type": "string",
"description": "native-token amount to bridge (ETH, or BNB if fromChain is 56), as a decimal string"
},
"toChain": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "destination chain id — same supported set as fromChain, must differ from it"
},
"fromChain": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "source chain id — one of 4663 (Robinhood), 1 (Ethereum), 8453 (Base), 42161 (Arbitrum), 56 (BNB Chain)"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get a cross-chain bridge quote"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/xyz.scanhood/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/xyz.scanhood/mcp"}) over MCP.
build_launch_tx ~463 tokensget_bridge_quote ~342 tokensscan_token ~230 tokenssave_watchlist ~229 tokensset_bots_claim_prefs ~222 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fxyz.scanhood%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fxyz.scanhood%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.scanhood%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.scanhood%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fxyz.scanhood%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6a2c551fafb15d76…, first seen 2026-10-17, included at leaf 231 of 53,615. Version history · verify what your client received.
Compare: most reliable other servers · most reliable finance servers · most reliable data servers · most reliable security servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 18:07 UTC, the Scanhood MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 31 outages in 90 days, with a median recovery of 3 minutes.
Scanhood MCP server advertises 22 tools, including apply_partner_key, build_launch_tx, get_bots_claim_prefs, get_bots_stats, get_bridge_quote.
Point your MCP client at this streamable-http endpoint: https://scanhood.xyz/mcp
Glimind scanned all 22 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.