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·更新 2026-11-18
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 1 ★ · AIME-TECH-UK-LIMITED/signafaide-sdk · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 1 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
AIME-TECH-UK-LIMITED/signafaide-sdk;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# signafAIde SDK
以下摘录自该仓库的 README(片段)
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.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/aime-tech-uk-limited-signafaide-sdk/)
- 来源
- awesome · https://github.com/AIME-TECH-UK-LIMITED/signafaide-sdk
- 按领域浏览
- MCP 服务
- Traction
- 1 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。