Chain of Title
REMOTE · CHAINOFTITLE.ORG
Solana launches recorded at creation: what each claimed, hashed. Observations, never verdicts.
Available components
Last scanned (14 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 17 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 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. 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
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 428 tokens (~142/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 Management57
- Stability observed for 17 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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 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.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “archive_status” rewrote its description, which is the text the model reads security
- Tool “lookup_launch” rewrote its description, which is the text the model reads security
- Tool “search_ticker_or_name” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 33. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 13 to 23. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 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.
- 1 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Sept 26 71
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 17 Oct 2026 · Probed https://chainoftitle.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chainoftitle.org | CN=WE1,O=Google Trust Services,C=US | 6 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ca331c6c1c5467ce0e85ab7406ddde27 |
| SANs: chainoftitle.org, *.chainoftitle.org | ||||||
| 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 chainoftitle.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| chainoftitle.org. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chainoftitle.org/mcp | Verified | 200 | |
| http (plaintext) | http://chainoftitle.org/mcp | HTTPS enforced | 301 | https://chainoftitle.org/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 →
archive_status Archive coverage ~49
The register's own coverage figures: how many launches are on record, since when, from which venues, and what is free versus licensed. The result states the basis for any answer drawn from the register.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_launch Look up a launch ~140
Look up one Solana token launch in the Chain of Title register by its mint address. Returns what was recorded at creation: what the creator took in the first block, who bought the bonding curve, whether the curve completed, what the launch declared about itself as captured at the time, and the finding class - observations only, never a verdict. A launch the register did not observe returns a not-observed result, which records the absence of an observation and is not evidence that the launch is safe. Each result includes a citation URL for the underlying record.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | The token's mint address (base58, 32-44 characters) |
No output schema declared.
No examples provided.
search_ticker_or_name Search a ticker or name ~125
Search the register for every launch that carried a ticker symbol or a launch name. Launch identity is free to copy, so one name is often many mints from many wallets; this returns the count, the wallets behind it and the recent launches, as dated observations. It answers questions such as whether a token by some name has launched before, or how many times a ticker has been reused.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Search by ticker symbol or by launch name |
| value | string | yes | The ticker (e.g. PNUT) or the exact launch name |
No output schema declared.
No examples provided.
How do I install the Chain of Title MCP server?
Chain of Title is a hosted endpoint at https://chainoftitle.org/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 · chainoftitle.org
claude mcp add --transport http org-chainoftitle-chain-of-title 'https://chainoftitle.org/mcp'
What is the Chain of Title MCP server?
Chain of Title is an MCP server listed in the public MCP registry as org.chainoftitle/chain-of-title. Solana launches recorded at creation: what each claimed, hashed. Observations, never verdicts. This page covers its hosted endpoint (https://chainoftitle.org/mcp).
Is the Chain of Title MCP server safe to use?
Chain of Title scores 77 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 Chain of Title MCP server expose?
Chain of Title exposes 3 tools: lookup_launch, search_ticker_or_name, archive_status. Their descriptions and schemas cost roughly 314 tokens of context every time the server is loaded.
Does the Chain of Title MCP server require authentication?
No. We connected to Chain of Title without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Chain of Title MCP server still maintained?
Chain of Title is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.