Fabric Verify
NPM · @AUGMENTEV/FABRIC-VERIFY-MCP · 2 COMPONENTS
Signed, publicly logged records of what your AI agent did, with proofs anyone can check offline.
Available components
Last scanned (5 hours ago)
Scores higher than 50% 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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
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 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1393 tokens (~232/item across 6 items; 6 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 Management50
- Stability observed for 15 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
- 94% 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
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 −2
- Tool safety: pass → unverified ▼ security
- Stability: 0.33 → unverified ▼ security
- Schema quality: 162 → 232 ▼ functional
- Tool coverage: 100% → 94% ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.2 → 0.2.1 functional
- Package version: 0.1.2 → 0.2.0 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +7
- Source repository: fail → pass ▲ security
- Security disclosure: unverified → pass ▲ functional
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
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 5 Nov 2026 · Analysed npm/@augmentev/fabric-verify-mcp@0.2.1
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
buy_credit_link Get a link to buy credit ~87
Create a card checkout link for adding Fabric Verify credit ($25, $50, $100 or $500; balance capped at $1,000; credit is non-refundable). Nothing is charged by this tool: a person must open the link and pay. Give the link to the user; never try to pay it yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | – | yes | Top-up amount in US dollars |
No output schema declared.
No examples provided.
check_balance Check Fabric Verify credit ~32
Show the remaining prepaid credit, about how many records it covers, and this session's spend against its limit. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
export_events Bundle agent events for an offline check ~128
Gather agent events recorded from this machine, with their proofs and salts, into one file (augmentev/fabric-agent-events/v1) that anyone can check offline with `augmentev-verify agent-events`. Free. Fetch each event's proof with get_proof first. The file discloses the events' contents to whoever receives it. It shows the bundled events, not that the bundle holds every event: completeness comes from the account's governance export.
| Name | Type | Req | Description |
|---|---|---|---|
| indices | array | – | Or bundle these log indices. |
| run_id | string | – | Bundle every saved event of this run. |
No output schema declared.
No examples provided.
get_proof Get the proof for a record ~155
Fetch the public proof for a recorded action and save it next to the record, with the agent record needed to check it. Free. Returns "pending" if the record is not in a public checkpoint yet (usually a few minutes). Anyone can check a saved proof offline with the verifier at https://augmentev.com/verify. A proof shows that this exact record existed, unchanged, by a certain time. It does not show that what the record describes is true.
| Name | Type | Req | Description |
|---|---|---|---|
| index | integer | yes | The log index returned by record_action |
| wait_seconds | integer | – | How long to wait for the proof if it is not ready yet (default 0, max 45). If still pending, call again later. |
No output schema declared.
No examples provided.
record_action Record an agent action (costs $0.005) ~254
Sign a record of an action this agent took and add it to the Fabric Verify public log. Spends $0.005 of prepaid credit. The summary stays on this machine. The public log permanently holds only a salted SHA-256 fingerprint of the summary, the action kind and time, and coded identifiers that only the user, or an auditor they give an audit pack to, can link to this agent. Returns the record's log index; fetch its proof later with get_proof. A proof shows that this exact record existed, unchanged, by a certain time. It does not show that what the record describes is true.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_record | string | – | Optional. The record (payload_sha256) of an approval, when the account's governance policy requires one for this kind. |
| idempotency_key | string | – | Optional. If a call fails, retry with the same value (and the same kind and summary): the exact same signed record is resent and charged at most once. |
| kind | string | yes | Type of action |
| summary | string | yes | What the agent did, in plain words. Kept locally with the salt so the user can later show what the record was about. Not sent. |
No output schema declared.
No examples provided.
record_event Record an agent event (costs $0.005) ~531
Sign a structured record of one governed step and add it to the Fabric Verify log: a tool call, its result, an approval, a delegation, a policy decision, a halt, and so on (format augmentev/fabric-agent-event/v1). Spends $0.005 of prepaid credit. The event stays on this machine with its salt. Action details stay private: the public log holds only a salted fingerprint of the payload, the action kind and time, and coded identifiers that only the user, or an auditor they give an audit pack to, can link to this agent. Returns `record`: later events link to it (a tool call's approval_record, a tool result's request_record, parent_record). For a tool call, give `body.tool` and `body.arguments` (hashed for you), or `action`; an approval of that call gives the same `action`, so both name the same action. When the account's policy requires approval for tool calls, set body.approval_record and it is presented to the log. Bundle a run with export_events for an offline check. The check shows each event was logged unchanged and every link points to an earlier event of the right type. It does not show that a described tool result is true.
| Name | Type | Req | Description |
|---|---|---|---|
| action | object | – | For tool_call, approval and policy_decision: the tool, server and arguments the action is about. Fills action_sha256 by the published recipe, so a call and its approval match. |
| body | object | yes | The event's fields. tool_call: tool, arguments (or arguments_sha256), optional server, call_id, approval_record. tool_result: request_record, is_error, result (or result_sha256), optional call_id. ap… |
| delegation_record | string | – | The delegation record that handed this agent its task. |
| event | string | yes | Event type |
| idempotency_key | string | – | Optional. Retry with the same value and the same event to resend the same signed record; charged at most once. |
| kind | string | – | Only when the event allows several kinds (delegation: message_sent or decision; third_party_access: data_read, data_write or credential_use). |
| parent_record | string | – | An earlier record this one follows from. |
| run_id | string | – | Your run identifier; export_events bundles a run by it. |
| step_id | string | – | – |
No output schema declared.
No examples provided.
How do I install the Fabric Verify MCP server?
Fabric Verify runs locally as an npm package, launched with npx -y @augmentev/fabric-verify-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 · @augmentev/fabric-verify-mcp
claude mcp add ai-augmentev-fabric-verify -- npx -y @augmentev/fabric-verify-mcp
What is the Fabric Verify MCP server?
Fabric Verify is an MCP server listed in the public MCP registry as ai.augmentev/fabric-verify. Signed, publicly logged records of what your AI agent did, with proofs anyone can check offline. This page covers its npm package (@augmentev/fabric-verify-mcp).
Is the Fabric Verify MCP server safe to use?
Fabric Verify scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Fabric Verify MCP server expose?
Fabric Verify exposes 6 tools: record_action, record_event, export_events, get_proof, check_balance, buy_credit_link. Their descriptions and schemas cost roughly 1,187 tokens of context every time the server is loaded.
Is the Fabric Verify MCP server still maintained?
Fabric Verify is still listed as active in the MCP registry. We last reached this channel on 5 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 Fabric Verify MCP server under?
Fabric Verify 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.