sigill.ai — Evidence infrastructure for autonomous systems
sigill.ai — Evidence infrastructure for autonomous systems
Cryptographic RFC 3161 timestamping and advanced electronic seals for AI systems, regulated platforms, and software supply chains.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · api.sigill.ai
30tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://api.sigill.ai/mcp
Skill page: https://www.mcpbundles.com/skills/sigill-mcp-389c281084
Explore capabilities (30)
read 17
write 8
Showing 25 of 30
Showing 25 of 30 tools from the public preview. Connect the server to inspect the full live tool list.
Sigill25
Timestamp a hash
write
sigill_stamp
Timestamp a document using RFC 3161. Compute SHA-256 of the file locally and pass the hex digest — the file content never leaves your machine. Returns the transaction ID and TSR. Requires a Sigill API key.
Timestamp a hash — Timestamp a document using RFC 3161. Compute SHA-256 of the file locally and pass the hex digest — the file content never leaves your machine. Returns the transaction ID and TSR. Requires a Sigill API key.
Verify a hash against a timestamp token — Verify that a file's hash matches a Time-Stamp Response (TSR). Call sigill_inspect first to determine the hash algorithm, compute that hash of the file locally, then pass the hex digest. No authentication required.
Inspect a timestamp token — Parse a TSR and return its metadata: serial, timestamp, hash algorithm, hash hex, policy OID, and whether it is eIDAS-qualified. No authentication required.
Look up a public timestamp record — Check whether a document has been timestamped by its SHA-256 hash. Public — no authentication required. Only returns records whose owning organisation allows public existence checks (an opt-in setting, default off); a record whose owner has not opted in answers as not found.
List recent seal operations — List recent document seal operations for your organisation. Requires a Sigill API key.
Show plan and remaining quota — Return the current plan, monthly quota limits, and remaining credits for plain timestamps, qualified (eIDAS) timestamps, and document seals. Call this when the user asks about their plan, quota, remaining stamps, or billing cycle.
List seal certificates — List available seal certificates for your organisation, including the shared platform certificate. Returns certificate IDs for sigill_seal_hash and sigill_seal_objects (detached seals over hashes), and for the web app, HTTP API and SDKs. Seals embedded in a PDF (PAdES) need the document and are not available over MCP — use the SDKs. Requires a Sigill API key or sign-in.
List timestamp authorities — List the timestamp authorities your organisation can choose with sigill_stamp's tsa_slug: qualified (eIDAS) TSAs you are entitled to and your own verified BYOT authorities. "auto" (Sigill-managed standard timestamping) is always available. Requires a Sigill API key or sign-in.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
What is the sigill.ai — Evidence infrastructure for autonomous systems MCP server?
Cryptographic RFC 3161 timestamping and advanced electronic seals for AI systems, regulated platforms, and software supply chains.
How do I connect sigill.ai — Evidence infrastructure for autonomous systems to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
Operate this server?
Request removal if you do not want sigill.ai — Evidence infrastructure for autonomous systems listed here, or claim the listing if you want to manage it on MCPBundles.
Operate sigill.ai — Evidence infrastructure for autonomous systems?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
Seal a hash (CAdES/JAdES) — Create a detached electronic seal (CAdES .p7s, or JAdES for JSON content) over the SHA-256 digest of a file, with one of your organisation's seal certificates. A signature timestamp (RFC 3161) is added when a timestamp authority responds; if none does, the seal is still created without trusted time (format …-b-b) and the result says so. Hash the file locally — its content never reaches Sigill. Returns the detached signature inline; save it next to the file. PDFs with an embedded seal are not ava
Verify a detached seal by hash — Verify a detached CAdES (.p7s) or JAdES (.jades.json) seal against the digest of the file it covers: hash match, signature, signer certificate trust and timestamp. Hash the file locally; only the digest and the signature are sent. Embedded PDF (PAdES) seals cannot be verified over MCP — use sigill.ai/verify or the SDKs. No authentication required.
Seal a multi-object record by hashes — Blind multi-object JAdES seal — e.g. an AI-evidence record binding a prompt, an output and an envelope. Send the envelope's digest and one digest per content object (with an opaque URI each); neither the envelope nor any content reaches Sigill. Returns the JWS to store alongside your envelope. Requires a Sigill API key or sign-in; uses your seal quota.
Verify a multi-object seal by hashes — Verify a multi-object JAdES seal by digests only: is the signature valid, and was every signed object supplied with a matching digest (complete)? Reports missing and unreferenced objects. Supply the envelope's digest under the envelope reference the signature carries (sigD.pars[0]: sigill-envelope.json, or urn:sigill:envelope for older seals). No content is sent. No authentication required.
List and search evidence — List your organisation's evidence (one row per artifact: timestamps, seals, restamp chains), newest activity first. Filter by text, tags, format, status, verification verdict, the needs-action work queue, archive view or ERS exportability. Returns ids and hashes the other evidence tools take, plus a link to each evidence page.
Get evidence detail — Full detail of one evidence: for a timestamp, the restamp chain with per-token metadata and verification state; for a seal, the operation with format, level, certificate and timestamps.
Evidence event log — Chronological custody events for an evidence: stamping, restamps, sealing, reminder changes and emails, risk acknowledgements, with the acting user.
List validation reports — Every ETSI TS 119 102-2 validation report issued for an evidence (current and superseded) with sha256 and signing state.
Get a validation report (XML) — The ETSI TS 119 102-2 validation report XML (unsigned) for a timestamp chain's latest verification, or a specific issued report_id. The signed report bundle is a download in the dashboard. Returned inline; very large reports are refused with a link instead of being truncated.
Export RFC 4998 evidence record — Export a timestamp evidence's restamp chain as one RFC 4998 EvidenceRecord (.ers, DER, base64) that independent ERS tools validate. Only for ERS-exportable evidence (see sigill_list_evidence ers_exportable).
Get a stored timestamp token — Download the stored RFC 3161 time-stamp response (.tsr, base64) of a timestamp transaction — when your organisation stores tokens.
Restamp/re-seal jobs — Recent bulk restamp and re-seal jobs, or one job's progress by job_id.
Tag or untag evidence — Add and/or remove tags on evidence (by content hash). At most 10 tags per evidence, 40 characters each, case-insensitive.
Set an evidence label — Set (or clear, with label omitted/null) the human-readable label of a timestamp transaction.
Archive or restore evidence — Archive evidence (hide from the active view and mute expiry reminders) or restore it with archive=false. Reversible.
Set expiry reminders — Override expiry reminders for one evidence: inherit the organisation default, or force on/off, optionally with days before expiry (30/60/90/180).
Re-verify evidence — Cryptographically verify every chain of each evidence (token signatures, hash linkage, certificate trust) and record the verdict. Up to 50 hashes.
Showing the first 25 tools — full list and schemas: Directory API.
How many tools does sigill.ai — Evidence infrastructure for autonomous systems provide?
MCPBundles probed 30 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does sigill.ai — Evidence infrastructure for autonomous systems require?
sigill.ai — Evidence infrastructure for autonomous systems may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.