Skip to content

Put a tool to work

Start with one question. Each walkthrough explains the access you need, the inputs to supply, the result to inspect and what that result leaves unresolved.

Find each tool's place in how Cairn works and what supports an answer, or browse the MCP servers.

Single-tool walkthroughs

Connect Receipts MCP

Set up the free claim-checking server, inspect coverage and read supported CMBS results.

Set up EDGAR MCP

Read the filing-metadata connection guide and arrange API-key access for your client.

Run Twinning locally

Install the stdio MCP manager for Postgres and REST twins, then follow the documented setup checks.

Screen a company through the paid KYC API

Read the offer, prepare payment and retrieve a screening result. Paid execution has not been demonstrated in this guide.

Find a table before querying it

Use Reveal to look up a known table and understand what one observation represents.

Query a loan balance

Describe the columns, run a bounded Data query and distinguish reporting dates from filing dates.

Trace a table's lineage

Read upstream dependencies with Evidence and distinguish table lineage from proof of a particular value.

Resolve an address to a census tract

Use GEO to inspect an address match, its tract identifier and the sources used to resolve it.

Receipts is free and needs no key. Twinning runs locally. Reveal, Data, Evidence, GEO and EDGAR need access arranged with CMD+RVL. The separate KYC HTTP API requires payment; its guide documents setup and retrieval, but does not present a completed paid demonstration.

The Reveal, Data, Evidence and GEO examples were run on November 3, 2026. Each guide identifies its observed result and limits. News and Signet have product and access guidance; runnable walkthroughs will follow verified access.

Integration references

Receive webhook notifications

Follow the receiver setup and inspect the documented notification payload and evidence record.

Read the artifact contracts

Look up artifact schemas and examples before passing one tool's output to another.

For client setup and integration choices, see the developer guide. To discuss access or a workflow using several tools, contact us.