io.github.verixiaapps/hostdefi-x402
REMOTE · HOSTDEFI.COM · SCANNED SEP 20
Free token-safety scans + paid x402 verdicts, signals, radar & EVM swap quotes for AI agents.
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 15 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 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
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
claude mcp add --transport http verixiaapps-hostdefi-x402 'https://hostdefi.com/api/v1/mcp'
{
"mcpServers": {
"verixiaapps-hostdefi-x402": {
"url": "https://hostdefi.com/api/v1/mcp"
}
}
} {
"servers": {
"verixiaapps-hostdefi-x402": {
"type": "http",
"url": "https://hostdefi.com/api/v1/mcp"
}
}
} [mcp_servers.verixiaapps-hostdefi-x402] url = "https://hostdefi.com/api/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"verixiaapps-hostdefi-x402": {
"type": "remote",
"url": "https://hostdefi.com/api/v1/mcp",
"enabled": true
}
}
} openclaw mcp add verixiaapps-hostdefi-x402 --url 'https://hostdefi.com/api/v1/mcp' --transport streamable-http
mcp_servers:
verixiaapps-hostdefi-x402:
url: "https://hostdefi.com/api/v1/mcp" {
"McpServers": {
"verixiaapps-hostdefi-x402": {
"Transport": "http",
"Url": "https://hostdefi.com/api/v1/mcp"
}
}
} assistant mcp add verixiaapps-hostdefi-x402 -t streamable-http -u 'https://hostdefi.com/api/v1/mcp'
{
"mcpServers": {
"verixiaapps-hostdefi-x402": {
"type": "http",
"url": "https://hostdefi.com/api/v1/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.
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 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 | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | e7f62e8a0baed01e1394bb749d4c3361 |
| 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 |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| x402_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| marketId | string | yes | Polymarket market id (conditionId, from predict_markets) |
| x402_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| x402_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana mint address |
| x402_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| x402_payment | string | – | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | token 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.
| Name | Type | Req | Description |
|---|---|---|---|
| buyToken | string | yes | 'native' or the 0x… address of the token being bought |
| chainId | string | yes | EVM chain id (e.g. 8453 = Base) |
| sellAmount | string | yes | integer amount in the sell token's base units |
| sellToken | string | yes | 'native' or the 0x… address of the token being sold |
| x402_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| buyToken | string | yes | 'native' or the 0x… address of the token being bought |
| chainId | string | yes | EVM chain id (e.g. 8453 = Base, 1 = Ethereum, 137 = Polygon, 42161 = Arbitrum, 43114 = Avalanche) |
| ref | string | – | optional referrer 0x… address (splits the platform fee) |
| sellAmount | string | yes | integer amount in the sell token's base units |
| sellToken | string | yes | 'native' or the 0x… address of the token being sold |
| taker | string | yes | the wallet (0x…) that will sign and broadcast the returned transaction |
| x402_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | chain filter (default solana) |
| limit | integer | – | – |
| x402_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | token contract address / mint |
| chain | string | yes | solana, ethereum, base, arbitrum, … |
| x402_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | token contract address / mint |
| chain | string | yes | solana, ethereum, base, arbitrum, … |
| limit | integer | – | history rows returned, oldest first (default 365) |
| x402_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | token contract address / mint |
| chain | string | yes | solana, ethereum, base, arbitrum, … |
| x402_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | Solana wallet address (base58) |
| x402_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| resource | string | yes | resource URL or provider origin |
| x402_payment | string | – | base64 X-PAYMENT payload |
No output schema declared.
No examples provided.
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 74 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.