Archalis Radar
REMOTE · API.ARCHALIS.COM
BNB Chain token risk ratings (AAA to C), honeypot checks and rug pull forensics with on-chain proof
Available components
Last scanned (1 hour ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 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 Security77
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 535 tokens (~133/item across 4 items; 4 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 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.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 70
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 5 Nov 2026 · Probed https://api.archalis.com/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=radar.archalis.com | CN=YE2,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5857e84fa145dcfa6f0afd634ff27e3e0a9 |
| SANs: api.archalis.com, docs.archalis.com, radar.archalis.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.archalis.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| archalis.com. | present | 47294 | 8 | Verified |
| api.archalis.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.archalis.com/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.archalis.com/v1/mcp | HTTPS enforced | 301 | https://api.archalis.com/v1/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 →
check_wallet Wallet history ~98
What the radar knows about a BNB Chain wallet: pools it created and how they ended (rug pulls), other roles in pools (insider seller, received pulled liquidity, volume bot), who funded it, which wallets it funded, and the network of linked token creators it belongs to. From the radar archive (pools found since October 16, 2026).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet or contract address on BNB Chain |
No output schema declared.
No examples provided.
get_liquidity_alerts Liquidity alerts ~126
Alerts from the liquidity sentinel, which reads every pool about every 1.5 seconds: pools whose base liquidity (BNB, USDT...) dropped 40% (liquidity_falling) or 70% or more (liquidity_collapsed) from their peak. Covers every pool found in the last 24 hours on PancakeSwap, Uniswap V4 and PancakeSwap Infinity. The free plan sees alerts with a 60-second delay.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| since_minutes | integer | – | How far back to look |
No output schema declared.
No examples provided.
get_rating_track_record Rating track record ~45
How often new BNB Chain pools ended in a rug pull after receiving each grade at their first analysis (official default rates), so the reliability of the ratings can be judged.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_token_rating Token rating ~172
Risk rating of a BNB Chain token from AAA to C (SCAM for confirmed scam patterns, D after a rug pull), with risk flags, simulated buy/sell taxes, who controls the contract and the liquidity, the creator history and, after a collapse, the forensics of who took the money out. A token whose markets the radar cannot read (no pool with real liquidity in BNB, USDT, USDC, FDUSD or the other supported bases) is not rated: rating is null and notRated says why. Ratings measure structural risk, not price potential. Not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract address on BNB Chain |
| fresh | boolean | – | Run a new on-chain analysis instead of using the archive (counts against the daily fresh analyses of the plan) |
No output schema declared.
No examples provided.
How do I install the Archalis Radar MCP server?
Archalis Radar is a hosted endpoint at https://api.archalis.com/v1/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.archalis.com
claude mcp add --transport http archalisradar-archalis-radar 'https://api.archalis.com/v1/mcp'
What is the Archalis Radar MCP server?
Archalis Radar is an MCP server listed in the public MCP registry as io.github.ArchalisRadar/archalis-radar. BNB Chain token risk ratings (AAA to C), honeypot checks and rug pull forensics with on-chain proof. This page covers its hosted endpoint (https://api.archalis.com/v1/mcp).
Is the Archalis Radar MCP server safe to use?
Archalis Radar scores 72 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 Archalis Radar MCP server expose?
Archalis Radar exposes 4 tools: get_token_rating, check_wallet, get_liquidity_alerts, get_rating_track_record. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.
Does the Archalis Radar MCP server require authentication?
No. We connected to Archalis Radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Archalis Radar MCP server still maintained?
Archalis Radar 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.