chain-of-title
Registry code: 3e0c63218968e8b2
Chain of Title is a register of Solana token launches recorded at creation, with the launch document and artwork hashed at capture. Responses state observations from the record with the transaction or hash behind them, never a verdict: there are no scores, no grades and no advice here. A launch the register did not observe returns a not-observed result, which records the absence of an observation and is not a statement that the launch is safe. Each record in a response carries a citation URL for the underlying record, so the figures can be checked at the source.
- endpoint
- https://chainoftitle.org/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is chain-of-title live?
- Yes — it answered the hub's last check (checked 5h ago). It answered 96% of checks over the last 30 days.
- Is chain-of-title free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does chain-of-title have?
- 3 tools: search_ticker_or_name, lookup_launch, archive_status.
- Is chain-of-title safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 97.4%· all time 97.4%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· HTTP 502
- degraded → live
- topic
- crypto & onchain tokens & nft
- used for
- look up a solana token launch record
- search launches by ticker or name
- get register coverage figures
- takes → gives
- text → data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
archive_status reads open 23h ago
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.
{ "type": "object", "properties": {} }arguments 4 linessearch_ticker_or_name reads unknown 23h ago
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.
{ "type": "object", "required": [ "kind", "value" ], "properties": { "kind": { "enum": [ "ticker", "name" ], "type": "string", "description": "Search by ticker symbol or by launch name" }, "value": { "type": "string", "description": "The ticker (e.g. PNUT) or the exact launch name" } } }arguments 21 lineslookup_launch reads unknown 23h ago
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.
{ "type": "object", "required": [ "mint" ], "properties": { "mint": { "type": "string", "description": "The token's mint address (base58, 32-44 characters)" } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id3e0c63218968e8b2.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/3e0c63218968e8b2/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/3e0c63218968e8b2?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.