Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Signed, publicly logged records of what your AI agent did, with proofs anyone can check offline.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
FABRIC_CREDIT_KEY, FABRIC_AGENT, FABRIC_MAX_SPEND_USDValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.augmentev.com/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"fabric-verify": {
"command": "npx",
"args": [
"-y",
"@augmentev/fabric-verify-mcp"
],
"env": {
"FABRIC_CREDIT_KEY": "your-value",
"FABRIC_AGENT": "your-value",
"FABRIC_MAX_SPEND_USD": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http fabric-verify https://mcp.augmentev.com/mcpclaude mcp add fabric-verify --env FABRIC_CREDIT_KEY=your-value --env FABRIC_AGENT=your-value --env FABRIC_MAX_SPEND_USD=your-value -- npx -y @augmentev/fabric-verify-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"fabric-verify": {
"url": "https://mcp.augmentev.com/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"fabric-verify": {
"command": "npx",
"args": [
"-y",
"@augmentev/fabric-verify-mcp"
],
"env": {
"FABRIC_CREDIT_KEY": "your-value",
"FABRIC_AGENT": "your-value",
"FABRIC_MAX_SPEND_USD": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"fabric-verify": {
"type": "http",
"url": "https://mcp.augmentev.com/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"fabric-verify": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@augmentev/fabric-verify-mcp"
],
"env": {
"FABRIC_CREDIT_KEY": "your-value",
"FABRIC_AGENT": "your-value",
"FABRIC_MAX_SPEND_USD": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.augmentev.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
FABRIC_AGENT envFABRIC_MAX_SPEND_USD envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain augmentev.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 157 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: FABRIC_CREDIT_KEY
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.3.1) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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. Action details stay private. The public log holds only a salted fingerprint, the action kind and time, and coded identifiers that only you, or an auditor you give an audit pack to, can link to your agents. Records are permanent. AugmentEV keeps the agent name, key name and public key in an erasable store so they can go into your audit packs, so never put personal data in FABRIC_AGENT or FABRIC_KID.
| Tool | Cost |
|---|---|
record_action, record_event | $0.005 per record, from prepaid credit |
get_proof, check_balance, buy_credit_link, export_events | free |
Buy credit by card at https://augmentev.com/pricing#buy. Your credit key (fvk_…) is shown once after payment, so save it in a password manager.
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
The Cursor plugin (.cursor-plugin/plugin.json and mcp.json) and the Gemini CLI extension (gemini-extension.json) in this repository don't run this package. They connect to the hosted server at https://mcp.augmentev.com/mcp, the address chat apps use as a custom connector. There is nothing to install.
When an app connects, it sends you to a sign-in page where you enter your credit key, a name for the assistant and a daily spending limit ($0.50 to $20). The app gets an access token, not your key.
The remote connector has four tools: record_action, record_event, get_proof and check_balance. Records made through it are signed by a key AugmentEV hosts for your account and are labelled "augmentev-hosted"; only this connector can make records with that label. For records signed by a key only your agent holds, use the package above.
| Variable | Default | Meaning |
|---|---|---|
FABRIC_CREDIT_KEY | (required) | Your credit key. Keep it secret. |
FABRIC_AGENT | mcp-agent | A stable name for this agent (printable ASCII, no spaces). |
FABRIC_KID | -key-1 | A name for the agent's signing key. Change it when you rotate the key. |
FABRIC_HOME | ~/.fabric-verify | Where the agent key and your records are kept (private to your user). |
FABRIC_MAX_SPEND_USD | 1 | The most this server may spend in one session. |
kind, summary, optional idempotency_key, optional approval_record): signs and logs one record, then returns its log index. The summary and its salt are saved under FABRIC_HOME/records/ / /, so you can later show what the record was about. If a call fails, call again with the same idempotency_key, kind and summary: the exact same signed record is resent and charged at most once.event, body, optional action, run_id, step_id, parent_record, delegation_record, kind, idempotency_key): signs and logs one structured agent event: a tool call, its result, an approval, a delegation, a policy decision, a halt and so on (format augmentev/fabric-agent-event/v1). Same price as record_action. The event is the record's payload and stays on this machine. It returns record, which later events link to. For a tool call, pass action (tool, server, arguments), and pass the same action when recording its approval, so both name the same action. If your account's governance policy requires approval for tool calls, set body.approval_record and the approval is presented to the log, which uses it once. A tool result is signed as kind other, so that rule does not also gate results.run_id or indices): bundles events recorded from this machine, with their proofs, into one file that anyone can check offline with augmentev-verify agent-events. Free. Fetch the proofs first. The bundle shows that its events were logged unchanged and that every link points to an earlier event of the right type. It does not show that the bundle holds every event, or that a described tool result is true. Events recorded on another machine (another agent's approval, say) are in that machine's bundle; merge records in log order to check them together.index, optional wait_seconds up to 45): fetches the proof and saves it next to the record. Proofs are usually ready a few minutes after recording.amount_usd: 25, 50, 100 or 500): returns a card checkout link for a person to open. This tool charges nothing.Download the verifier and the published log keys from https://augmentev.com/verify, then run this in the record's folder:
augmentev-verify log-proof proof.json --pins fabric-log-v1.json --audit agent-record.json
For production agents, pin an exact version, such as npx -y @augmentev/fabric-verify-mcp@0.2.1, and update deliberately. The package ships a lockfile (npm-shrinkwrap.json) so its dependencies are fixed too.
The agent key is FABRIC_HOME/agent-ed25519.pem. Back it up. Each key name (FABRIC_KID) belongs to one key for good. If you lose the key, set a new FABRIC_KID.
support@augmentev.com
Apache-2.0. "Fabric Verify" and "AugmentEV" are trademarks of AugmentEV Inc.; the licence grants no rights to them.