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.

Prescan

REMOTE · PRESCAN.CANISELL.XYZ

Agent security pre-checks: prompt-injection scan, MCP tool-poisoning scan, x402 endpoint check.

66 Trust /100

Last scanned (57 minutes ago)

Scores higher than 52% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

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 Security63
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1044 tokens (~174/item across 6 items; 6 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 Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 3 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 2 Nov 26 64

    First indexed and scored.

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 5 Nov 2026 · Probed https://prescan.canisell.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=canisell.xyz CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 ec1666b1936707490e06ef8af2ea92ef
SANs: canisell.xyz, prescan.canisell.xyz, *.prescan.canisell.xyz
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of prescan.canisell.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
canisell.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://prescan.canisell.xyz/mcp Verified 200
http (plaintext) http://prescan.canisell.xyz/mcp Served over HTTP 200
MCP tools · 6 exposed · ~961 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
about ~28

Free. What Prescan does, prices of the paid tools and HTTP endpoints, and links to docs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_x402_endpoint ~244

Is this x402 endpoint safe to pay? Fetches its 402 terms with one GET (never pays) and checks: payTo validity and EIP-55 checksum, zero/token-contract/OFAC-sanctioned payTo, asset is canonical USDC for the network, amount vs your budget, price vs the price advertised in its OpenAPI and on x402scan, payTo vs the one x402scan recorded, HTTPS, redirects, resource host, domain age (RDAP), tunnels/shared hosts. Returns go/caution/no_go, the recommended payment option and findings. Costs $0.003 USDC per call via x402 (charged only on success). Without an x402 wallet you get the payment terms and the paid HTTP URL instead.

NameTypeReqDescription
max_usdnumber–Your budget per call in USD; above it the verdict is no_go.
networkstring–Preferred network, CAIP-2 (eip155:8453) or v1 name (base).
urlstringyesThe x402 endpoint you are about to pay (full URL incl. query). Only GET is sent; nothing is paid.

No output schema declared.

No examples provided.

list_rules ~26

Free. The detection categories, rule counts and thresholds used by scan_text and scan_tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

preview_scan_text ~102

Free. Prompt-injection pre-check for up to 1000 characters: verdict (safe/suspicious/malicious), score, categories and rule ids. For spans, a sanitized copy, long texts or batches use scan_text (paid).

NameTypeReqDescription
sourcestring–Where the text comes from; tunes a few rules (token_metadata flags any URL in a token name).
textstringyesText to check, up to 1000 characters

No output schema declared.

No examples provided.

scan_text ~379

Prompt-injection pre-check for text your agent is about to read (tool output, web page, email, document, token names/metadata). Deterministic rules, no LLM: instruction override (EN/DE/FR/ES/IT/PT/PL/RU), role hijack, jailbreaks, system-prompt extraction, fake chat delimiters, text addressed to the AI, concealment, data exfiltration (markdown-image beacons, secrets to URLs), tool/fund hijack (shell pipes, transfers, unlimited approvals, skip-confirmation), crypto lures (seed-phrase requests, claim/airdrop links), hidden text (zero-width, Unicode tag and variation-selector smuggling, bidi, homoglyphs, CSS-hidden HTML, ANSI) and encoded payloads (base64/hex/percent decoded and re-scanned). Returns verdict safe/suspicious/malicious, action allow/treat_as_untrusted_data/block, 0-100 score, findings with character spans, risky links, decoded payloads and a sanitized copy. Batch up to 100 texts per call. Costs $0.002 USDC per call via x402 (charged only on success). Without an x402 wallet you get the payment terms and the paid HTTP URL instead.

NameTypeReqDescription
itemsarray–Batch: up to 100 texts (e.g. token names, search results, emails), 200000 characters in total, one price.
sanitizeboolean–Return `sanitized`: the text with invisible characters removed and injected instructions replaced by a marker. Default true.
sourcestring–Where the text comes from; tunes a few rules (token_metadata flags any URL in a token name).
textstring–Text to scan, up to 100000 characters. Use either text or items.

No output schema declared.

No examples provided.

scan_tools ~182

Tool-poisoning scan of MCP tool definitions (a tools/list result) or function schemas before your agent connects or calls them: hidden <IMPORTANT> instructions, cross-tool shadowing, side-channel parameters that ask for file/conversation contents, recipient/payee overrides, instructions hidden in parameter names, defaults or enums, Unicode/ANSI smuggling, duplicate or lookalike tool names. Per-tool verdict and findings with location, plus capability flags (shell, files, network, payments, messaging). Costs $0.002 USDC per call via x402 (charged only on success). Without an x402 wallet you get the payment terms and the paid HTTP URL instead.

NameTypeReqDescription
serverobject–Optional label echoed back.
toolsarrayyesTool definitions as returned by MCP tools/list (or OpenAI/Anthropic function schemas), up to 200.

No output schema declared.

No examples provided.

Install

How do I install the Prescan MCP server?

Prescan is a hosted endpoint at https://prescan.canisell.xyz/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 · prescan.canisell.xyz

# add to Claude Code
claude mcp add --transport http xyz-canisell-prescan 'https://prescan.canisell.xyz/mcp'
Common questions

What is the Prescan MCP server?

Prescan is an MCP server listed in the public MCP registry as xyz.canisell/prescan. Agent security pre-checks: prompt-injection scan, MCP tool-poisoning scan, x402 endpoint check. This page covers its hosted endpoint (https://prescan.canisell.xyz/mcp).

Is the Prescan MCP server safe to use?

Prescan 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 Prescan MCP server expose?

Prescan exposes 6 tools: scan_text, scan_tools, check_x402_endpoint, about, preview_scan_text, list_rules. Their descriptions and schemas cost roughly 961 tokens of context every time the server is loaded.

Does the Prescan MCP server require authentication?

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

Is the Prescan MCP server still maintained?

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