A
AIME-TECH-UK-LIMITED/signafaide-sdk
signafAIde gives you audit evidence of what your AI agents did, for EU AI Act record-keeping, ISO/IEC 42001 and SOC 2.
★ 1·updated 2026-11-18
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 1 ★ · AIME-TECH-UK-LIMITED/signafaide-sdk · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 1 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
AIME-TECH-UK-LIMITED/signafaide-sdk;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# signafAIde SDK
Excerpted from the repository README (abridged)
signafAIde gives you audit evidence of what your AI agents did, for EU AI Act record-keeping, ISO/IEC 42001 and SOC 2. Each tool call is recorded, signed with the agent's own key and chained on the machine that wrote it. Once a person opts in, an independent witness (the signafAIde service, or one you host) co-signs it and timestamps it publicly, so neither side can forge, edit or remove a record alone, and an auditor can check it offline without trusting either. It attests integrity and timing, never whether a decision was right.
Free on its own: the SDK and the verifiers are Apache-2.0 and need no account. On their own they give you a signed, chained, offline-verifiable record of every tool call, on your machine. The service adds what one party cannot give itself: an independent second signature, two public time bounds, and a check that no record is missing.
Local first: with no API key, records are signed, chained and verified in .signafaide/, and nothing is sent. Sending starts only when a person runs signafaide init (a sandbox: no account, email or card) or sets SIGNAFAIDE_API_KEY.
Hashes, not content: after the opt-in, each record sends its content hash with its tool name, agent name and time (and its chain links), never its inputs or outputs, unless you turn on stored content. Tool and agent names are sent as you write them, so don't put personal data in them. Each content hash is salted with 16 random bytes that stay on your machine with the content, so the hash alone cannot be used to guess the content, even when it has only a few possible values.
Your environment: the default witness is the hosted service (https://api.signafaide.co.uk). A self-hosted witness, under an Enterprise contract, is set with SIGNAFAIDE_URL (self-host guide). Running in production: production guide.
Independent checks: the protocol is a public spec with test vectors, and the verifier checks a verification pack without our service.
## What is here
| path | what |
| spec/SPEC.md | the protocol: records, batches, receipts, anchors, the HTTP API, verification packs, local state |
| spec/vectors.json | test vectors every implementation reproduces byte for byte |
| python/ | the Python SDK and CLI (signafaide on PyPI) |
| python-langchain/ | langchain-signafaide: a LangChain agent middleware that records every tool call the agent makes |
| js/ | the TypeScript SDK, CLI and agent setup for coding agents (signafaide on npm), and the MCP server (signafaide-mcp, in js/mcp) |
| CHANGELOG.md | what changed in each release; every release is a git tag (v0.4.0) |
| verifier/ | signafaide-verify, the standalone Rust verifier of a pack (also builds to WebAssembly) |
| core/ | the Rust protocol core shared by the verifier and the service |
| plugin/ | the Claude Code plugin: the MCP server and the skill |
## Quick start
bash
uv add signafaide # Python, in a uv project; or: python3 -m venv .venv && .venv/bin/python -m pip install signafaide
npm install signafaide # TypeScript or JavaScript
Wrap the tools that act, run the agent, then signafaide verify (npx signafaide verify for TypeScript). See the Python and TypeScript READMEs.
Free on its own: the SDK and the verifiers are Apache-2.0 and need no account. On their own they give you a signed, chained, offline-verifiable record of every tool call, on your machine. The service adds what one party cannot give itself: an independent second signature, two public time bounds, and a check that no record is missing.
Local first: with no API key, records are signed, chained and verified in .signafaide/, and nothing is sent. Sending starts only when a person runs signafaide init (a sandbox: no account, email or card) or sets SIGNAFAIDE_API_KEY.
Hashes, not content: after the opt-in, each record sends its content hash with its tool name, agent name and time (and its chain links), never its inputs or outputs, unless you turn on stored content. Tool and agent names are sent as you write them, so don't put personal data in them. Each content hash is salted with 16 random bytes that stay on your machine with the content, so the hash alone cannot be used to guess the content, even when it has only a few possible values.
Your environment: the default witness is the hosted service (https://api.signafaide.co.uk). A self-hosted witness, under an Enterprise contract, is set with SIGNAFAIDE_URL (self-host guide). Running in production: production guide.
Independent checks: the protocol is a public spec with test vectors, and the verifier checks a verification pack without our service.
## What is here
| path | what |
| spec/SPEC.md | the protocol: records, batches, receipts, anchors, the HTTP API, verification packs, local state |
| spec/vectors.json | test vectors every implementation reproduces byte for byte |
| python/ | the Python SDK and CLI (signafaide on PyPI) |
| python-langchain/ | langchain-signafaide: a LangChain agent middleware that records every tool call the agent makes |
| js/ | the TypeScript SDK, CLI and agent setup for coding agents (signafaide on npm), and the MCP server (signafaide-mcp, in js/mcp) |
| CHANGELOG.md | what changed in each release; every release is a git tag (v0.4.0) |
| verifier/ | signafaide-verify, the standalone Rust verifier of a pack (also builds to WebAssembly) |
| core/ | the Rust protocol core shared by the verifier and the service |
| plugin/ | the Claude Code plugin: the MCP server and the skill |
## Quick start
bash
uv add signafaide # Python, in a uv project; or: python3 -m venv .venv && .venv/bin/python -m pip install signafaide
npm install signafaide # TypeScript or JavaScript
Wrap the tools that act, run the agent, then signafaide verify (npx signafaide verify for TypeScript). See the Python and TypeScript READMEs.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/aime-tech-uk-limited-signafaide-sdk/)
- Source
- awesome · https://github.com/AIME-TECH-UK-LIMITED/signafaide-sdk
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.