Token Pressure + Holder Health
REMOTE · PRESSURE-AL6BXCNGIA-UE.A.RUN.APP
Buying-pressure ladder + holder health for Solana memecoins. $0.02/call via x402.
Available components
Last scanned (17 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 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 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 624 tokens (~312/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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 →
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.
- 21 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.
- 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.
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://pressure-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 pressure-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://pressure-al6bxcngia-ue.a.run.app/mcp | Verified | 200 | |
| http (plaintext) | http://pressure-al6bxcngia-ue.a.run.app/mcp | HTTPS enforced | 302 | https://pressure-al6bxcngia-ue.a.run.app/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 →
token_pressure ~432
Full buying-pressure + holder-health report for ONE Solana memecoin (mint address in). BUYING PRESSURE: deterministic constant-product math on live pool reserves — the exact net quote inflow that moves the price to 1.5x, 2x, 3x, 5x, 10x, 25x, 50x and 100x, with target prices and target market caps, plus the gross inflow after the venue fee. Works for pump.fun bonding curves (virtual reserves read from the curve account, pre-graduation), PumpSwap and Raydium constant-product pools; concentrated pools (CLMM/DLMM) are reported unavailable with the reason, never approximated. HOLDER HEALTH: cost basis reconstructed from public chain history over a bounded top-holder sample (pool vaults excluded) — total unrealized PnL, percent of sampled wallets in profit, supply-weighted average cost, MVRV, UPNL vs liquidity, per-holder detail, and the sample coverage (% of supply) stated up front. Includes a canonical-contract check for tracked narratives (NEET at launch): clones trading on the name are flagged and the real contract named. Every report carries its methodology (pool type, reserves snapshot slot, fee assumption, holder sample bounds) and names its data gaps — figures that cannot be computed from public state are reported unavailable, never estimated. Cost: $0.02 USDC per call via x402 (Base settlement; Solana settlement when configured) — no API key needed. Use it to answer 'how much money has to arrive for this to 2x / 10x, and are the holders sitting on profit or underwater?' before sizing into any Solana memecoin.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint address (base58, 32-44 chars), e.g. Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump. EVM 0x addresses are rejected — this is a Solana tool. |
No output schema declared.
No examples provided.
token_pressure_lite ~192
FREE lite buying-pressure + holder-health report for one Solana memecoin. Top-line only: net inflow needed for 2x, 5x and 10x moves, percent of sampled wallets in profit, total unrealized PnL headline, weighted average cost, MVRV and sample coverage. The full ladder (1.5x-100x), gross-of-fee figures, reserves, UPNL vs liquidity and per-holder detail are capped. Use it to triage whether a token deserves the full token_pressure report.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint address (base58, 32-44 chars), e.g. Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump. EVM 0x addresses are rejected — this is a Solana tool. |
No output schema declared.
No examples provided.
How do I install the Token Pressure + Holder Health MCP server?
Token Pressure + Holder Health is a hosted endpoint at https://pressure-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 · pressure-al6bxcngia-ue.a.run.app
claude mcp add --transport http theharrisontruong-web-pressure 'https://pressure-al6bxcngia-ue.a.run.app/mcp'
What is the Token Pressure + Holder Health MCP server?
Token Pressure + Holder Health is an MCP server listed in the public MCP registry as io.github.theharrisontruong-web/pressure. Buying-pressure ladder + holder health for Solana memecoins. $0.02/call via x402. This page covers its hosted endpoint (https://pressure-al6bxcngia-ue.a.run.app/mcp).
Is the Token Pressure + Holder Health MCP server safe to use?
Token Pressure + Holder Health 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 Token Pressure + Holder Health MCP server expose?
Token Pressure + Holder Health exposes 2 tools: token_pressure, token_pressure_lite. Their descriptions and schemas cost roughly 624 tokens of context every time the server is loaded.
Does the Token Pressure + Holder Health MCP server require authentication?
No. We connected to Token Pressure + Holder Health without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Token Pressure + Holder Health MCP server still maintained?
Token Pressure + Holder Health 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 Token Pressure + Holder Health MCP server?
VerifyMCP ran 13 checks on Token Pressure + Holder Health, 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.