Cybercentry B20 Token Verification
REMOTE · APP.CYBERCENTRY.CO.UK
Check a Base B20 token can actually be sold: honeypots, frozen exits, issuer controls. $1 USDC.
Available components
Last scanned (2 hours ago)
Scores higher than 51% of remote servers
Reachable. Last reached 21 Nov 2026.
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 3 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 566 tokens (~188/item across 3 items; 3 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (11)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 66
First indexed and scored.
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 21 Nov 2026 · Probed https://app.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=app.cybercentry.co.uk | CN=YR1,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | RSA 2048 | SHA256-RSA | 5e1fa96fc1953d62578072de955ed09fc43 |
| SANs: app.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 app.cybercentry.co.uk. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | DS published | 43876 | 8 | Verified |
| co.uk. | DS published | 11810 | 8 | Verified |
| cybercentry.co.uk. | DS published | 59695 | 8 | Verified |
| app.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 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self' https:; base-uri 'self'; form-action 'self'; frame-ancestors * |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.cybercentry.co.uk/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.cybercentry.co.uk/api/mcp | HTTPS enforced | 301 | https://app.cybercentry.co.uk/api/mcp |
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 →
get_verification_report ~71
Fetch the report for a jobId returned by verify_b20_token. Free to call. While the scan is still running this returns status 'running' with a retryAfter in seconds — wait that long before calling again.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The jobId returned by verify_b20_token. |
No output schema declared.
No examples provided.
verify_b20_token ~254
Start a Cybercentry B20 token verification: can this token actually be sold? Checks pool-hook honeypots, whitelisted exits, freeze-and-seize, live pauses, fakes and issuer controls. Returns a jobId — poll it with get_verification_report. Costs $1 USDC, so a payment reference is required.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The token contract address to verify, as 0x followed by 40 hex characters. |
| chain | string | – | 'base' (mainnet, default) or 'base-sepolia' (testnet). |
| paymentId | string | – | Proof the scan was paid for. Supply ONE of `txHash` (a Base transaction hash for a $1 USDC transfer to the treasury) or `paymentId` (a Base Pay payment id). Each is single-use. Without one the call r… |
| txHash | string | – | Proof the scan was paid for. Supply ONE of `txHash` (a Base transaction hash for a $1 USDC transfer to the treasury) or `paymentId` (a Base Pay payment id). Each is single-use. Without one the call r… |
No output schema declared.
No examples provided.
verify_quote_asset ~241
Settle any token address against the issuer's published tokenized-stock list and read what it is a claim on — a quote asset, a basket, an ERC-4626 wrapper. Synchronous, no polling. Costs $1 USDC, so a payment reference is required.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The token contract address to verify, as 0x followed by 40 hex characters. |
| chain | string | – | 'base' (mainnet, default) or 'base-sepolia' (testnet). |
| paymentId | string | – | Proof the scan was paid for. Supply ONE of `txHash` (a Base transaction hash for a $1 USDC transfer to the treasury) or `paymentId` (a Base Pay payment id). Each is single-use. Without one the call r… |
| txHash | string | – | Proof the scan was paid for. Supply ONE of `txHash` (a Base transaction hash for a $1 USDC transfer to the treasury) or `paymentId` (a Base Pay payment id). Each is single-use. Without one the call r… |
No output schema declared.
No examples provided.
How do I install the Cybercentry B20 Token Verification MCP server?
Cybercentry B20 Token Verification is a hosted endpoint at https://app.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 · app.cybercentry.co.uk
claude mcp add --transport http uk-co-cybercentry-b20-verification 'https://app.cybercentry.co.uk/api/mcp'
What is the Cybercentry B20 Token Verification MCP server?
Cybercentry B20 Token Verification is an MCP server listed in the public MCP registry as uk.co.cybercentry/b20-verification. Check a Base B20 token can actually be sold: honeypots, frozen exits, issuer controls. $1 USDC. This page covers its hosted endpoint (https://app.cybercentry.co.uk/api/mcp).
Is the Cybercentry B20 Token Verification MCP server safe to use?
Cybercentry B20 Token Verification scores 66 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 B20 Token Verification MCP server expose?
Cybercentry B20 Token Verification exposes 3 tools: verify_b20_token, get_verification_report, verify_quote_asset. Their descriptions and schemas cost roughly 566 tokens of context every time the server is loaded.
Does the Cybercentry B20 Token Verification MCP server require authentication?
No. We connected to Cybercentry B20 Token Verification without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Cybercentry B20 Token Verification MCP server still maintained?
Cybercentry B20 Token Verification is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Cybercentry B20 Token Verification MCP server?
VerifyMCP ran 11 checks on Cybercentry B20 Token Verification, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Cybercentry B20 Token Verification: Authorization and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.