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.

Cluster & Consensus

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

Tracked-wallet cluster detection + 0-100 consensus score for Solana/Base tokens. $0.02/call.

71 Trust /100

Last scanned (18 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 Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 799 tokens (~199/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 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 4 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
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.

  • 19 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.

  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 70

    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://cluster-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 cluster-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://cluster-al6bxcngia-ue.a.run.app/mcp Verified 200
http (plaintext) http://cluster-al6bxcngia-ue.a.run.app/mcp HTTPS enforced 302 https://cluster-al6bxcngia-ue.a.run.app/mcp
MCP tools · 4 exposed · ~799 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
cluster_check ~431

Full cluster & consensus report for ONE token (Solana mint or Base contract address; chain auto-detected). Detects whether tracked smart-money wallets are converging on the token in the last 24h: tracked buyer/seller counts, per-wallet cluster events (side, tx count, estimated USD, first/last seen), tracked net USD flow, tracked wallets sitting in the top-holder list, and a 0-100 consensus score with a STRONG / FORMING / QUIET / EXITING signal and a stated confidence. Fuses a safety summary (RugCheck on Solana, GoPlus on Base) and a canonical check: for tokens trading on a registered narrative name (NEET at launch) it states CANONICAL or CLONE and names the real contract — ticker copies are industrial-scale and resolving the real one is the toll. FAIL-CLOSED AND HONEST ABOUT COVERAGE: Solana cluster detection is sample-based (a bounded sample of recent main-pool transactions intersected with the tracked set); every report states signatures seen, transactions parsed and the sample span, and missing sources cap confidence and are named in data_gaps — a consensus score is only produced when real cluster data answered. Base support is holder-overlap plus a bounded transfer-log scan and is labelled a weaker signal. The tracked set is derived from public data (repeat cross-token buyers on public RPC flow + GoPlus holder lists), shipped as data and rebuildable. Cost: $0.02 USDC per call via x402 (Base settlement; Solana settlement when configured) — no API key needed. Use it before apeing into any social-driven token: are the wallets that matter already in, still entering, or leaving?

NameTypeReqDescription
addressstringyesToken address: a Solana mint (base58, e.g. Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump) or a Base contract (0x-prefixed, 40 hex chars). Chain is auto-detected from the format.

No output schema declared.

No examples provided.

cluster_check_lite ~154

FREE lite cluster & consensus report for one token (Solana mint or Base contract). Top-line only: consensus score, signal, tracked buyer/seller counts, tracked net USD, canonical status and the safety band — events, holder overlap and coverage detail are capped. Use it to triage whether a token deserves the full cluster_check report.

NameTypeReqDescription
addressstringyesToken address: a Solana mint (base58, e.g. Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump) or a Base contract (0x-prefixed, 40 hex chars). Chain is auto-detected from the format.

No output schema declared.

No examples provided.

cluster_feed ~156

Full cluster board: the tokens with ACTIVE tracked-wallet cluster events right now, ranked by consensus score. Candidates come from DexScreener's public attention feeds (boosts + latest profiles, Solana) plus registered narrative canonicals; each candidate is cluster-scanned live and only tokens with real tracked-wallet activity make the board. Per token: consensus score, signal, tracked buyers/sellers, tracked net USD, safety band, canonical status. An empty board is a real answer — it means no cluster events were detected in the current candidate set, not an error. This is the in-loop product: poll it to catch convergence as it forms. Cost: $0.02 USDC per call via x402 — no API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cluster_feed_lite ~58

FREE lite cluster board: tokens with active cluster events right now (address, symbol, consensus score, signal, tracked buyer count only — net flow, sellers, safety and canonical detail are capped). The full cluster_feed board adds the detail.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Cluster & Consensus MCP server?

Cluster & Consensus is a hosted endpoint at https://cluster-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 · cluster-al6bxcngia-ue.a.run.app

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

What is the Cluster & Consensus MCP server?

Cluster & Consensus is an MCP server listed in the public MCP registry as io.github.theharrisontruong-web/cluster. Tracked-wallet cluster detection + 0-100 consensus score for Solana/Base tokens. $0.02/call. This page covers its hosted endpoint (https://cluster-al6bxcngia-ue.a.run.app/mcp).

Is the Cluster & Consensus MCP server safe to use?

Cluster & Consensus 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 Cluster & Consensus MCP server expose?

Cluster & Consensus exposes 4 tools: cluster_check, cluster_check_lite, cluster_feed, cluster_feed_lite. Their descriptions and schemas cost roughly 799 tokens of context every time the server is loaded.

Does the Cluster & Consensus MCP server require authentication?

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

Is the Cluster & Consensus MCP server still maintained?

Cluster & Consensus 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 Cluster & Consensus MCP server?

VerifyMCP ran 13 checks on Cluster & Consensus, 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.