Terminal 7
REMOTE · API.TERMINAL7.XYZ
Signals, scores and payout data for stonkfun coins on Solana, for bots and AI agents.
Available components
Last scanned (2 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 23 Oct 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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability63
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 473 tokens (~67/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
- 78% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 22 Oct 26 0
- Tool coverage: 100% → 78% ▼ functional
- Schema quality: 272 → 473 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “get_coins” functional
- New tool “get_launches” functional
- New tool “get_mood” functional
- 21 Oct 26 +40
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 20 Oct 26 28
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 23 Oct 2026 · Probed https://api.terminal7.xyz/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=terminal7.xyz | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c18306998814b320134d93a0c681fc42 |
| SANs: terminal7.xyz, api.terminal7.xyz, *.api.terminal7.xyz | ||||||
| CN=WE1,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 | 7ff31977972c224a76155d13b6d685e3 |
| 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 api.terminal7.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| terminal7.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.terminal7.xyz/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.terminal7.xyz/v1/mcp | Inconclusive | 401 |
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 →
get_coin ~59
Everything T7 scores on one coin: REAL score and call, compound or conviction, payout APY / paid / last payout, market, launch radar, TOP 10 rank, recent signals.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | the coin's mint address |
No output schema declared.
No examples provided.
get_coins ~65
Every coin T7 scores in one list, biggest first: REAL score and call, compound, conviction, payout APY, market cap, holders. Paged.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | free 100, paid 500 a page |
| offset | integer | – | – |
No output schema declared.
No examples provided.
get_launches ~93
New stonkfun launches from T7's launch radar, newest first: score and call (REAL / WATCH / THIN / FARM), market cap, peak, holders, liquidity, flags; and the newest pairs (quote assets).
| Name | Type | Req | Description |
|---|---|---|---|
| call | string | – | only this call, e.g. REAL |
| limit | integer | – | default 50, max 200 |
| min_score | integer | – | – |
No output schema declared.
No examples provided.
get_mood ~43
The meme market mood for stonkfun coins (0-100: cold under 40, hot 60+), its parts and 7 days of hourly history.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_signals ~101
Signal families (radar, holders, chart, scores, kols, flow, rising, combo) firing on stonkfun coins, and the T7 bot's paper buys / sells, oldest first, with unix times.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | at most this many (default 200, max 500) |
| mint | string | – | only this coin (its mint address) |
| since | integer | – | unix seconds: only newer events |
No output schema declared.
No examples provided.
get_top ~38
The coins the most T7 signal families agree on now (the TOP 10), with market cap, 24 h change, holders, liquidity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_usage ~16
This key's plan and requests today.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Terminal 7 MCP server?
Terminal 7 is a hosted endpoint at https://api.terminal7.xyz/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.terminal7.xyz
claude mcp add --transport http linkmarine777-terminal7 'https://api.terminal7.xyz/v1/mcp'
What is the Terminal 7 MCP server?
Terminal 7 is an MCP server listed in the public MCP registry as io.github.LinkMarine777/terminal7. Signals, scores and payout data for stonkfun coins on Solana, for bots and AI agents. This page covers its hosted endpoint (https://api.terminal7.xyz/v1/mcp).
Is the Terminal 7 MCP server safe to use?
Terminal 7 scores 68 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 Terminal 7 MCP server expose?
Terminal 7 exposes 7 tools: get_signals, get_top, get_coin, get_usage, get_launches, and 2 more. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.
Does the Terminal 7 MCP server require authentication?
Yes. Terminal 7 asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Terminal 7 MCP server still maintained?
Terminal 7 is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.