mcpField
C
Cybercentry Verification

Cybercentry Verification

Remote
centry.cybercentry.co.ukSecurity2Updated 10w ago

About Cybercentry Verification

Cybercentry Verification is a remote MCP server for AI agents that checks wallets, tokens, contracts, websites, and other security targets. It provides two free tools, while the remaining verifications are charged per call.

Key features

  1. 01Verify wallets and assess risk
  2. 02Check tokens and Solidity code
  3. 03Scan websites and dApp frontends
  4. 04Verify agent configuration and media
  5. 05Prove private data and encrypt for quantum resistance
  6. 06Browse exploit updates and service catalogue

Use cases

  1. 01Screen wallets for sanctions and risk
  2. 02Check tokens and contracts for security issues
  3. 03Scan a dApp website frontend
  4. 04Assess an agent's configuration security

MCP support

It exposes 12 security verification tools to MCP clients over Streamable HTTP. Two tools are free; the others are charged per call.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://centry.cybercentry.co.uk/api/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

14

This tool takes no parameters.

Details

From the project README

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)

Links


Cybercentry Limited

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.