Chain of Title

org.chainoftitlePublished by chainoftitle.orgOfficial publisherv1.0.0Updated Oct 24, 2026

Solana launches recorded at creation: what each claimed, hashed. Observations, never verdicts.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

A remote MCP server that records Solana token launches at creation time, capturing what each project claimed and hashing it.

What you can do
Chain of Title is a remote MCP endpoint that records Solana token launches at the moment of creation, preserving what each project claimed and storing a hash of that record. Its stated stance is to provide observations rather than verdicts, so it presents recorded launch data instead of judgments or ratings. The manifest lists no tools, so the exact callable surface is not documented here.
When to use it
Worth considering when an assistant needs a timestamped, hashed record of what a Solana token project claimed at launch, for example to compare early claims against later information. It is not a general Solana data or trading tool.
Requirements
A remote streamable HTTP endpoint at the provider's site; no package installation. The manifest declares no authentication, environment variables, or headers, so no credentials appear to be required.
Before you install
The description is very short and no tool list or README is provided, so verify what data is returned and whether any calls write or submit anything before relying on it. The server records claims made by third parties; a recorded claim is not a verification of accuracy.

Installation

In SourceWeft

  1. Open Chain of Title in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.chainoftitle%2Fchain-of-title/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "chain-of-title": {
      "type": "http",
      "url": "https://chainoftitle.org/mcp"
    }
  }
}

Tools

3

lookup_launch

Look up a launch

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.

Parametersmintrequired

search_ticker_or_name

Search a ticker or name

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.

Parameterskindrequiredvaluerequired

archive_status

Archive coverage

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.

Takes no parameters.

Version history

1
  1. v1.0.0LatestOct 1, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.