xyz.chainverdict/chainverdict
REMOTE · CHAINVERDICT.XYZ · SCANNED SEP 20
Pay-per-call x402 checks before an agent moves money: token safety, wallet risk, identifiers.
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1171 tokens (~58/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the xyz.chainverdict/chainverdict MCP server?
xyz.chainverdict/chainverdict is a hosted endpoint at https://chainverdict.xyz/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 · chainverdict.xyz
claude mcp add --transport http xyz-chainverdict-chainverdict 'https://chainverdict.xyz/mcp'
{
"mcpServers": {
"xyz-chainverdict-chainverdict": {
"url": "https://chainverdict.xyz/mcp"
}
}
} {
"servers": {
"xyz-chainverdict-chainverdict": {
"type": "http",
"url": "https://chainverdict.xyz/mcp"
}
}
} [mcp_servers.xyz-chainverdict-chainverdict] url = "https://chainverdict.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-chainverdict-chainverdict": {
"type": "remote",
"url": "https://chainverdict.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-chainverdict-chainverdict --url 'https://chainverdict.xyz/mcp' --transport streamable-http
mcp_servers:
xyz-chainverdict-chainverdict:
url: "https://chainverdict.xyz/mcp" {
"McpServers": {
"xyz-chainverdict-chainverdict": {
"Transport": "http",
"Url": "https://chainverdict.xyz/mcp"
}
}
} assistant mcp add xyz-chainverdict-chainverdict -t streamable-http -u 'https://chainverdict.xyz/mcp'
{
"mcpServers": {
"xyz-chainverdict-chainverdict": {
"type": "http",
"url": "https://chainverdict.xyz/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 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 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://chainverdict.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chainverdict.xyz | CN=WE1,O=Google Trust Services,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 746e13abeaf9fa95139be9ee4676055a |
| SANs: chainverdict.xyz | ||||||
| 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 chainverdict.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| chainverdict.xyz. | 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://chainverdict.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://chainverdict.xyz/mcp | HTTPS enforced | 301 | https://chainverdict.xyz/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 →
data_block Latest Base block ~27
Latest block number, timestamp, tx count, gas utilization. $0.001 per call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
data_gas Base gas oracle ~33
Live Base gas conditions: base fee, priority fees, congestion, est transfer cost. $0.002 per call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
data_portfolio Address portfolio (Base) ~59
ETH + canonical token balances (USDC/WETH/cbBTC/EURC) for an address. $0.004 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Base address to read balances for (0x-prefixed, 42 chars) |
No output schema declared.
No examples provided.
data_token_activity Token transfer activity (Base) ~79
Recent transfer count, volume, unique senders/receivers, activity level. $0.005 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | ERC-20 token contract address on Base (0x-prefixed, 42 chars) |
| blocks | number | – | Look-back window in blocks (default 2000, ~1 hour on Base) |
No output schema declared.
No examples provided.
data_token_supply Token supply & burn (Base) ~60
Total/circulating/burned supply and burn percentage for an ERC-20 on Base. $0.003 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | ERC-20 token contract address on Base (0x-prefixed, 42 chars) |
No output schema declared.
No examples provided.
html_to_markdown HTML to Markdown ~41
Convert raw HTML to clean Markdown. $0.002 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | Raw HTML string to convert (full document or fragment) |
No output schema declared.
No examples provided.
payment_info How to pay for these tools (free) ~43
Free. Explains how to call the paid tools on this server: the x402 protocol, the network and asset, the settlement address, and the price of every tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
security_email Email spoofing posture (SPF/DMARC/DKIM) ~69
Live DNS check of a domain's email authentication records. $0.01 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, without scheme (e.g. example.com) |
| selector | string | – | Optional DKIM selector to look up (e.g. google, default, s1) |
No output schema declared.
No examples provided.
security_tls TLS certificate check ~53
Live TLS handshake: cert validity, issuer, expiry countdown. $0.01 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Hostname to probe over TLS on port 443, without scheme (e.g. example.com) |
No output schema declared.
No examples provided.
security_typosquat Typosquat / look-alike domain check ~86
Flags homoglyph and edit-distance look-alikes of known brands (c0inbase, b1nance, etc.). $0.005 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| brands | string | – | Optional comma-separated brand list to check against (defaults to a built-in set) |
| domain | string | yes | Domain to analyse for brand impersonation (e.g. c0inbase.com) |
No output schema declared.
No examples provided.
text_diff Structured text diff ~69
Diff two texts (lines/words/chars). $0.002 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | Original text (left side of the diff) |
| b | string | yes | Modified text (right side of the diff) |
| mode | string | – | Diff granularity; defaults to lines |
No output schema declared.
No examples provided.
token_verdict Token safety verdict (Base) ~71
Heuristic ERC-20 safety verdict on Base: bytecode risk capabilities, ownership, metadata, 0-100 score, hold/caution/avoid. $0.01 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | ERC-20 token contract address on Base (0x-prefixed, 42 chars) |
No output schema declared.
No examples provided.
validate_bic Validate BIC/SWIFT ~60
BIC/SWIFT structural validation and decomposition. $0.001 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| bic | string | yes | BIC/SWIFT code, 8 or 11 characters (e.g. DEUTDEFF or DEUTDEFF500) |
No output schema declared.
No examples provided.
validate_iban Validate IBAN ~65
IBAN mod-97 checksum + country length rules. $0.001 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | yes | IBAN including 2-letter country prefix (e.g. DE89 3704 0044 0532 0130 00; spaces tolerated) |
No output schema declared.
No examples provided.
validate_isin Validate ISIN (ISO 6166) ~49
Securities identifier checksum validation. $0.001 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| isin | string | yes | 12-character International Securities Identification Number (ISO 6166), e.g. US0378331005 |
No output schema declared.
No examples provided.
validate_lei Validate LEI (ISO 17442) ~57
Legal Entity Identifier checksum validation. $0.002 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| lei | string | yes | 20-character Legal Entity Identifier (ISO 17442), e.g. 5299000J2N45DDNE4Y28 |
No output schema declared.
No examples provided.
validate_vat Validate EU VAT number ~61
EU VAT format validation with deterministic checksums (DE, IT, LU, PL, SI). $0.001 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| vat | string | yes | EU VAT number including country prefix (e.g. DE123456789, LU12345678) |
No output schema declared.
No examples provided.
verify_payment Verify on-chain payment (Base) ~54
Decode ERC-20 transfers in a Base transaction: amounts, counterparties, confirmations. $0.02 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| txhash | string | yes | Base transaction hash to decode (0x-prefixed, 66 chars) |
No output schema declared.
No examples provided.
verify_token Canonical token check (Base) ~76
Is this the real USDC/EURC/WETH/cbBTC/USDT on Base? Anti-phishing for stablecoin payments. $0.005 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Token contract address (0x…) or symbol (e.g. USDC, WETH) to verify against the canonical Base list |
No output schema declared.
No examples provided.
wallet_dossier Wallet dossier (Base) ~59
Profile of a Base address: EOA vs contract, balance, activity band, flags. $0.01 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Base address to profile (0x-prefixed, 42 chars; EOA or contract) |
No output schema declared.
No examples provided.
What is the xyz.chainverdict/chainverdict MCP server?
xyz.chainverdict/chainverdict is an MCP server listed in the public MCP registry as xyz.chainverdict/chainverdict. Pay-per-call x402 checks before an agent moves money: token safety, wallet risk, identifiers. This page covers its hosted endpoint (https://chainverdict.xyz/mcp).
Is the xyz.chainverdict/chainverdict MCP server safe to use?
xyz.chainverdict/chainverdict scores 80 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 xyz.chainverdict/chainverdict MCP server expose?
xyz.chainverdict/chainverdict exposes 20 tools: payment_info, token_verdict, wallet_dossier, validate_iban, validate_vat, and 15 more. Their descriptions and schemas cost roughly 1,171 tokens of context every time the server is loaded.
Does the xyz.chainverdict/chainverdict MCP server require authentication?
No. We connected to xyz.chainverdict/chainverdict without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the xyz.chainverdict/chainverdict MCP server still maintained?
xyz.chainverdict/chainverdict 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.