Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Pre-spend trust for AI agents that buy: check x402 services and product listings before paying.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
TWZRD_SIGNAL_SOURCEDu brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"twzrd-agent-intel": {
"command": "uvx",
"args": [
"twzrd-agent-intel"
],
"env": {
"TWZRD_SIGNAL_SOURCE": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add twzrd-agent-intel --env TWZRD_SIGNAL_SOURCE=your-value -- uvx twzrd-agent-intelTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"twzrd-agent-intel": {
"command": "uvx",
"args": [
"twzrd-agent-intel"
],
"env": {
"TWZRD_SIGNAL_SOURCE": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"twzrd-agent-intel": {
"type": "stdio",
"command": "uvx",
"args": [
"twzrd-agent-intel"
],
"env": {
"TWZRD_SIGNAL_SOURCE": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
TWZRD_SIGNAL_SOURCE envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto twzrd-sol bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.5.13) kam vor 18 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Python (uv) auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Georgia MCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
An MCP server for Georgian public data, read from the organizations that publish it.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Muse pilot (Meta Global AI Developer Hackathon): a read-only MCP connector at
https://intel.twzrd.xyz/muse/mcpwith 6 tools covering one listing (Vuori Kore Short,
Ink, US).
check_listingreturnsadvertised,check_failed, orunknown_seller, and
every result carries
authorizes_spend: false. Discovery:
Demo: video.
Pre-spend trust for agents that buy. Before an agent pays an x402 seller or buys a product from a store, TWZRD answers one question from public evidence: should this payment go ahead? The buyer-side gate turns that answer into a refusal before the wallet signs. This repository is the public source of truth for the hosted checks, the npm packages, the receipt and record formats, and the proofs behind them.
Guard an agent's paying fetch: a caller-supplied USDC cap, an explicit recipient allowlist, mandatory free preflight, and a local decision record before signing. createBuyerFetch is the front door (since twzrd-x402-gate@0.12.3); its expectedAmount quote binding needs twzrd-x402-gate@0.12.4 or later. Install the current release, twzrd-x402-gate@0.16.2, and start with the runnable buyer wrapper quickstart. The other toolkit APIs below remain available with their existing defaults.
quickCheck is $0.001 USDC, paid by the buyer over x402 (seller wash risk, tier and score; no receipt). Separately, the gate can issue a portable twzrd.payment_decision.v1 record from its own decision, signed locally with your own signer; TWZRD never holds a key.Not a wallet. Not a payment network. The commerce walkthrough lives in docs/COMMERCE-KIT.md.
Canonical skill (always refresh) • https://intel.twzrd.xyz/skill.md (skill twzrd-trust; the live copy carries its version) · ClawHub skill twzrd-trust Spend-control SDK (npm) • twzrd-x402-gate@0.16.2 + seat x402-solana@3.0.1
Live MCP • https://intel.twzrd.xyz/mcp (streamable HTTP; free tools for x402 service checks and product-listing checks) Shopping check • free check_listing on the hosted MCP · report: https://twzrd.xyz/shopping-check/vuori-kore/ Agent contract • https://intel.twzrd.xyz/llms.txt · https://intel.twzrd.xyz/.well-known/agent.json
https://intel.twzrd.xyz/mcp and the REST routes below), twzrd-x402-gate on npm, the offline twzrd-receipt-verifier, the receipt transparency log with on-chain anchors (one per advanced tree head, hourly cadence), and the no-spend recorded demonstration at /v1/intel/demo-gate.eip155:8453), and the gate runs the scored preflight on both. The paid /quick and /trust endpoints accept the buyer's $0.001 or $0.05 USDC payment on either chain but score a Solana seller wallet only, so signed V7 receipts cover Solana sellers. EVM chains other than Base are recognized but not scored. The examples below use the Solana seat; see the gate's network table for Base.authorizes_spend is always false). See What TWZRD does not claim.| You want to | Do this |
|---|---|
| See a refusal with nothing installed | Run the hosted recorded demonstration below: one curl, no wallet, no key. |
| Put the gate on a paying agent | twzrd-x402-gate/QUICKSTART.md, then the package README for entry points and defaults. |
| Call the checks from an MCP client | Add https://intel.twzrd.xyz/mcp; the tool list is live (tools/list). Agent contract: llms.txt. |
| Review the cryptography and the claims | REVIEW.md (bind-v1, with mainnet ground truth), docs/security-assurance.md, docs/receipt-v6-spec.md, docs/transparency-log.md, SECURITY.md. |
| Know which document is current | docs/README.md: every document in this repository, labeled canonical, historical or internal, with the versions verified on the date shown. |
| Build or publish from this checkout | AGENTS.md: what is source and what is a published-artifact mirror, the one supported install, and the fork relationship with the upstream monorepo. |
Registry latest as read on that date. The tree column is what this checkout mirrors; a difference is a pending resync, not a second product.
| Package | Registry | This tree | Role |
|---|---|---|---|
twzrd-x402-gate | npm 0.16.2 | 0.16.2 | Buyer-side gate SDK and CLIs; the one package with source here |
x402-solana | npm 3.0.1 | peer | Compatible Solana client seat |
twzrd-receipt-verifier | npm and PyPI 1.4.4 | floor ^1.4.0 | Offline V5/V6/V7 receipt verifier (separate repository) |
twzrd-mcp-server / twzrd-mcp | npm 0.6.2 / PyPI 0.2.3 | 0.6.2 (dist/ mirror) | Local spend-capped MCP client; prefer the hosted MCP |
@wzrd_sol/eliza-plugin | npm 0.10.1 | 0.10.1 (dist/ mirror; source in eliza-plugin-source/) | elizaOS actions |
@wzrd_sol/plugin-trustgate | npm 0.3.10 | 0.3.10 | elizaOS and facilitator settle hook |
twzrd-preflight | npm 0.5.0 | separate repository | OpenClaw wrapped-fetch adapter |
twzrd-agent-intel | PyPI 0.5.13 | not in this repository | Server package behind the hosted checks |
twzrd-log-verifier | npm 0.5.0 | 0.5.0 | Offline transparency-log verifier: npx -y twzrd-log-verifier selftest. Upgrade from 0.4.0 or earlier: 0.5.0 verifies the anchor transaction bytes and the authority's signature locally, where 0.4.0 trusts the RPC's parsed response; 0.3.0 also reports a failing different-size consistency path as proven equivocation |
npm ci
npm run build npm run buyer-demo --workspace=twzrd-x402-gate
This uses the real x402 client against an offline 402 fixture. It prints reason: price_cap_exceeded, signer_invocations: 0 and usdc_spent: 0, and writes .twzrd/demo-decisions.jsonl locally. It makes no network request and needs no wallet. This is internal demonstration evidence, not outside use.
For an installed consumer, pack the gate and install the tarball with its optional @x402/core and @x402/fetch peers; then run npx twzrd-buyer-demo. See the package README for the install and live client wiring. /quick and /trust stay optional seller-score products; the wrapper buys neither and makes no fulfillment claim.
Run this one-line command with no wallet, no API key, and no configuration:
curl -fsS https://intel.twzrd.xyz/v1/intel/demo-gate | jq '{verdict: (.steps[] | select(.name == "block_path") | .verdict), approved: (.steps[] | select(.name == "block_path") | .approved), signerInvocations: (.steps[] | select(.name == "block_path") | .signer_invocations), mode, ok}'
Without jq, run: curl -fsS https://intel.twzrd.xyz/v1/intel/demo-gate
Expected output:
{
"verdict": "block", "approved": false, "signerInvocations": 0, "mode": "no_spend", "ok": true }
*Blocks happen before your signer is invoked (signerInvocations: 0) — zero USDC at risk.*
Pre-spend trust for AI agents that buy: check x402 services and product listings before paying.
| You are | Free | Paid |
|---|---|---|
| an agent about to pay an x402 seller | Readiness card (allow, warn or block), wash flags, seller reputation, offline receipt check. | $0.001 quickCheck (seller wash risk, tier and score, no receipt); optional $0.05 trust receipt, a signed V7 receipt when you pay on Solana. |
| an agent about to buy a product from a store | check_listing(product_url, declared_unit_price) against a published listing card, and the Agent Shopping Check report. | Optional $0.001 checkout brief for a human to review before checkout; TWZRD never opens or completes a checkout. |
Each piece below works alone. Plugged into the hosted checks, they form one pre-spend path.
| Piece | On its own | Plugged in | Install |
|---|---|---|---|
| Hosted checks | Free checks with nothing to install: is this x402 seller safe to pay, and does this store listing match a published card. | The pieces below that screen a payment call it; it is where the decisions and the signed receipts come from. The receipt verifier needs no server. | Add https://intel.twzrd.xyz/mcp to an MCP client |
twzrd-x402-gate | Wraps an x402 client's pay path: asks the hosted checks about the seller before your signer runs, refuses a block (the signer is never invoked), enforces a spend cap, and can issue a twzrd.payment_decision.v1 record from its decision, signed with your own signer. | Decisions come from the hosted checks; pairs with x402-solana or @x402/fetch as the payer. | npm install twzrd-x402-gate |
twzrd-preflight | OpenClaw plugin: assign its wrapped fetch to the client and every 402 that passes through it is checked before a signer can attach payment (enforce and fail-closed by default). | Matches the gate's wrapper and adds OpenClaw tool-call gating, against the hosted checks. Payments outside the wrapped fetch (a ClawRouter proxy, unparsed exec or curl) are not covered. | npm install twzrd-preflight |
twzrd-receipt-verifier | Verifies a TWZRD receipt offline against a published Ed25519 key: no wallet, no API key, no trust in TWZRD's server. | Checks the signed receipts that the hosted checks issue. | npx twzrd-receipt-verifier or pip install twzrd-receipt-verifier |
| twzrd-mcp-server / twzrd-mcp | A local MCP client with 6 tools that pays the $0.001 and $0.05 calls itself under a spend cap (a wallet only if you enable paid calls). | Calls the hos
Nur der Anfang wird gezeigt; den Rest findest du im Repo