Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.geekmarine/mcp-defi-router

REMOTE · MCP-DEFI.DATASNAG.COM

Autonomous DeFi router for multi-hop execution, MEV risk mitigation, and transaction calldata.

0 this week 30 Trust /100

Last scanned (20 hours ago)

Scores higher than 13% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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 connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 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
  • 17 Oct 26 0
    • Endpoint reachability: unreachable → not serving MCP ▼ security
  • 16 Oct 26 0
    • Endpoint reachability: not serving MCP → unreachable ▼ security
  • 1 Oct 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • HTTPS: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 26 0
    • Authorization: unverified → partial ▲ security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • First check of Tool coverage: 100 functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 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
  • 24 Sept 26 0

    First indexed and scored.

Diagnostics

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 21 Nov 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 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 743a5b00f880d4d0132522bc08782642
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. DS published 19718 13 Verified
datasnag.com. DS published 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
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy same-origin

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 Inconclusive 405
MCP tools · 3 exposed · ~515 tokens

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 →

Tool Tokens
contract_security_screener ~125

Audits EVM token contracts for honeypots, transfer traps, blacklist bytecode, and calculates a composite vulnerability score and liquidity ceiling.

NameTypeReqDescription
chain_idinteger–EVM chain ID (e.g., 8453 for Base, 1 for Ethereum Mainnet, 56 for BSC). Defaults to 8453.
max_acceptable_tax_pctnumber–Maximum allowable cumulative buy/sell tax threshold percentage. Defaults to 5.0%.
token_addressstringyesThe EVM contract address of the target token to evaluate.
NameTypeReqDescription
chain_idintegeryes–
detected_risk_flagsarray––
risk_metricsobjectyesComposite risk score (0-100) and max position ceiling
security_verdictstringyesClearance indicator (e.g., CLEAR_FOR_AUTOMATED_TRADE or CRITICAL_REJECT_SCAM)
tax_auditobjectyesAudit of buy, sell, and transfer taxes
token_addressstringyes–
token_identityobject––

No examples provided.

cross_chain_bridge_optimizer ~206

Simulates cross-chain bridge and swap paths across EVM and Solana, factors gas and protocol overhead, and formats ready-to-sign execution call data.

NameTypeReqDescription
from_addressstringyesUser or agent sender wallet address.
from_amountstringyesSource token quantity in base atomic units (e.g., '1000000' for 1 USDC).
from_chainstringyesOrigin blockchain network key (e.g., 'base', 'eth', 'arbitrum', 'solana').
from_tokenstringyesSource token symbol or contract address.
slippage_tolerancenumber–Maximum allowable slippage fraction (e.g., 0.005 for 0.5%). Defaults to 0.005.
to_chainstringyesDestination blockchain network key (e.g., 'base', 'eth', 'arbitrum', 'solana').
to_tokenstringyesDestination token symbol or contract address.
NameTypeReqDescription
economic_friction_analysisobjectyesGas and protocol bridge fees breakdown
execution_timingobject––
pre_flight_requirementsobject––
ready_to_sign_payloadobjectyesTransaction calldata payload containing to, data, value, gasLimit
route_idstringyes–
route_summarystringyes–

No examples provided.

dex_liquidity_router ~184

Simulates DEX swap routes across liquidity pools, calculates dynamic price impact for trade sizes, and computes MEV/sandwich attack risk scores.

NameTypeReqDescription
chain_idstring–Blockchain network identifier (e.g., 'base', 'ethereum', 'arbitrum', 'bsc'). Defaults to 'base'.
max_slippage_pctnumber–Maximum acceptable slippage tolerance percentage. Defaults to 0.5%.
token_addressstringyesThe ERC-20 contract address of the token to audit (e.g. 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 for USDC).
trade_size_usdnumber–Simulated order size in USD to calculate dynamic slippage and price impact. Defaults to 1000.0.
NameTypeReqDescription
alternative_routesarray–Secondary liquidity pools sorted by depth
chainstringyes–
execution_verdictstringyesTrade suitability verdict (e.g., APPROVED_FOR_EXECUTION or REJECT_HIGH_SLIPPAGE)
optimal_routeobjectyesTop liquidity pool with dynamic price impact and calibrated execution parameters
simulated_trade_size_usdnumber––
token_addressstringyes–

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http geekmarine-mcp-defi-router 'https://mcp-defi.datasnag.com/mcp'
Common questions

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 DeFi router for multi-hop execution, MEV risk mitigation, and transaction calldata. 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 30 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 515 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.geekmarine/mcp-defi-router server?

VerifyMCP ran 4 checks on io.github.geekmarine/mcp-defi-router, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about io.github.geekmarine/mcp-defi-router: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.