signafAIde
NPM · SIGNAFAIDE-MCP
Use when adding a tool that pays, deletes, sends, runs commands or pushes code: checks calls first.
Available components
Last scanned (15 hours ago)
Scores higher than 44% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2738 tokens (~248/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
- Security disclosure: fail → pass ▲ functional
- 20 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.5.2 → 0.5.3 functional
- 19 Nov 26 +27
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- 18 Nov 26 −11
- Known CVEs: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: 1.00 → unverified ▼ functional
- Package version: 0.4.0 → 0.5.2 functional
- Package version: 0.4.0 → 0.5.1 functional
- Package version: 0.4.0 → 0.5.0 functional
- 17 Nov 26 +12
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Schema quality: 2254 → 2668 ▼ functional
- Dependency health: unverified → 1.00 ▲ functional
- Package version: 0.3.5 → 0.4.0 functional
- 16 Nov 26 −11
- Known CVEs: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 150 → 250 ▼ functional
- Dependency health: 1.00 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Schema quality: good → excellent functional
- Destructive annotations: pass → 100 functional
- Package version: 0.3.2 → 0.3.5 functional
- Package version: 0.3.2 → 0.3.4 functional
- Package version: 0.3.2 → 0.3.3 functional
- 15 Nov 26 0
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.3.1 → 0.3.2 functional
- 14 Nov 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/signafaide-mcp@0.5.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 6 packages
| Packages resolved | 6 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
signafaide_claim_link signafAIde sandbox claim link ~184
The link the human opens to claim this project's free sandbox and keep its records, what claiming gives and how long an unclaimed sandbox has left. Show it to the user; do not open it yourself. Use this tool when the user only needs the claim link, or needs it again. signafaide_status shows the same link among the whole state of the project (key, chains, outbox, quota): call that one when you need those too. Read-only: with a sandbox key it asks the service whether the sandbox is still unclaimed; with no sandbox it makes no request and says so. It never creates a sandbox: that is signafaide_init, after the user agrees.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Path of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder. |
No output schema declared.
No examples provided.
signafaide_explain_error Explain a signafAIde error code ~73
What a signafAIde error code means and how to fix it, e.g. chain_conflict, quota_exceeded, invalid_key, network, not_recorded.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The error code, e.g. from SignafaideError.code or the service's error body. |
No output schema declared.
No examples provided.
signafaide_explain_ruling Explain a signafAIde ruling on a tool call ~266
Explains why a tool call was allowed, noted or blocked: the client's tool-call checks, the witness's ruling (allow or block, mode, basis), the rules that matched, the rule set version, the fields that were not disclosed, and how to allow the call. Pass the record hash (or its first 8 or more characters) of the call's decision or outcome, from signafaide_records. Pass pack to read a verification pack instead of the local records. Read-only: it reads local files, makes no request and changes nothing. It never prints a disclosed value, only field pointers, rule ids, codes and versions. It does not re-verify the record (use signafaide_verify); to see all the rules held, use signafaide_show_rules.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Path of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder. |
| pack | string | – | Path of a verification pack (from `signafaide export` or an auditor link) to read the record from, instead of the local records. |
| record | string | yes | A record hash, or its first 8 or more characters: a decision or its outcome. |
No output schema declared.
No examples provided.
signafaide_flush Send the waiting signafAIde records now ~285
Sends the records waiting in this project's outbox to the signafAIde service (or the SIGNAFAIDE_URL witness) now, the same as `signafaide flush`, and saves the receipts that come back beside the records. What is sent is each record's envelope (hashes, agent and tool names, times) with the agent's signature, never inputs or outputs unless stored content was turned on in the code. Use it after signafaide_init, or when signafaide_status shows records waiting. Records also ship by themselves while the agent runs, and signafaide_verify ships them before it checks; this tool only ships. It sends only when an API key already exists, which means a person opted in with `signafaide init`, signafaide_init or SIGNAFAIDE_API_KEY. Without a key it does nothing and says so: it never creates a sandbox and never opts in. Returns how many records were shipped, how many are left in the outbox, each chain that is BLOCKED with its next step, and each error with its code (see signafaide_explain_error). Safe to repeat: a record that has shipped is not sent again.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Path of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder. |
No output schema declared.
No examples provided.
signafaide_init Create an external signafAIde sandbox (ask the user first) ~299
Creates an external sandbox project on the signafAIde service (or the SIGNAFAIDE_URL witness), saves its API key to .env and returns the claim link, what claiming gives and when an unclaimed sandbox is deleted. From then on record hashes (never content) are sent there, and records written earlier ship with their original times. This is an external side effect: ask the user and call it only after they agree. Without it, records stay local and still verify. Creating a sandbox means the user agrees to the signafAIde Terms and Privacy notice (<service>/legal/terms and <service>/legal/privacy, where <service> is SIGNAFAIDE_URL or the signafAIde service): show them both links when you ask, and pass on the notice this tool returns. It creates nothing unless confirm_user_agreed is true and user_words holds what the user wrote when they agreed.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_user_agreed | boolean | – | Set to true only after the user, in this conversation, agreed to create the sandbox and to the Terms and Privacy notice. Never set it on your own judgement. |
| directory | string | – | Path of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder. |
| user_words | string | – | The user's own words when they agreed, quoted from the conversation (for example "yes, create the sandbox"). |
No output schema declared.
No examples provided.
signafaide_quickstart signafAIde snippet for a language and framework ~188
Use when adding or changing a tool that pays, deletes, sends messages, runs commands, pushes code, or edits secrets or config, in a stack that is not the open project. A reference snippet for a language and framework you name: returns the install command, the canonical code to record an agent's tool calls with signafAIde, and the verify command. It reads nothing in the project, detects nothing, changes nothing and sends nothing; the same arguments always give the same answer. Use it to answer a question about a stack that is not the open project, or when signafaide_setup could not tell the language. When you are working inside a project, use signafaide_setup instead: it detects the stack and previews the exact edit for that project.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | plain (default) for ordinary functions. |
| language | string | yes | – |
No output schema declared.
No examples provided.
signafaide_records List and search the signafAIde records on this machine ~435
Lists the records in this project's .signafaide/ folder, newest first, and searches them by agent, by time window, or by record hash. Use it to see what was recorded: which tool calls, by which agent, when, and how far each record has got. Returns one line per record with its time, agent, sequence number, kind (decision, outcome or note), tool name, record hash and status (signed only; co-signed; co-signed with the public timestamp pending; BLOCKED; or FAILED a check), then the total that matched, how many are shown and whether the list was truncated. Metadata only: the inputs and outputs of the tool calls are never returned, they stay in the local files (a person reads them with `npx signafaide replay`). Read-only: it writes nothing and sends no records. Each record is checked against its signature and its chain as it is listed; when records here have been co-signed, it fetches the service's public keys to check their receipts, and otherwise it makes no request. For the full check with PASS or FAIL use signafaide_verify; for counts per chain, the outbox and the quota use signafaide_status.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Only this agent's records. Default: every agent with records here. |
| directory | string | – | Path of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder. |
| from | string | – | Only records at or after this time: an ISO time such as 2026-11-13T10:00:00Z, or a date (YYYY-MM-DD). |
| limit | integer | – | The most records to return. Default 20; values above 100 are treated as 100. |
| record | string | – | A record hash, or its first 8 or more characters: returns that record and its paired decision or outcome. |
| to | string | – | Only records before this ISO time, or up to the end of this date (YYYY-MM-DD). |
No output schema declared.
No examples provided.
signafaide_setup Preview signafAIde setup for this project (changes nothing) ~247
Use when adding or changing a tool that pays, deletes, sends messages, runs commands, pushes code, or edits secrets or config, or when the user asks for an audit trail of what an AI agent did. signafAIde wraps that tool with protect(): it runs only when the rules a person set allow it, and each call is signed and recorded on this machine; nothing is sent until a person opts in. Call this first when you are working inside a project. It reads the project's dependency files and source and returns a preview: it changes no file, creates nothing and sends nothing. Returns the detected language, package manager and framework, the exact install command, the code edit for this framework, the functions that look like actions, whether an API key is present, and what a sandbox would send. Make the edit yourself, run the agent, then call signafaide_verify. For a snippet in a language and framework you name, without reading any project, use signafaide_quickstart instead.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Path of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder. |
No output schema declared.
No examples provided.
signafaide_show_rules Show the tool-call rules this project holds ~167
Shows the rules in force for this project's tool-call checks: the held rule set (version, mode, default, each rule on one line), the local rules and whether the checks file has them On or Calibrating, what happens to each protected tool if signafAIde can't be reached (Stop or Let it run), and the fields each protected tool discloses to the witness. Use it before explaining a ruling, or to see what a call would meet. Read-only: it reads local files, makes no request and changes nothing; `signafaide rules pull` fetches a newer version.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Path of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder. |
No output schema declared.
No examples provided.
signafaide_status Show the state of signafAIde in this project ~304
Reports how signafAIde is set up in this project and whether records are reaching the service. Call it to check that set-up worked, after signafaide_init, or when signafaide_verify or signafaide_flush reports a problem and you need to see why. Returns one line for each of: the API key (masked) and its env, or that there is none and records stay on this machine; the service URL; the project; the local state folder; every agent chain with its key id, record count and last receipt; any chain that is BLOCKED, with the reason and the next step; how many records wait in the outbox; the quota used; and, for a sandbox, the claim link with how long an unclaimed sandbox has left. Read-only: it sends no records and changes no code, record or key (it only saves what the service says about the sandbox's claim state in .signafaide/). It contacts the service only when an API key exists, to read the project, the quota and the claim state; without a key it makes no request. Use signafaide_records to list the records themselves, signafaide_flush to send the waiting ones, and signafaide_claim_link when the user only needs the claim link.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Path of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder. |
No output schema declared.
No examples provided.
signafaide_verify Verify the local signafAIde records ~184
Checks every record in the project's .signafaide/ folder (or a verification pack): schema, hashes, agent signatures, chain links and content hashes, and, for records a witness has co-signed, Merkle proofs, the service's batch and head signatures, drand and anchors. With an API key it first ships waiting records (signafaide_flush is the explicit way to ship them without verifying); without one nothing is sent. Returns one line per check, what still needs the witness, and PASS or FAIL. To list the records themselves, use signafaide_records.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Path of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder. |
| pack | string | – | Path of a pack from `signafaide export`, instead of the local state. |
No output schema declared.
No examples provided.
How do I install the signafAIde MCP server?
signafAIde runs locally as an npm package, launched with npx -y signafaide-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · signafaide-mcp
claude mcp add uk-co-signafaide-signafaide -- npx -y signafaide-mcp
What is the signafAIde MCP server?
signafAIde is an MCP server listed in the public MCP registry as uk.co.signafaide/signafaide. Use when adding a tool that pays, deletes, sends, runs commands or pushes code: checks calls first. This page covers its npm package (signafaide-mcp).
Is the signafAIde MCP server safe to use?
signafAIde scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the signafAIde MCP server expose?
signafAIde exposes 11 tools: signafaide_setup, signafaide_init, signafaide_quickstart, signafaide_verify, signafaide_status, and 6 more. Their descriptions and schemas cost roughly 2,632 tokens of context every time the server is loaded.
Is the signafAIde MCP server still maintained?
signafAIde is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the signafAIde MCP server under?
signafAIde declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the signafAIde MCP server?
VerifyMCP ran 16 checks on signafAIde, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.