Is the Co Cybercentry Verification MCP server down?

mcp-registry/uk.co.cybercentry/verification · v1.0.4

As of 2026-10-20 07:38 UTC, the Co Cybercentry Verification MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.

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

claude mcp add --transport http co-cybercentry-verification-mcp-server https://centry.cybercentry.co.uk/api/mcp

{
  "mcpServers": {
    "co-cybercentry-verification-mcp-server": {
      "type": "http",
      "url": "https://centry.cybercentry.co.uk/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (81/100)

What to fix (4)

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fuk.co.cybercentry%2Fverification/fixes

{
  "name": "list_services",
  "description": "List every Cybercentry verification service with its price, inputs and SLA. Free.",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "List Services"
}

{
  "name": "post_launch_screening",
  "description": "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 c",
  "inputSchema": {
    "type": "object",
    "required": [
      "token"
    ],
    "properties": {
      "chain": {
        "type": "string",
        "description": "Chain name or EVM chain ID. base (8453) only for now, since the scoring contracts are deployed there."
      },
      "token": {
        "type": "string",
        "description": "Token contract address"
      },
      "creator": {
        "type": "string",
        "description": "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_token": {
        "type": "string",
        "description": "Optional Cybercentry subscription token. Uses your plan quota instead of paying per call."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Post-launch Screening"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/uk.co.cybercentry/verification"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/uk.co.cybercentry/verification"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~2,713 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.97% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• post_launch_screening ~330 tokens
• pre_launch_screening ~305 tokens
• ethereum_token_verification ~288 tokens
• media_content_verification ~268 tokens
• openclaw_ai_agent_verification ~235 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fuk.co.cybercentry%2Fverification.svg)](https://glimind.com/server/mcp-registry%2Fuk.co.cybercentry%2Fverification?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fuk.co.cybercentry%2Fverification?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fuk.co.cybercentry%2Fverification.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fuk.co.cybercentry%2Fverification.svg
   :target: https://glimind.com/server/mcp-registry%2Fuk.co.cybercentry%2Fverification?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a90677fbba23a4f8…, first seen 2026-10-17, included at leaf 2828 of 31,590. Version history · verify what your client received.

Tools (14)

• base_token_verification
• cyber_security_consultant
• ethereum_token_verification
• list_services
• media_content_verification
• openclaw_ai_agent_verification
• post_launch_screening
• pre_launch_screening
• private_data_verification
• quantum_cryptography_verification
• recent_exploits
• solidity_code_verification
• wallet_verification
• web_application_verification

Compare: most reliable security servers · most reliable knowledge servers · most reliable data servers · most reliable code servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Co Cybercentry Verification MCP server down right now?

As of 2026-10-20 07:38 UTC, the Co Cybercentry Verification MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Co Cybercentry Verification MCP server provide?

Co Cybercentry Verification MCP server advertises 14 tools, including base_token_verification, cyber_security_consultant, ethereum_token_verification, list_services, media_content_verification.

How do I install Co Cybercentry Verification MCP server?

Point your MCP client at this streamable-http endpoint: https://centry.cybercentry.co.uk/api/mcp

Is the Co Cybercentry Verification MCP server safe to connect to an AI agent?

Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Co Cybercentry Verification MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.