Run this in a terminal where the Codex CLI is installed. The CLI and IDE extension share this configuration.
codex mcp add chainsourced --url https://chainsourced.com/mcpOpenAI setup reference ↗ChainSourced connects reviewed public addresses and accounts to entities, with the relationship and primary-source evidence returned together.
https://chainsourced.com/mcpStreamable HTTP · Read-only tools · Authorization may be requested by your client
Connect this remote MCP server to Codex, ChatGPT, or Claude. Use the same endpoint in each client; follow its setup path below.
Run this in a terminal where the Codex CLI is installed. The CLI and IDE extension share this configuration.
codex mcp add chainsourced --url https://chainsourced.com/mcpOpenAI setup reference ↗Use the ChainSourced listing to connect the MCP server in ChatGPT. Check the listing's current availability and follow any workspace controls.
View ChainSourced in ChatGPT ↗In Claude, open Settings → Connectors → Add custom connector. Name it ChainSourced and paste the endpoint above.
claude mcp add --transport http chainsourced https://chainsourced.com/mcpClaude remote MCP guide ↗These counts describe the published, reviewed index. They do not describe every entity, address, network, or relationship that exists.
Search results are evidence-linked relationships between public entities, blockchain addresses, and public accounts such as domains or repository namespaces.
An empty result means “no reviewed mapping in this index.” It does not prove that an address has no relationship elsewhere.
Use get_coverage for the current snapshot. Each result includes its recorded relationship and source link for independent inspection.
Additional tools may return approved cached contract metadata and chain observations with source, block, age, and coverage details. A published artifact does not establish ownership, deployed bytecode, or contract safety.
Each relationship links to its primary evidence. Archived notices below preserve license terms for source materials; their presence does not mean every source candidate is published.
A deployment listing, website, or repository may establish a specific public relationship. It does not establish personal wallet ownership, current control, endorsement, bytecode verification, or contract safety.
The registry has limited coverage. Rights changes, source withdrawals, or review can change which records are published. Check the primary source and date before relying on a result.
Choose a client after connecting and ask for a lookup with its exact chain or public account identifier.
“What reviewed relationship is recorded for this Ethereum address? Show the source.”
“Find Safe in the reviewed index and list its recorded addresses and public accounts with source links.”
Available tools include lookup_address, lookup_account, search_entities, get_entity, and get_coverage, get_observation_coverage, get_contract_metadata, and get_onchain_snapshot, and list_address_transactions. Use the live server to inspect its current tool list.