Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cybercentry Verification

REMOTE · CENTRY.CYBERCENTRY.CO.UK · SCANNED OCT 6

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

0 this week 79 Trust /100
Trust breakdown (7 categories)

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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1949 tokens (~139/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Cybercentry Verification MCP server?

Cybercentry Verification is a hosted endpoint at https://centry.cybercentry.co.uk/api/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 · centry.cybercentry.co.uk

# add to Claude Code
claude mcp add --transport http uk-co-cybercentry-verification 'https://centry.cybercentry.co.uk/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "uk-co-cybercentry-verification": {
      "url": "https://centry.cybercentry.co.uk/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "uk-co-cybercentry-verification": {
      "type": "http",
      "url": "https://centry.cybercentry.co.uk/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.uk-co-cybercentry-verification]
url = "https://centry.cybercentry.co.uk/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-co-cybercentry-verification": {
      "type": "remote",
      "url": "https://centry.cybercentry.co.uk/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add uk-co-cybercentry-verification --url 'https://centry.cybercentry.co.uk/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  uk-co-cybercentry-verification:
    url: "https://centry.cybercentry.co.uk/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "uk-co-cybercentry-verification": {
      "Transport": "http",
      "Url": "https://centry.cybercentry.co.uk/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add uk-co-cybercentry-verification -t streamable-http -u 'https://centry.cybercentry.co.uk/api/mcp'
// mcp.json
{
  "mcpServers": {
    "uk-co-cybercentry-verification": {
      "type": "http",
      "url": "https://centry.cybercentry.co.uk/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 28 Sept 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 18 Sept 26 +1
    • Stability: fail → pass ▲ security
  • 17 Sept 26 0
    • Tool “wallet_verification” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • “ethereum_token_verification” added an optional parameter “chain” cosmetic
    • “ethereum_token_verification” reworded the description of “chain_id” cosmetic
    • “ethereum_token_verification” reworded the description of “contract_address” cosmetic
    • “ethereum_token_verification” reworded the description of “platform_id” cosmetic
    • “ethereum_token_verification” made “chain_id” optional cosmetic
    • “ethereum_token_verification” made “platform_id” optional cosmetic
  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 89 to 93.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 86.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 76 to 79.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 9 Oct 2026 · Probed https://centry.cybercentry.co.uk/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=centry.cybercentry.co.uk CN=YR1,O=Let's Encrypt,C=US 21 Sept 2026 20 Dec 2026 RSA 2048 SHA256-RSA 5535f5b523266a8c79beb779bda02a844bd
SANs: centry.cybercentry.co.uk
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of centry.cybercentry.co.uk. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
uk. present 43876 8 Verified
co.uk. present 11810 8 Verified
cybercentry.co.uk. present 59695 8 Verified
centry.cybercentry.co.uk. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://centry.cybercentry.co.uk/api/mcp Verified 200
http (plaintext) http://centry.cybercentry.co.uk/api/mcp HTTPS enforced 301 https://centry.cybercentry.co.uk/api/mcp
MCP tools · 14 exposed · ~1,909 tokens

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 →

Tool Tokens
base_token_verification ~158

Check a Base token contract before buying: detects honeypots, armed freeze-and-seize, a live pause, fake B20s and ticker-impersonation copycats, and separately discloses issuer controls (admin centralisation, supply cap, transfer policy, rebase) so a legitimate token is not mistaken for a scam. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
chainstring–base for mainnet (default), or base-sepolia to check a token before you launch it
contract_addressstringyesB20 token contract address
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.

No output schema declared.

No examples provided.

cyber_security_consultant ~97

Ask a cyber security question and get an expert answer backed by real-time threat intelligence, covering current threats, best practice and compliance. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
querystringyesQuestion (e.g., What should an incident response capability include?).
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.

No output schema declared.

No examples provided.

ethereum_token_verification ~212

Check an Ethereum or EVM token contract before buying: rug pull, hidden tax, liquidity legitimacy and holder concentration risk. Token due diligence returned as a scan report. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
chainstring–Chain name or EVM chain ID: ethereum (1), base (8453), arc (5042), robinhood (4663), optimism (10), polygon (137), arbitrum (42161), bsc (56), avalanche (43114), gnosis (100), blast (81457). Defaults…
chain_idnumber–Legacy: network, 1 mainnet or 2 testnet. Use chain instead.
contract_addressstringyesToken contract address
platform_idnumber–Legacy: 1 Ethereum or 17 Base. Use chain instead.
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.

No output schema declared.

No examples provided.

list_services ~25

List every Cybercentry verification service with its price, inputs and SLA. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

media_content_verification ~169

Check whether an image or video is authentic and where it came from: C2PA content credentials, provenance and metadata extraction, with an avatar and logo impersonation check. Detect AI-generated or tampered media before trusting it. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
extract_metadataboolean–Extract file metadata (default: true)
image_uristringyesAvatar/logo image URI: HTTPS URL or IPFS path
media_file_pathstringyesURL or path to the media file to verify
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.
verify_authenticityboolean–Verify content authenticity / C2PA provenance (default: true)

No output schema declared.

No examples provided.

openclaw_ai_agent_verification ~145

Audit an AI agent configuration for security holes: prompt injection exposure, missing authentication, over-broad tool permissions and unsafe gateway settings. Check an agent before you trust it or connect to it. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
configstringyesAgent configuration as a JSON string
messagestring–Message
sessionIdstring–Session ID
skillsstring–Skills
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.
toolstring–Tool to validate, as a JSON string

No output schema declared.

No examples provided.

post_launch_screening ~283

Score a live token launch under ERC-8376, the token launch abuse standard we co-authored. The twelve-signal vector is assembled from chain state and scored against the eleven deployer abuse patterns into an abuse score of 0 to 100, with confidence reported separately so a high score on thin evidence cannot read as a certainty. Signals that could not be computed are named rather than scored clean. Price decline is excluded by rule, so a launch that locked liquidity, sold nothing and fell 95 per cent still scores clean: falling is not fraud. Name the creator, because at most venues the token was deployed by the venue's own factory and the creating address is the launchpad rather than the applicant. A screening, not a bonded on-chain report. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
chainstring–Chain name or EVM chain ID. base (8453) only for now, since the scoring contracts are deployed there.
creatorstring–Wallet of the party who requested the launch, as connected at your venue. Without it the launch is unattributed and the signals about the deployer come back unavailable.
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.
tokenstringyesToken contract address

No output schema declared.

No examples provided.

pre_launch_screening ~296

Screen who is asking to launch, before you deploy anything for them. At most venues the launchpad creates the token, so the only thing in front of you beforehand is a connected wallet: this screens that wallet, and it includes the full wallet verification rather than a summary of one. OFAC SDN sanctions screening, the funding chain walked to depth across 33 chains, mixer contact including the Tornado Cash pools, dusting, control clusters and exchange reuse, with a risk score. Then the launch-specific half: allocations this wallet has taken from contracts before and whether it still holds them or sold them, and whether the ticker it wants collides with a token it already touched. Says what it could not establish rather than reporting it clean. Eight of the twelve ERC-8376 signals describe conduct during or after a sale and cannot exist yet, so this reports on the party and not on the launch. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
chainstring–Chain name or EVM chain ID. Defaults to base (8453).
creatorstringyesWallet address of the party requesting the launch, as connected at your venue
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.
tickerstring–Ticker or name they want, to check for collision with an existing project

No output schema declared.

No examples provided.

private_data_verification ~100

Prove a fact about private data without revealing the data: validates text integrity and returns a zero-knowledge proof (ZKP) with a verification ID and URL. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
cpdv_datastringyesData (e.g., Test Data)
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.

No output schema declared.

No examples provided.

quantum_cryptography_verification ~102

Encrypt text with quantum-resistant (post-quantum) cryptography, for secrets that must outlast classical encryption. Returns a record ID and a decrypt URL. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
cqcv_datastringyesAny text data you want to encrypt and verify
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.

No output schema declared.

No examples provided.

recent_exploits ~54

Recent real-world web3 exploits from the live feed, with loss amounts, attack vectors and the Cybercentry service that addresses each. Free.

NameTypeReqDescription
limitnumber–Max incidents to return (default 10).

No output schema declared.

No examples provided.

solidity_code_verification ~82

Audit Solidity smart contract source for vulnerabilities before you deploy or call it. Returns findings with a clear risk level. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
solidity_codestringyesSolidity Code
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.

No output schema declared.

No examples provided.

wallet_verification ~99

Screen a wallet address for sanctions and risk: OFAC SDN sanctions screening, risk scoring and suspicious-activity detection across 33 EVM chains. Check a counterparty before you transact with it. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.
wallet_addressstringyesWallet Address

No output schema declared.

No examples provided.

web_application_verification ~87

Scan a website or dApp frontend for vulnerabilities using OWASP checks, before connecting a wallet to it or trusting it with user data. Costs $1.00 per call, paid in USDC over x402.

NameTypeReqDescription
subscription_tokenstring–Optional Cybercentry subscription token. Uses your plan quota instead of paying per call.
target_urlstringyesTarget URL

No output schema declared.

No examples provided.

Common questions

What is the Cybercentry Verification MCP server?

Cybercentry Verification is an MCP server listed in the public MCP registry as uk.co.cybercentry/verification. Twelve tools: token, wallet, contract and site security. Two free, the rest $1 in USDC over x402. This page covers its hosted endpoint (https://centry.cybercentry.co.uk/api/mcp).

Is the Cybercentry Verification MCP server safe to use?

Cybercentry Verification scores 79 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 Cybercentry Verification MCP server expose?

Cybercentry Verification exposes 14 tools: list_services, recent_exploits, base_token_verification, cyber_security_consultant, ethereum_token_verification, and 9 more. Their descriptions and schemas cost roughly 1,909 tokens of context every time the server is loaded.

Does the Cybercentry Verification MCP server require authentication?

No. We connected to Cybercentry Verification without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Cybercentry Verification MCP server still maintained?

Cybercentry Verification is still listed as active in the MCP registry. We last reached this channel on 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.