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.verixiaapps/hostdefi-x402

REMOTE · HOSTDEFI.COM

Free token-safety scans + paid x402 verdicts, signals, radar & EVM swap quotes for AI agents.

Available components

0 this week 81 Trust /100

Last scanned (2 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 5 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 Security74
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2648 tokens (~176/item across 15 items; 15 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 Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 28 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
  • 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
  • 22 Sept 26 0
    • Authorization: unverified → partial ▲ security
    • Tool “buy_api_key” changed its title: Buy a 30-day API key cosmetic
    • Tool “get_x402_pricing” changed its title: Machine-payable price catalog cosmetic
    • Tool “predict_history” changed its title: Polymarket odds history cosmetic
    • Tool “predict_markets” changed its title: Polymarket odds board cosmetic
    • Tool “pregrad_signals” changed its title: Pre-graduation Solana signals cosmetic
    • Tool “radar_alerts” changed its title: Trend radar alerts cosmetic
    • Tool “scan_token” changed its title: Token safety scan (free) cosmetic
    • Tool “swap_evm_price” changed its title: EVM swap price preview cosmetic
    • Tool “swap_evm_quote” changed its title: EVM swap quote (ready to sign) cosmetic
    • Tool “token_launches” changed its title: Fresh token launches (pre-read) cosmetic
    • Tool “token_report” changed its title: Full token due-diligence report cosmetic
    • Tool “token_risk_deep” changed its title: Deep token risk report cosmetic
    • Tool “token_risk_verdict” changed its title: Token risk verdict (A+ to F) cosmetic
    • Tool “wallet_exposure” changed its title: Wallet risk exposure read cosmetic
    • Tool “x402_provider_risk” changed its title: x402 seller risk grade cosmetic
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 30 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “swap_evm_quote” rewrote its description, which is the text the model reads security
  • 26 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
  • 22 Aug 26 0
    • Tool “pregrad_signals” rewrote its description, which is the text the model reads security
    • Tool “token_risk_verdict” rewrote its description, which is the text the model reads security
    • Schema quality: 1581 → 2648 ▼ functional
    • Server version: 1.3.0 → 1.3.1 functional
    • Server version: 1.2.0 → 1.3.0 functional
    • New tool “predict_history” functional
    • New tool “predict_markets” functional
    • New tool “token_launches” functional
    • New tool “token_report” functional
    • New tool “token_risk_deep” functional
    • New tool “wallet_exposure” functional
  • 20 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://hostdefi.com/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=hostdefi.com CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 f191c29ee53e9efe13239ac1c89c13ac
SANs: hostdefi.com, *.hostdefi.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 hostdefi.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
hostdefi.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://hostdefi.com/api/v1/mcp Verified 200
http (plaintext) http://hostdefi.com/api/v1/mcp HTTPS enforced 301 https://hostdefi.com/api/v1/mcp
MCP tools · 15 exposed · ~2,468 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
buy_api_key ~133

PAID ($5, one payment). Mint a 30-day HostDeFi Agent-plan API key (5,000 calls, batch enabled) — the key arrives in the paid response; no account, no signup. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
x402_paymentstring–base64 X-PAYMENT payload

No output schema declared.

No examples provided.

get_x402_pricing ~34

FREE. The HostDeFi machine-payable price catalog: every paid resource, its USD price and settlement rails.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

predict_history ~168

PAID ($0.02/call). 24h odds history for one tracked Polymarket market: [ts, yesUsd, noUsd] points sampled ~1/min into a normalized series — one call, no auth juggling. An untracked market is an uncharged 404. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
marketIdstringyesPolymarket market id (conditionId, from predict_markets)
x402_paymentstring–base64 X-PAYMENT payload

No output schema declared.

No examples provided.

predict_markets ~145

PAID ($0.005/call). Polymarket prediction markets HostDeFi tracks (top ~100 by 24h volume): market ids, questions, latest yes/no odds and sampling stats from HostDeFi's own recorded series. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
limitinteger––
x402_paymentstring–base64 X-PAYMENT payload

No output schema declared.

No examples provided.

pregrad_signals ~141

PAID ($0.05/call). Pre-graduation on-chain signals for a Solana mint: bundled-launch detection, curve-aware holder concentration, Token-2022 traps, authority state. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
mintstringyesSolana mint address
x402_paymentstring–base64 X-PAYMENT payload

No output schema declared.

No examples provided.

radar_alerts ~125

PAID ($0.01/call). Recent HostDeFi trend-radar alerts: big dated movers with real market cap, structured JSON. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
limitinteger––
x402_paymentstring–base64 X-PAYMENT payload

No output schema declared.

No examples provided.

scan_token ~114

FREE. HostDeFi token-safety scan — pass any token contract address (Solana mint or EVM address), or an exact token name/ticker: structured risk read with concerning/legitimate on-chain signals (authority state, liquidity, holder concentration, contract flags). No payment, no signup — fair use 100 checks/day per IP (the same free scanner as https://hostdefi.com/scan).

NameTypeReqDescription
tokenstringyestoken contract address / Solana mint, or an exact token name/ticker

No output schema declared.

No examples provided.

swap_evm_price ~214

PAID ($0.002/call). EVM swap price preview: expected and minimum output for a pair/amount before committing to a firm quote — the cheap look-before-you-swap call. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
buyTokenstringyes'native' or the 0x… address of the token being bought
chainIdstringyesEVM chain id (e.g. 8453 = Base)
sellAmountstringyesinteger amount in the sell token's base units
sellTokenstringyes'native' or the 0x… address of the token being sold
x402_paymentstring–base64 X-PAYMENT payload

No output schema declared.

No examples provided.

swap_evm_quote ~324

PAID ($0.01/call). Executable EVM swap: a firm KyberSwap-routed quote plus a ready-to-sign transaction for the taker's OWN wallet — non-custodial, no key, no account. A 1% platform fee in the chain's native coin is priced into the returned transaction, on top of the swap. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
buyTokenstringyes'native' or the 0x… address of the token being bought
chainIdstringyesEVM chain id (e.g. 8453 = Base, 1 = Ethereum, 137 = Polygon, 42161 = Arbitrum, 43114 = Avalanche)
refstring–optional referrer 0x… address (splits the platform fee)
sellAmountstringyesinteger amount in the sell token's base units
sellTokenstringyes'native' or the 0x… address of the token being sold
takerstringyesthe wallet (0x…) that will sign and broadcast the returned transaction
x402_paymentstring–base64 X-PAYMENT payload (omit on the first call to get payment requirements)

No output schema declared.

No examples provided.

token_launches ~168

PAID ($0.02/call). Fresh token launches with HostDeFi safety pre-reads baked in: newest token profiles annotated with authority state, bundled-launch flag, holder concentration and market depth — the clean flag is fail-closed (true only when every check is provably good). Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
chainstring–chain filter (default solana)
limitinteger––
x402_paymentstring–base64 X-PAYMENT payload

No output schema declared.

No examples provided.

token_report ~197

PAID ($0.35/call). HostDeFi full due-diligence report — one document: the A+–F verdict, on-chain signals (authority state, bundled-launch read, holder concentration, Token-2022 traps on Solana), the dated verdict-history series, trend-radar mentions and a rug-ledger cross-check. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
addressstringyestoken contract address / mint
chainstringyessolana, ethereum, base, arbitrum, …
x402_paymentstring–base64 X-PAYMENT payload (omit on the first call to get payment requirements)

No output schema declared.

No examples provided.

token_risk_deep ~229

PAID ($0.25/call). Deep HostDeFi report in one call: the current A+-F verdict with authority/holder signals, the FULL dated safety history for the token, and a derived trend block (grade movement, liquidity trajectory, worst drawdown, days tracked). All figures are computed from recorded rows — no projections. History depth accrues from 2026-08-16. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
addressstringyestoken contract address / mint
chainstringyessolana, ethereum, base, arbitrum, …
limitinteger–history rows returned, oldest first (default 365)
x402_paymentstring–base64 X-PAYMENT payload (omit on the first call to get payment requirements)

No output schema declared.

No examples provided.

token_risk_verdict ~168

PAID ($0.02/call). HostDeFi A+–F token safety verdict by chain + address: grade, score, verdict prose, liquidity/holders/authority signals. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
addressstringyestoken contract address / mint
chainstringyessolana, ethereum, base, arbitrum, …
x402_paymentstring–base64 X-PAYMENT payload (omit on the first call to get payment requirements)

No output schema declared.

No examples provided.

wallet_exposure ~160

PAID ($0.10/call). Wallet risk-exposure read for a Solana wallet: its largest holdings graded through the full verdict path, exposure counts by risk tier, and a rug-ledger symbol cross-check. Holdings exposure heuristics — NOT AML attribution or sanctions screening. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
walletstringyesSolana wallet address (base58)
x402_paymentstring–base64 X-PAYMENT payload

No output schema declared.

No examples provided.

x402_provider_risk ~148

PAID ($0.02/call). Vet an x402 seller BEFORE paying it: A–F grade from observable signals (402-spec fidelity, price sanity, payTo presence, TLS, latency), dated crawl snapshot. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

NameTypeReqDescription
resourcestringyesresource URL or provider origin
x402_paymentstring–base64 X-PAYMENT payload

No output schema declared.

No examples provided.

Install

How do I install the io.github.verixiaapps/hostdefi-x402 MCP server?

io.github.verixiaapps/hostdefi-x402 is a hosted endpoint at https://hostdefi.com/api/v1/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 · hostdefi.com

# add to Claude Code
claude mcp add --transport http verixiaapps-hostdefi-x402 'https://hostdefi.com/api/v1/mcp'
Common questions

What is the io.github.verixiaapps/hostdefi-x402 MCP server?

io.github.verixiaapps/hostdefi-x402 is an MCP server listed in the public MCP registry as io.github.verixiaapps/hostdefi-x402. Free token-safety scans + paid x402 verdicts, signals, radar & EVM swap quotes for AI agents. This page covers its hosted endpoint (https://hostdefi.com/api/v1/mcp).

Is the io.github.verixiaapps/hostdefi-x402 MCP server safe to use?

io.github.verixiaapps/hostdefi-x402 scores 81 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.verixiaapps/hostdefi-x402 MCP server expose?

io.github.verixiaapps/hostdefi-x402 exposes 15 tools: scan_token, get_x402_pricing, token_risk_verdict, token_risk_deep, pregrad_signals, and 10 more. Their descriptions and schemas cost roughly 2,468 tokens of context every time the server is loaded.

Does the io.github.verixiaapps/hostdefi-x402 MCP server require authentication?

No. We connected to io.github.verixiaapps/hostdefi-x402 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.verixiaapps/hostdefi-x402 MCP server still maintained?

io.github.verixiaapps/hostdefi-x402 is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.