English Français العربية

Cybercentry Verification

Official registry Finance and payments

Twelve tools: token, wallet, contract and site security. Two free, the rest $1 in USDC over x402.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http cybercentry-verification 'https://centry.cybercentry.co.uk/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "cybercentry-verification": {
            "type": "http",
            "url": "https://centry.cybercentry.co.uk/api/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Cybercentry MCP Server
  2. Connect
  3. Tools
  4. Paying
  5. Standards
  6. Links

Cybercentry MCP Server

Pay-per-call security verification for AI agents: wallets, tokens, contracts, dApps, agents and more.

Nothing to install. This is a remote MCP server — connect to the URL and the tools appear.
Endpointhttps://centry.cybercentry.co.uk/api/mcp
Transportstreamable-http
Registryuk.co.cybercentry/verification
Websitehttps://centry.cybercentry.co.uk

Connect

Claude (Desktop or claude.ai)

Remote servers are added as connectors, not through claude_desktop_config.json — that file is for local servers that run a command.

  1. Settings → Connectors
  2. Add → Add custom connector
  3. Paste https://centry.cybercentry.co.uk/api/mcp
Other clients

Anything that speaks MCP over streamable HTTP can connect. Point it at:

https://centry.cybercentry.co.uk/api/mcp

Check your client's own documentation for where a remote MCP server URL goes — some use a settings pane, some a config file. If yours takes a config file, the field is the server URL rather than a command.

Tools

Twelve tools. Two are free and need no payment, credentials or account:

ToolWhat it does
list_servicesThe catalogue: every verification, its inputs and its price
recent_exploitsLive exploit feed, curated from DefiLlama

The other ten are paid, at $1.00 per call:

ToolWhat it verifies
wallet_verificationSanctions screening and risk scoring across 35 EVM chains
base_token_verificationBase B20 tokens: honeypots, freeze-and-seize, pause, impersonation
ethereum_token_verificationEthereum token due diligence
solidity_code_verificationSolidity source, for known vulnerability classes
web_application_verificationLive site and dApp frontend scan
openclaw_ai_agent_verificationAn agent's configuration: auth gaps, prompt-injection exposure, unsafe permissions
media_content_verificationC2PA provenance and content authenticity
private_data_verificationZero-knowledge proof over a payload, without revealing it
quantum_cryptography_verificationQuantum-resistant encryption of a payload
cyber_security_consultantAdvisory answers grounded in a security body of knowledge

Wallet and web application verification return a job immediately and fill in as findings arrive; both can take up to three minutes. The rest return in under ten seconds.

Paying

No API keys. No accounts. Two ways to pay for the ten paid tools:

x402 — the client is told the price, pays in USDC, and retries. Automatic in clients that support it.

Base    eip155:8453   USDC
Solana  mainnet       USDC

Subscription token — for clients that do not speak x402 yet. Pass subscription_token as a tool argument, or send it as the x-subscription-token header.

A paid call runs the verification before it settles, so a call that fails is never charged.

Standards

The interfaces these services implement were specified in public:

  • ERC-8126 — AI Agent Verification (Final)
  • ERC-8196 — AI Agent Authenticated Wallet (Final)
  • ERC-8376 — Token Launch Abuse Detection and Remediation (open pull request)

Cybercentry Limited

Frequently asked questions

What is Cybercentry Verification?

Twelve tools: token, wallet, contract and site security. Two free, the rest $1 in USDC over x402.

How do I install Cybercentry Verification?

It runs as a remote server. In Claude Code: claude mcp add --transport http cybercentry-verification 'https://centry.cybercentry.co.uk/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Cybercentry Verification need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Cybercentry Verification open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Cybercentry Verification?

It is published by Cybercentry. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.