Cybercentry Verification

Registre officiel Finance et paiements

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

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

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

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  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

Questions fréquentes

Qu'est-ce que Cybercentry Verification ?

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

Comment installer Cybercentry Verification ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http cybercentry-verification 'https://centry.cybercentry.co.uk/api/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Cybercentry Verification ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Cybercentry Verification est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Cybercentry Verification ?

Il est publié par Cybercentry. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.