qpon.arctic/arctic
REMOTE · WWW.ARCTIC.QPON · SCANNED OCT 4
Read Robinhood Chain live: scan a token, trace its deployer, list new launches.
Available components
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
- 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 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 397 tokens (~132/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the qpon.arctic/arctic MCP server?
qpon.arctic/arctic is a hosted endpoint at https://www.arctic.qpon/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 · www.arctic.qpon
claude mcp add --transport http qpon-arctic-arctic 'https://www.arctic.qpon/api/mcp'
{
"mcpServers": {
"qpon-arctic-arctic": {
"url": "https://www.arctic.qpon/api/mcp"
}
}
} {
"servers": {
"qpon-arctic-arctic": {
"type": "http",
"url": "https://www.arctic.qpon/api/mcp"
}
}
} [mcp_servers.qpon-arctic-arctic] url = "https://www.arctic.qpon/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"qpon-arctic-arctic": {
"type": "remote",
"url": "https://www.arctic.qpon/api/mcp",
"enabled": true
}
}
} openclaw mcp add qpon-arctic-arctic --url 'https://www.arctic.qpon/api/mcp' --transport streamable-http
mcp_servers:
qpon-arctic-arctic:
url: "https://www.arctic.qpon/api/mcp" {
"McpServers": {
"qpon-arctic-arctic": {
"Transport": "http",
"Url": "https://www.arctic.qpon/api/mcp"
}
}
} assistant mcp add qpon-arctic-arctic -t streamable-http -u 'https://www.arctic.qpon/api/mcp'
{
"mcpServers": {
"qpon-arctic-arctic": {
"type": "http",
"url": "https://www.arctic.qpon/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Oct 26 65
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 8 Oct 2026 · Probed https://www.arctic.qpon/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.arctic.qpon | CN=YR2,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | RSA 2048 | SHA256-RSA | 62e0eeda17f04f653a7abe43492e6d60a39 |
| SANs: *.arctic.qpon, arctic.qpon | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 insecure
Validation of www.arctic.qpon. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| qpon. | present | 2327, 16832 | 8, 8 | Verified |
| arctic.qpon. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.arctic.qpon/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.arctic.qpon/api/mcp | HTTPS enforced | 308 | https://www.arctic.qpon/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 →
robinhood_radar ~103
List Robinhood Chain tokens right now: `new` gives the latest Pons v2 launches (age, curve progress, market cap), `trending` gives the most traded tokens over 24h (volume, liquidity, buys and sells, change). Use it to find tokens, then scan_token to read one in depth.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many tokens, 5 by default. |
| list | string | yes | Which list to read. |
No output schema declared.
No examples provided.
scan_token ~96
Read a Robinhood Chain token right now: name, supply, owner powers, Pons v2 launch and graduation, creator tax, price, market cap, liquidity, 24h volume, buys and sells, deployer share and burned share. Every key carries its unit. Use it whenever the user mentions a token contract address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The token contract address: 0x followed by 40 hex characters. |
No output schema declared.
No examples provided.
trace_wallet ~113
Read the wallet behind a Robinhood Chain token: how many tokens it launched through the Pons v2 factory in the last hours, how many graduated, how many are still on a curve, and whether it bought or sold on its own curves. Use it when the user asks who is behind a token, or about a deployer.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | How far back to look, 24 by default. |
| wallet | string | yes | The wallet address: 0x followed by 40 hex characters. |
No output schema declared.
No examples provided.
What is the qpon.arctic/arctic MCP server?
qpon.arctic/arctic is an MCP server listed in the public MCP registry as qpon.arctic/arctic. Read Robinhood Chain live: scan a token, trace its deployer, list new launches. This page covers its hosted endpoint (https://www.arctic.qpon/api/mcp).
Is the qpon.arctic/arctic MCP server safe to use?
qpon.arctic/arctic 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 qpon.arctic/arctic MCP server expose?
qpon.arctic/arctic exposes 3 tools: scan_token, trace_wallet, robinhood_radar. Their descriptions and schemas cost roughly 312 tokens of context every time the server is loaded.
Does the qpon.arctic/arctic MCP server require authentication?
No. We connected to qpon.arctic/arctic without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the qpon.arctic/arctic MCP server still maintained?
qpon.arctic/arctic is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.