MCP and API for your agents

Your agent records the file. You share the reference.

Integrate our MCP server or API with your system or agents.

Registration returns a reference. The certificate may still be in preparation.

Two connection paths

Choose how to connect Rootsure

With an API key

Available now

For agents and processes running in your own infrastructure. Use local MCP in Cursor or Claude Desktop, or integrate the API into your backend to automate file registration and lookup.

Where to use it

Cursor · Claude Desktop · Backends and automations

Configure local MCP View the API →

With OAuth

Coming soon

Connect your account from cloud interfaces without copying an API key. This is the path we are preparing for ChatGPT and other compatible remote MCP clients.

Intended use · not yet available

ChatGPT · Cloud MCP clients

Set up your connection

Your checkout. Your key. Your environment.

You need uv, Python 3.12 or later and access to the server repository. This configuration runs the local code; it does not depend on a published PyPI package.

01 · Prepare

Install uv. Get rootsure-mcp.

git clone https://github.com/rootsure/rootsure-mcp.git
cd rootsure-mcp
uv sync

02 · Create key

Create account ↗ · Open API keys in the portal ↗. Sign in and create a key for this integration. Confirm that your plan supports hash registration.

03 · Connect

Generate configuration and add it to .cursor/mcp.json or claude_desktop_config.json. If you already have other servers, add only the rootsure entry to mcpServers. Restart the client.

This configuration runs a local stdio process; it does not create a multi-user cloud endpoint. The reviewed public CLI has stdio logging and shutdown issues: let's review the integration before production.

Tool contract

Four actions, with explicit states.

Contract reviewed against public sourceb22afa7.Check your checkout version and compatibility before integrating it.

`certify_document`

Accepts file_path or content. Hash-only registration requires store_in_vault=false and a compatible plan. Without that parameter, it can upload the original if the plan requires a vault; true requests upload. The initial response is registered, pending anchoring.

`verify_document`

Looks up a document_hash of 64 hexadecimal characters. No account required; returns the state reported by the backend.

`get_certificate`

Looks up the same digest and returns available registration, batch and transaction data. A pending certificate is not a confirmed proof.

`list_certified_documents`

Lists your account's records with date filters and pagination. Requires an API key.

How it works

Select. Share. Check.

Select the file

Get a reference

Get a reference with a registration date and a link to share. The certificate may still be in preparation.

Check a copy

Once the certificate is ready, the recipient opens the link and selects their copy. The portal automatically checks whether it matches.

Try an example file.

Ask your agent to register a non-sensitive file and return its link. The calculation is automatic.

Open the link to check the status. Once the certificate is ready, select a copy in the portal to check it.

Check how the original is handled and use names or information you can show publicly.

Look up a record →Read the API documentation →

Choose the integration point

Integration review

Which file should your agent record?

Tell us what your agent produces and who needs to check a copy. Let's discuss the integration.