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.

NEET Radar

REMOTE · NEET-AL6BXCNGIA-UE.A.RUN.APP

NEET narrative radar + canonical-or-clone verify for Solana mints. $0.02 / $0.005 via x402.

71 Trust /100

Last scanned (15 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 Security74
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 715 tokens (~238/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 Management13
  • Stability observed for 4 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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 69

    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 21 Nov 2026 · Probed https://neet-al6bxcngia-ue.a.run.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.a.run.app CN=WE2,O=Google Trust Services,C=US 3 Nov 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 f668c9036838957b095b05d18ab2228d
SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more
CN=WE2,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 7ff32d6b409d15d5965b05873a7c72e0
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 neet-al6bxcngia-ue.a.run.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
run.app. No DS 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://neet-al6bxcngia-ue.a.run.app/mcp Verified 200
http (plaintext) http://neet-al6bxcngia-ue.a.run.app/mcp HTTPS enforced 302 https://neet-al6bxcngia-ue.a.run.app/mcp
MCP tools · 3 exposed · ~715 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
neet_report ~319

Full one-call report on NEET (Solana, canonical mint Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump) for agents acting for NEET holders. Sections, each with its source named: canonical identity verification (registry), market block (price, 24h change, market cap, liquidity, volume — DexScreener), safety summary (RugCheck score, flagged risks, LP lock), cluster and consensus state (are tracked smart-money wallets converging on NEET in the last 24h: consensus score, STRONG / FORMING / QUIET / EXITING signal, tracked buyer and seller counts, net flow, coverage), buying-pressure headline (net inflow needed for 2x / 5x / 10x from live pool reserves, constant-product math), holder-health headline (percent of sampled wallets in profit, total unrealized PnL, weighted average cost, MVRV, sample coverage), and recent CLONE sightings: other Solana mints trading on the NEET name, each marked CLONE with the canonical contract named. Sections degrade independently and honestly: a failed source is named in data_gaps and never blocks the rest. Independent tooling, not affiliated with the NEET token or its team; data only, no predictions or recommendations. Cost: $0.02 USDC per call via x402 (Base settlement; Solana settlement when configured) — no API key needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

neet_report_lite ~95

FREE lite NEET report: price, 24h change, market cap, canonical status, cluster signal and consensus score, safety band, net inflow needed for 2x / 5x / 10x, and the wallets-in-profit headline. Section detail, cluster events, full ladder and clone sightings are capped. Use it to triage whether the full neet_report is worth $0.02.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

neet_verify ~301

Verify any Solana mint against the NEET narrative: returns CANONICAL (it is the real NEET, Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump), CLONE (it trades on the NEET name but is a different contract; the canonical contract is named in the verdict), or NOT_NEET. Registry-driven: registered clones resolve by address even when the token is dead and has no market data. This is the anti-scam check to run before buying, quoting, or routing to anything named NEET: ticker copies are industrial-scale on Solana and at least one aggregator has mislabelled a dead clone as the official contract. Independent tooling, not affiliated with the NEET token or its team. Cost: $0.005 USDC per call via x402 (Base settlement; Solana settlement when configured).

NameTypeReqDescription
mintstringyesAny Solana mint address (base58, 32-44 chars) to check against the NEET narrative, e.g. 9MaKE8AQW2HjsQjLYgvkXc8PEWTQ43t5qj9Gc9VEpump (a known clone) or the canonical Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQ…

No output schema declared.

No examples provided.

Install

How do I install the NEET Radar MCP server?

NEET Radar is a hosted endpoint at https://neet-al6bxcngia-ue.a.run.app/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 · neet-al6bxcngia-ue.a.run.app

# add to Claude Code
claude mcp add --transport http theharrisontruong-web-neet 'https://neet-al6bxcngia-ue.a.run.app/mcp'
Common questions

What is the NEET Radar MCP server?

NEET Radar is an MCP server listed in the public MCP registry as io.github.theharrisontruong-web/neet. NEET narrative radar + canonical-or-clone verify for Solana mints. $0.02 / $0.005 via x402. This page covers its hosted endpoint (https://neet-al6bxcngia-ue.a.run.app/mcp).

Is the NEET Radar MCP server safe to use?

NEET Radar scores 71 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 NEET Radar MCP server expose?

NEET Radar exposes 3 tools: neet_report, neet_report_lite, neet_verify. Their descriptions and schemas cost roughly 715 tokens of context every time the server is loaded.

Does the NEET Radar MCP server require authentication?

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

Is the NEET Radar MCP server still maintained?

NEET Radar 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 NEET Radar MCP server?

VerifyMCP ran 13 checks on NEET Radar, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.