io.github.geekmarine/mcp-defi-router
REMOTE · MCP-DEFI.DATASNAG.COM · SCANNED SEP 25
Autonomous Web3 router for DEX liquidity depth, EVM contract security, and cross-chain bridges.
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 Security49
- 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 3 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 163 tokens (~54/item across 3 items; 3 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.geekmarine/mcp-defi-router server?
io.github.geekmarine/mcp-defi-router is a hosted endpoint at https://mcp-defi.datasnag.com/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 · mcp-defi.datasnag.com
claude mcp add --transport http geekmarine-mcp-defi-router 'https://mcp-defi.datasnag.com/mcp'
{
"mcpServers": {
"geekmarine-mcp-defi-router": {
"url": "https://mcp-defi.datasnag.com/mcp"
}
}
} {
"servers": {
"geekmarine-mcp-defi-router": {
"type": "http",
"url": "https://mcp-defi.datasnag.com/mcp"
}
}
} [mcp_servers.geekmarine-mcp-defi-router] url = "https://mcp-defi.datasnag.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"geekmarine-mcp-defi-router": {
"type": "remote",
"url": "https://mcp-defi.datasnag.com/mcp",
"enabled": true
}
}
} openclaw mcp add geekmarine-mcp-defi-router --url 'https://mcp-defi.datasnag.com/mcp' --transport streamable-http
mcp_servers:
geekmarine-mcp-defi-router:
url: "https://mcp-defi.datasnag.com/mcp" {
"McpServers": {
"geekmarine-mcp-defi-router": {
"Transport": "http",
"Url": "https://mcp-defi.datasnag.com/mcp"
}
}
} assistant mcp add geekmarine-mcp-defi-router -t streamable-http -u 'https://mcp-defi.datasnag.com/mcp'
{
"mcpServers": {
"geekmarine-mcp-defi-router": {
"type": "http",
"url": "https://mcp-defi.datasnag.com/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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 54
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 25 Sept 2026 · Probed https://mcp-defi.datasnag.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=datasnag.com | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | aab95d0721fd99750eaa383b4df30fcf |
| SANs: datasnag.com, *.datasnag.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 secure
Validation of mcp-defi.datasnag.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| datasnag.com. | present | 2371 | 13 | Verified |
| mcp-defi.datasnag.com. | Verified address RRset verified with the apex keys |
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://mcp-defi.datasnag.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp-defi.datasnag.com/mcp | Served over HTTP | 200 |
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 →
contract_security_screener ~46
Audits EVM token contracts for blacklists, honeypot traps, and tax anomalies.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | integer | – | – |
| token_address | string | yes | – |
No output schema declared.
No examples provided.
cross_chain_bridge_optimizer ~71
Calculates lowest-slippage bridge routes across EVM and Solana.
| Name | Type | Req | Description |
|---|---|---|---|
| from_address | string | yes | – |
| from_amount | string | yes | – |
| from_chain | string | yes | – |
| from_token | string | yes | – |
| to_chain | string | yes | – |
| to_token | string | yes | – |
No output schema declared.
No examples provided.
dex_liquidity_router ~46
Aggregates pool depth, 24h volume, spread, and pricing across DEXs.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | – | – |
| token_address | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.geekmarine/mcp-defi-router server?
io.github.geekmarine/mcp-defi-router is listed in the public MCP registry as io.github.geekmarine/mcp-defi-router. Autonomous Web3 router for DEX liquidity depth, EVM contract security, and cross-chain bridges. This page covers its hosted endpoint (https://mcp-defi.datasnag.com/mcp).
Is the io.github.geekmarine/mcp-defi-router server safe to use?
io.github.geekmarine/mcp-defi-router scores 55 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.geekmarine/mcp-defi-router server expose?
io.github.geekmarine/mcp-defi-router exposes 3 tools: dex_liquidity_router, contract_security_screener, cross_chain_bridge_optimizer. Their descriptions and schemas cost roughly 163 tokens of context every time the server is loaded.
Does the io.github.geekmarine/mcp-defi-router server require authentication?
No. We connected to io.github.geekmarine/mcp-defi-router without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.geekmarine/mcp-defi-router server still maintained?
io.github.geekmarine/mcp-defi-router is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.