Rootsure · Product and documentation

Register and check files with MCP/API

Start with a non-sensitive file and check how the original is handled.

1. Connect the local server

Use the MCP setup page to obtain the repository, prepare uv and Python 3.12+, and generate configuration with your own directory and API key. The documented connection is local stdio.

2. Register one file

Call certify_document with file_path or content, not both, and store_in_vault=false for hash-only registration. Use a non-sensitive name: MCP adds filename to metadata. Check stored_in_vault and save hash and registered_at; registered is not a confirmed anchor.

3. Inspect the certificate

Call verify_document or get_certificate with the 64-character digest. Pending means anchoring is not confirmed. Review transaction, Merkle root, network and proof before relying on them.

4. Check a copy

Open the record link. Once the certificate is ready, select a copy in the portal; comparison is automatic. Retain the file, approvals and communications too.

Connect MCP ↗

Let's discuss your workflow

Tell us what file you share and who needs to check it. If there was a version disagreement, explain what happened.

Additional context (optional)

Do not include confidential documents, keys or third-party personal data. We will use these details to handle your inquiry. Privacy.