Home / MCP registry index / xyz.chainverdict/chainverdict

Chainverdict

xyz.chainverdict/chainverdict in the official MCP registry. Endpoint https://chainverdict.xyz/mcp. Source: github.com/alexanderbalieu-connections/chainverdict.

The registry describes it as: Pay-per-call x402 checks before an agent moves money: token safety, wallet risk, identifiers.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http chainverdict https://chainverdict.xyz/mcp

{
  "mcpServers": {
    "chainverdict": {
      "url": "https://chainverdict.xyz/mcp"
    }
  }
}

code --add-mcp '{"name":"chainverdict","type":"http","url":"https://chainverdict.xyz/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

payment_info token_verdict wallet_dossier validate_iban validate_vat validate_bic html_to_markdown text_diff verify_payment verify_token validate_lei validate_isin security_email security_tls security_typosquat data_gas data_block data_token_supply data_token_activity data_portfolio

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 9ddeadd3f304cd22. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/xyz-chainverdict-chainverdict/badge.svg)](https://lazaretto.dev/mcp-registry/xyz-chainverdict-chainverdict)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers