TokenOS Token Launch Planner
REMOTE · TOKENOS.AI
Plan a Solana token launch
Available components
Last scanned (22 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 4 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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 313 tokens (~104/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% 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 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
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.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://tokenos.ai/api/mcp/apps/token-launch-planner
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tokenos.ai | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b91e1ad31864bf7c0e7379d501820fce |
| SANs: tokenos.ai | ||||||
| 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 tokenos.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| tokenos.ai. | 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; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tokenos.ai/api/mcp/apps/token-launch-planner | Verified | 200 | |
| http (plaintext) | http://tokenos.ai/api/mcp/apps/token-launch-planner | HTTPS enforced | 301 | https://tokenos.ai/api/mcp/apps/token-launch-planner |
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 →
compare_launch_platforms Compare launch platforms ~43
Compare Pump.fun (Solana), pons (Robinhood Chain) and a plain SPL mint: wallet, cost, bonding curve and graduation, speed, audience.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_token_launch Plan a token launch ~145
Produce a step-by-step launch plan for a token: costs, preparation, launch steps, checklist, pitfalls and a link to the launch documentation.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | solana = Pump.fun (default); robinhood = Robinhood Chain via pons |
| goal | string | – | What the token is for (default project) |
| has_logo | boolean | – | True if a logo already exists |
| name | string | yes | Token name, e.g. Moon Cat |
| socials | array | – | Existing social links (X, Telegram, Discord, website) |
| symbol | string | yes | Ticker, 2–10 chars, e.g. MCAT |
No output schema declared.
No examples provided.
token_launch_costs Estimate launch cost ~54
Estimate the total cost to launch a token on Solana or Robinhood Chain, including an optional initial buy.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| initial_buy | number | – | Optional initial buy in SOL or ETH |
No output schema declared.
No examples provided.
How do I install the TokenOS Token Launch Planner MCP server?
TokenOS Token Launch Planner is a hosted endpoint at https://tokenos.ai/api/mcp/apps/token-launch-planner, 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 · tokenos.ai
claude mcp add --transport http ai-tokenos-token-launch-planner 'https://tokenos.ai/api/mcp/apps/token-launch-planner'
What is the TokenOS Token Launch Planner MCP server?
TokenOS Token Launch Planner is an MCP server listed in the public MCP registry as ai.tokenos/token-launch-planner. Plan a Solana token launch. This page covers its hosted endpoint (https://tokenos.ai/api/mcp/apps/token-launch-planner).
Is the TokenOS Token Launch Planner MCP server safe to use?
TokenOS Token Launch Planner scores 89 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 TokenOS Token Launch Planner MCP server expose?
TokenOS Token Launch Planner exposes 3 tools: plan_token_launch, compare_launch_platforms, token_launch_costs. Their descriptions and schemas cost roughly 242 tokens of context every time the server is loaded.
Does the TokenOS Token Launch Planner MCP server require authentication?
No. We connected to TokenOS Token Launch Planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TokenOS Token Launch Planner MCP server still maintained?
TokenOS Token Launch Planner is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.