Skip to content

Tools for agents and data workflows

Run local CLIs, connect MCP servers or call HTTP APIs. Find tools by the job, how you get access and where they run.

Access and setup

Use open-source tools to inspect files and retain evidence, free services to check supported claims and read public data, or hosted MCP servers and APIs with access arranged through CMD+RVL. The separate KYC HTTP API supports pay-per-screen access.

What do you need to do?

Start with a task, then check the tool's inputs, access requirements and setup guide.
Open source · Run locally

Inspect and compare local files

Choose a CLI to inventory files, hash artifacts, compare CSVs or seal evidence. Each README explains supported inputs and outputs.Browse local file tools
Open source · Local MCP

Test an agent against local twins

Use Twinning's stdio MCP manager to rehearse declared Postgres and REST contracts locally, then inspect results and refusals.Set up Twinning
Request access · Hosted MCP

Find data and retained news

Use Loom's catalog, data and evidence tools to find datasets and their source trails. News is joining the stack with retained commercial-real-estate and data-center coverage; publisher article text is withheld by default.Browse discovery MCP servers
$1 per screen · No account required

Screen a company and its people

Screen one company and up to three people over HTTP using Stripe MPP, then retrieve findings, sources and a PDF. No Cairn account or API key is required.Read the KYC API guide
Free · No key required

Check claims against SEC filings

Use Receipts MCP to check supported CMBS claims against current SEC filings. Results include citations and identify the text the server could not check.Connect Receipts MCP
Request access · API key required

Find SEC filing records

Query filing metadata by company, form type and date through EDGAR MCP. Arrange API-key access for your MCP client before connecting.Request EDGAR MCP access
Setup guide · Configure your receiver

Receive outcome changes by webhook

Follow the webhook guide to receive state-transition notifications in a local service or internal workflow, with a JSON payload and attached evidence record.Read the webhook quickstart
Free · Upload and contact form

Extract Power BI model lineage

Upload a whole PBIX file to a hosted Lambda analyzer for model structure, DAX, M code and lineage metadata. A contact-details form unlocks the full report.Try the PBIX lineage extractor
Free · Public JSON

Read machine-readable facts

Read structured-finance facts, outcome definitions and glossary terms as JSON, with source references for citation.View machine-readable data

How Cairn works

Cairn uses context, connections and procedures to work with records and build useful software. Open a part of the stack to see the tools that contribute to it.

Business memory · Internal context

Prior conversations, decisions and work provide context for subsequent work.

This explains Cairn's internal context. It is not a public memory endpoint or access to another customer's records.

AI connectors (14 tools)

Interfaces that let agents find records, ask questions and inspect results.

Each connection has its own access, coverage and supported operations.

Playbooks (2 tools)

Procedures that guide a specific job and explain how to interpret its results.

A procedure does not make every tool combination an implemented integration.

Software factory (22 tools)

Tools for inspecting inputs, testing behavior, applying checks and packaging work.

Each tool establishes only the properties its documented checks cover.

Public records library (9 tools)

Collected public records and the services used to discover and read them.

Coverage, dates and permissions belong to the source and service, not the entire library.

A tool can contribute to several parts of Cairn. These roles describe its documented contribution, not a complete pipeline or a promise that every result has a receipt. Access and availability are listed separately.

What supports the answer

What supports the answer

Start with the question you would ask before relying on a result. A tool may help with several questions; its own coverage and checks determine what it can establish.

Where did this come from? (22 tools)

Identify the records or inputs used for a result.

Where is the supporting evidence? (7 tools)

Locate a supporting filing, clause, row or other declared source reference. Locator precision varies by tool.

What checks support this result? (18 tools)

Inspect the checks, agreement or assessment supporting a result. These are not a shared confidence score or certification.

What could not be established? (16 tools)

Read coverage limits, unresolved matches, conflicts and refusals.

How can I check this later? (6 tools)

Use retained identifiers, pinned inputs or sealed artifacts where supported. A hash establishes byte identity, not the truth of a claim.

A tool can contribute to several parts of Cairn. These roles describe its documented contribution, not a complete pipeline or a promise that every result has a receipt. Access and availability are listed separately.

How Cairn works

The field definition changes the answer

A number needs a field, an entity and a reporting period before you can check it. The Receipts examples show why those details belong together.

Source meaning
Receipts checks ending_balance as scheduled trust balance. Finding the claimed amount in another balance column does not verify that field.
Entity identity
Loan 25 is identified within WFCM 2020-C58, not across every deal. The example also fixes the reporting period to October 2026.
Relationships
The note_rate example links the same loan and period to supporting ABS-EE and 10-D filings. Those citations let a reader inspect the records behind the check.

Choose an interface or access model

Open a group to see matching tools and their access requirements. Each link leads to the same product entry below.

Interface

Command-line tool (18)
MCP server (10)
Agent skill (2)
HTTP API (4)
Web tool (1)
Interface unconfirmed (1)

Access

Open source (21)
Free (4)
Request access (9)
  • Reveal MCPRequest access · Access by arrangement
  • Data MCPRequest access · Access by arrangement
  • Evidence MCPRequest access · Access by arrangement
  • GEO MCPRequest access · Access by arrangement
  • EDGAR MCPRequest access · Access by arrangement
  • Vigil MCPRequest access · Access by arrangement
  • Signet MCPRequest access · Access by arrangement
  • News MCPRequest access · Access by arrangement
  • Loom APIRequest access · Access by arrangement
Pay per use (1)
Access unconfirmed (1)

All developer tools

Compare each tool's job, interface, access and setup. Open-source entries link to local tools or agent skills; hosted services have their own access requirements.

MCP servers

Connect Receipts for free, run Twinning locally or request access to a hosted server. News is joining Loom; confirm availability for your account during provisioning.

Local file and evidence tools

Inventory files, compare datasets, resolve identifiers or seal evidence. Choose tools whose documented inputs and outputs fit the task.
vacuum (what's there?) -> hash (prove identity) -> fingerprint (recognize templates) -> lock (pin inputs) -> shape (comparable?) -> rvl (what changed?) -> pack (seal the evidence)
Command-line tool

vacuum

Open source · AvailableRuns locallyEnumerate artifacts into a deterministic, sorted JSONL manifest with file size, modification time and MIME type.
Cairn roles
Software factory
Evidence roles
Source
Contribution
Inventory the files in a declared scope with size, modification time and MIME type.
Limit
A file inventory does not establish the meaning or accuracy of its contents.
View on GitHub
Command-line tool

hash

Open source · AvailableRuns locallyAdd SHA-256 or BLAKE3 byte identity to each artifact in a streamed manifest.
Cairn roles
Software factory
Evidence roles
Later verification
Contribution
Compute content hashes so the same bytes can be identified again.
Limit
Matching hashes establish byte identity, not source authority or factual correctness.
View on GitHub
Command-line tool

fingerprint

Open source · AvailableRuns locallyClassify artifacts using versioned, assertion-based definitions and produce content hashes.
Cairn roles
Software factory
Evidence roles
Checks and support
Semantic context
Source meaning
Contribution
Recognize artifact templates using versioned definitions and declared assertions.
Limit
A recognized template does not validate every value in the artifact.
View on GitHub
Command-line tool

profile

Open source · AvailableRuns locallyDraft and freeze column and key configuration for reports, with deterministic key suggestions and schema linting.
Cairn roles
Software factory
Evidence roles
Checks and support
Semantic context
Source meaning
Contribution
Declare columns and keys for report interpretation and check the configuration's schema.
Limit
Suggested keys and configured fields still need review against the source.
View on GitHub
Command-line tool

lock

Open source · AvailableRuns locallyPin artifacts, fingerprints and tool versions in a self-hashed, tamper-evident snapshot you can reproduce. Use lock verify to check its integrity.
Cairn roles
Software factory
Evidence roles
Source, Later verification
Contribution
Pin artifacts, fingerprints and tool versions in a snapshot whose integrity can be checked.
Limit
Pinning inputs preserves their identity; it does not prove they are correct.
View on GitHub
Command-line tool

shape

Open source · AvailableRuns locallyCheck whether two CSV datasets can be compared: schema overlap, usable keys, row granularity and consistent types.
Cairn roles
Software factory
Evidence roles
Checks and support, What is missing
Semantic context
Source meaning
Contribution
Check schema overlap, keys, row grain and types before comparing CSV datasets.
Limit
Structural comparability does not establish that differently named business concepts mean the same thing.
View on GitHub
Command-line tool

rvl

Open source · AvailableRuns locallyFinds the smallest set of numeric changes that explains the difference between two CSV files. Ranks explanations using declared tolerances and returns REAL CHANGE, NO REAL CHANGE, or REFUSAL.
Cairn roles
Software factory
Evidence roles
Checks and support, What is missing
Semantic context
Source meaning
Contribution
Explain numeric differences between comparable CSVs under declared tolerances, or refuse the comparison.
Limit
A numeric explanation does not establish the business cause of a change.
View on GitHub
Command-line tool

canon

Open source · AvailableRuns locallyDeterministic entity resolution. Resolves identifiers against versioned registries with a reviewable source trail.
Cairn roles
Software factory
Evidence roles
Source, Checks and support
Semantic context
Entity identity, Relationships
Contribution
Resolve identifiers through versioned registries with a reviewable source trail.
Limit
Resolution is bounded by the configured registry; it is not universal entity matching.
View on GitHub
Command-line tool

pack

Open source · AvailableRuns locallySeal lockfiles, reports and tool outputs in one immutable, content-addressed evidence pack with a self-hashed manifest. Use pack verify to check its integrity.
Cairn roles
Software factory
Evidence roles
Source, Later verification
Contribution
Seal selected inputs and results in a content-addressed evidence pack with an integrity check.
Limit
Pack integrity does not certify the truth of the enclosed results.
View on GitHub

Validation and policy tools

Check constraints, score extraction results or apply a declared policy to evidence.

Agent controls and local workflows

Open-source tools and skills for local workflows. Source availability does not include hosted data access.
Command-line tool

airlock

Open source · AvailableRuns locallyRecord the prompt payload and upstream artifacts sent across a model boundary in an attestation manifest.
Cairn roles
Software factory
Evidence roles
Source
Contribution
Record prompt payloads and upstream artifacts sent across a model boundary.
Limit
An attestation records what was sent; it does not establish that the model's response is correct.
View on GitHub
Command-line tool

veil

Open source · AvailableRuns locallyGuard supported sensitive-file reads into agent context using local hooks, explicit grants and structured refusals.
Cairn roles
Software factory
Evidence roles
What is missing
Contribution
Apply explicit grants and refusals to supported sensitive-file reads into agent context.
Limit
This is an access control, not a claim-verification service or a guarantee covering every data path.
View on GitHub
Command-line tool

decoding

Open source · AvailableRuns locallyReconcile bounded claims under a declared policy, emit canonical entries and send unresolved conflicts to an explicit review queue.
Cairn roles
Software factory
Evidence roles
Checks and support, What is missing
Semantic context
Source meaning
Contribution
Reconcile bounded claims under a declared policy and send unresolved conflicts for review.
Limit
A canonical entry reflects the stated policy and evidence, not an automatically established ontology truth.
View on GitHub
Command-line tool

regret

Open source · AvailableRuns locallySurface reverts and linked fixes from Git history, ranked with the evidence connecting a change to a later correction.
Cairn roles
Software factory
Evidence roles
Source, Checks and support
Semantic context
Relationships
Contribution
Link changes in Git history to observed reverts and fixes for review.
Limit
A linked correction is evidence about that history, not proof that every similar change is wrong.
View on GitHub
Command-line tool

EDGAR Fabric Ingest

Open source · AvailableRuns locallyFetch SEC filings and emit fabric command JSON with provenance for local processing or a configured ingest workflow.
Cairn roles
Software factory, Public records library
Evidence roles
Source
Contribution
Fetch SEC filings and retain provenance in commands for a configured ingest workflow.
Limit
Acquisition does not establish filing accuracy or prove that a downstream ingest completed.
View on GitHub
Command-line tool

XBRL Early Warning

Open source · AvailableRuns locallyDetect supported iXBRL fragility patterns with Arelle and produce a reproducible evidence pack plus machine-readable findings.
Cairn roles
Software factory
Evidence roles
Checks and support, Later verification
Semantic context
Source meaning
Contribution
Check supported iXBRL fragility patterns and package reproducible findings.
Limit
Findings cover the implemented patterns, not every filing defect or regulatory conclusion.
View on GitHub
Agent skill

Receipts skills

Open source · AvailableRuns locallyTurn a pair of comparable CSVs into a sealed receipt using the shape, rvl and pack tools, with evidence that can be verified offline.
Cairn roles
Playbooks, Software factory
Evidence roles
Checks and support, What is missing, Later verification
Semantic context
Source meaning
Contribution
Guide a local CSV comparison through shape, rvl and pack to produce a sealed receipt.
Limit
This local workflow is separate from hosted Receipts MCP and requires comparable inputs.
View on GitHub

HTTP APIs

Read public facts and directory records, use pay-per-screen KYC, or arrange access to the hosted conversational API.
HTTP API

DealCharts API

Free · AvailableHosted serviceRead public filing-derived facts, search results, dataset metadata and material-change feeds over HTTP/JSON without an account or key.
Cairn roles
AI connectors, Public records library
Evidence roles
Source
Semantic context
Source meaning
Contribution
Read filing-derived facts and dataset metadata through public HTTP endpoints.
Limit
Check each dataset's source and period; API access is not verification of every returned fact.
Read the DealCharts API guide
HTTP API

TrancheList API

Free · AvailableHosted serviceRead the curated structured-finance vendor directory as paginated HTTP/JSON. Listings support market research and do not certify a vendor's current capability.
Cairn roles
AI connectors
Evidence roles
Source
Contribution
Read a curated structured-finance vendor directory through HTTP.
Limit
A directory listing does not certify a vendor's current capability or suitability.
View the public listings API

Developer questions

What developer tools does CMD+RVL offer?

The directory covers local CLIs and agent skills, MCP servers, HTTP APIs and the PBIX web tool. It includes open-source projects, free public services, hosted services with arranged access and the pay-per-screen KYC API. Setup guides cover webhook delivery and machine-readable data.

Which tools need an account or key?

Open-source tools run locally. Receipts MCP and the public JSON APIs need no key. The keyed hosted MCP servers and Loom require access arranged with CMD+RVL; self-service registration is not available. The KYC API uses per-screen payment. The PBIX full report collects contact details.

Can an agent use KYC screening without signing up?

Yes. The standard HTTP API accepts one company and up to three named people for $1 per completed screen through Stripe MPP. Pay with a card through Link or USDC on Tempo, then retrieve structured findings, sources and a PDF. No Cairn account or API key is required. The KYC API guide explains supported coverage, payment and asynchronous results; custom scope is agreed separately through Hire Cairn.

How do developers use CMD+RVL with SEC EDGAR data?

Arrange API-key access to EDGAR MCP, then use the setup guide to query filing metadata from Claude, Codex or another MCP-compatible client. The open-source EDGAR Change Interpreter is a separate agent skill for filing review.

Why is the Kovrex listing marked unconfirmed?

We have not confirmed its current capability, access or availability. The archived rvl-kovrex repository is not evidence of a current hosted offer. Contact CMD+RVL before relying on the third-party listing.

What makes these developer workflows auditable?

Use each tool's documented schemas, content hashes, lockfiles, witness records and evidence packs to trace results back to inputs. These record provenance and integrity; inspect the source evidence before treating a result as fact.

Built in the open

Protocol tools, public examples, and source-verifiable workflow utilities live on GitHub.Browse CMD+RVL on GitHub