MCP.Market

Fabric Verify MCP server

online · 100% uptime
by augmentev.ai·ai.augmentev/fabric-verify·v0.3.1

Signed, publicly logged records of what your AI agent did, with proofs anyone can check offline.

A93/100grade A
What users say
No reviews yet
Be the first
Safety scan
A93/100

not scanned yet

Adoption
Growing

0 stars44 downloads/wk

Reviews

Write one

Nobody has reviewed Fabric Verify yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Fabric Verify tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Fabric Verify compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
93/100
higher than 96% of 4,460 AI and agents servers
Uptime
100%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
348 ms
faster than 40% of 2,331 AI and agents servers
Downloads a week
44
more than 36% of 1,538 AI and agents servers with a package

Release history: 3 versions in the registry since 2026-10-23, latest 2026-11-01, typically one every 9 days.

Install Fabric Verify in Claude Code, Cursor or VS Code

claude mcp add --transport http fabric-verify https://mcp.augmentev.com/mcp
Add to Cursor

What the publisher says

From the Fabric Verify repository's README, as published. We do not edit it. Read it on GitHub

Fabric Verify MCP server

Give your AI agent a tamper-evident record of what it did.

Each time the agent records an action, this server signs a short record on your machine, with the agent's own key, and adds it to the Fabric Verify public log. Later you get a proof that anyone can check offline, without trusting you or us.

A proof shows that this exact record existed, unchanged, by a certain time. It does not show that what the record describes is true.

Your text stays with you. Each record sends a salted fingerprint of it, plus the signature. The public log permanently shows the agent name, key name, action kind, time and public key with every record, so never put personal data in FABRICAGENT or FABRICKID.

Price

Buy credit by card at . Your credit key (fvk_…) is shown once after payment, so save it in a password manager.

Install

You need Node.js 20 or later. Add this to your MCP client's configuration:

{
  "mcpServers": {
    "fabric-verify": {
      "command": "npx",
      "args": ["-y", "@augmentev/fabric-verify-mcp"],
      "env": {
        "FABRIC_CREDIT_KEY": "fvk_...",
        "FABRIC_AGENT": "my-agent"
      }
    }
  }
}

In Claude Code:

claude mcp add fabric-verify --env FABRIC_CREDIT_KEY=fvk_... --env FABRIC_AGENT=my-agent -- npx -y @augmentev/fabric-verify-mcp

Settings

Tools

  • recordaction (kind, summary, optional idempotencykey): signs and logs one record, then returns its log index. The summary and its salt are saved under FABRICHOME/records///, so you can later show what the record was about. If a call fails, call again with the same idempotencykey, kind and summary: the exact same signed record is resent and charged at most once.
  • getproof (index, optional waitseconds up to 45): fetches the proof and saves it next to the record. Proofs are usually ready a few minutes after recording.
  • checkbalance**: shows your remaining credit and this session's spend.
  • buycreditlink (amount_usd: 25, 50, 100 or 500): returns a card checkout link for a person to open. This tool charges nothing.

Check a proof

Download the verifier and the published log keys from , then run this in the record's folder:

augmentev-verify log-proof proof.json --pins fabric-log-v1.json --audit agent-record.json

Pin the version

For production agents, pin an exact version, such as npx -y @augmentev/fabric-verify-mcp@0.1.1, and update deliberately. The package ships a lockfile (npm-shrinkwrap.json) so its dependencies are fixed too.

Keep your agent key

The agent key is FABRICHOME/agent-ed25519.pem. Back it up. Each key name (FABRICKID) belongs to one key for good. If you lose the key, set a new FABRIC_KID.

Support

support@augmentev.com

Licence

Apache-2.0. "Fabric Verify" and "AugmentEV" are trademarks of AugmentEV Inc.; the licence grants no rights to them.

Nothing above is checked by us. What we check is on the safety report.

Fabric Verify: common questions

Is Fabric Verify MCP server safe?
Yes, by our scan: it is graded A (93/100). Read the Fabric Verify safety report
How do I install Fabric Verify?
It runs remotely at mcp.augmentev.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Fabric Verify need an API key?
Yes. The registry entry asks for FABRIC_CREDIT_KEY.
Is Fabric Verify maintained?
The last commit was 12 days ago (2026-10-23). The latest release is v0.3.1.
Is Fabric Verify up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Fabric Verify?
Servers from other publishers that do the same job: three.ws Provenance MCP server, Emilia Protocol MCP server and Mockserver MCP server. Compare all Fabric Verify alternatives.
How does Fabric Verify compare with other AI and agents MCP servers?
safety score 93/100 (higher than 96% of 4,460 AI and agents servers); uptime 100% (of our recent checks; the typical remote AI and agents server answers 100%); response time 348 ms (faster than 40% of 2,331 AI and agents servers). Full comparison.

Alternatives to Fabric Verify

Same job from other publishers: the closest match first, then the best rated.

All Fabric Verify alternatives →
  • three.ws Provenance
    Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.
    B
  • Emilia Protocol
    Exact-action approval for consequential agent actions: request, track, and verify signed receipts.
    B
  • Mockserver
    Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
    A
  • Watch Skill
    Watch video and live sessions, keep timestamped evidence, and verify an agent's own work.
    B
  • CHAP Coordinator
    Auditable records of human decisions over AI agent work. Approvals, edits, overrides, escalations.
    A