Canisell
REMOTE · API.CANISELL.XYZ
Can I sell this Base token? Honeypot, tax and exit-liquidity verdict. Free metadata; $0.01 via x402.
Available components
Last scanned (19 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 420 tokens (~105/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 67
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 4 Nov 2026 · Probed https://api.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 | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f0de46012ab60944139c0bc4ea906524 |
| SANs: canisell.xyz, api.canisell.xyz, *.api.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 api.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://api.canisell.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://api.canisell.xyz/mcp | Served over HTTP | 200 |
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 →
check_base_token Check a Base token (paid) ~157
Pre-trade risk verdict for a Base ERC-20 (built for brand-new Clanker/Zora/Uniswap v4 launches): simulated buy+sell (honeypot, taxes, round-trip loss), owner powers (mint/blacklist/pause/fee setters, upgradeable proxy), exit liquidity and LP lock, token age and creator history. Returns SAFE/CAUTION/DANGER, a 0-100 score and reasons. Costs $0.01 USDC per call via x402. MCP clients without an x402 wallet get the payment terms and the paid HTTP URL instead of a verdict. Not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | ERC-20 token contract address on Base mainnet (chain 8453) |
No output schema declared.
No examples provided.
explain_verdict_fields Explain verdict fields (free) ~43
Free. What SAFE/CAUTION/DANGER, the score and each field of a verdict mean, the limits of the checks, prices, and the JSON schema.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_sample_verdict Example verdict (free) ~34
Free. A cached example of the check_base_token response for a real Base token, to see the shape before paying.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_token_info Base token metadata (free) ~81
Free. Whether an address on Base mainnet is a contract and an ERC-20, plus its name, symbol, decimals and total supply. No risk analysis: use check_base_token (paid) for the SAFE/CAUTION/DANGER verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | ERC-20 token contract address on Base mainnet (chain 8453) |
No output schema declared.
No examples provided.
How do I install the Canisell MCP server?
Canisell is a hosted endpoint at https://api.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 · api.canisell.xyz
claude mcp add --transport http xyz-canisell-canisell 'https://api.canisell.xyz/mcp'
What is the Canisell MCP server?
Canisell is an MCP server listed in the public MCP registry as xyz.canisell/canisell. Can I sell this Base token? Honeypot, tax and exit-liquidity verdict. Free metadata; $0.01 via x402. This page covers its hosted endpoint (https://api.canisell.xyz/mcp).
Is the Canisell MCP server safe to use?
Canisell scores 68 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 Canisell MCP server expose?
Canisell exposes 4 tools: check_base_token, get_token_info, get_sample_verdict, explain_verdict_fields. Their descriptions and schemas cost roughly 315 tokens of context every time the server is loaded.
Does the Canisell MCP server require authentication?
No. We connected to Canisell without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Canisell MCP server still maintained?
Canisell is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.