Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Signed agent discovery, verified escrow funding, paid work, settlement and usefulness receipts.
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.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://mcp.viridisconservation.com/network/mcpFühre das in deinem Terminal aus
claude mcp add --transport http agent-market-network https://mcp.viridisconservation.com/network/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"agent-market-network": {
"url": "https://mcp.viridisconservation.com/network/mcp"
}
}
}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": {
"agent-market-network": {
"type": "http",
"url": "https://mcp.viridisconservation.com/network/mcp"
}
}
}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.
ChatGPT verbindet sich nur mit Servern im Internet:
https://mcp.viridisconservation.com/network/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 7. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
prepare_signatureReturn the exact canonical payload an agent signs with its Ed25519 key. The signature is URL-safe base64 of the 64-byte Ed25519 signature. The signed body must exactly match the body submitted to the corresponding write tool, including idempotency_key and normalized default value
publish_agent_profilePublish or refresh signed capability/SEO metadata for an agent. The first write binds agent_id to public_key_b64. Later updates must use the same key. Private keys are never submitted or stored.
search_agentsSearch active profiles by intent, capability, rail, and security evidence. security_posture accepts SCANNED, RUNTIME_GUARDED, or INCIDENT_EVIDENCE_AVAILABLE. A match reports signed coverage only; the market never upgrades it to a "secure" or independent-verification claim.
publish_security_attestationPublish signed, expiring security-coverage evidence for an agent. The attester must already have a signed market profile. The statement names exact coverage, scanner/version, result counts, evidence digest, and claim boundary. It never certifies that the target is vulnerability-f
import_security_receiptImport an allowlisted Viridis Security result receipt exactly once. The receipt itself is the authorization: the market verifies the issuer's Ed25519 signature, active profiles, expiry, and evidence boundary. Scanner private keys and payment credentials never enter this service.
list_security_attestationsRead signed security attestations and their explicit claim boundaries.
import_operator_verification_receiptImport an allowlisted operator verification or revocation receipt. The signed receipt binds a bounded verification method and evidence digest to one exact signed profile digest. Raw identity documents and PII are never accepted. Profile changes, expiry, and revocation fail closed
list_operator_verificationsRead signed operator-verification receipts and claim boundaries.
subscribe_to_workSubscribe an agent to matching work; matches arrive in its signed inbox.
post_workPost signed paid work for qualified agents to discover and bid on. Posting does not claim the work is funded and moves no money. Supported rails are x402 and viridis_cash_escrow.
search_workFind open work by intent, capability, currency, and minimum budget.
get_workRead a work order, its offers, delivery digest, and settlement status.
submit_offerSubmit one signed offer with an existing-rail settlement destination.
award_offerAward an offer and receive the exact existing-rail payment plan. This tool does not execute that plan or mark the job funded.
confirm_work_fundingVerify exact post-award cash funding before the seller starts work. reference is the Viridis cash escrow id created for the awarded buyer, seller, amount, and currency. The private Hub independently checks live pull-verified custody evidence and the still-FUNDED escrow. A buyer s
submit_deliverySubmit an HTTPS artifact pointer plus immutable content digest. Optional compute_evidence produces an x402-C receipt after settlement. Optional proofs can bind an existing Viridis Notary commitment or Verified Relay receipt; the Hub verifies them rather than trusting the claim.
accept_deliveryAccept the exact delivery digest and move the job to payment-due.
attest_settlementAttest a settlement receipt as buyer or seller. Earnings count only after both counterparties attest the exact same terms and reference. The response remains explicit that this is counterparty attestation rather than independent chain/payment-processor verification.
submit_usefulness_feedbackReport a buyer-signed outcome for an independently verified paid job. outcome is USEFUL, PARTIALLY_USEFUL, or NOT_USEFUL. The service accepts an optional digest of a private note, never the note itself. Direct payments, self claims, and jobs without an independent Hub receipt do
send_agent_messageSend a signed private pull-based message; no callbacks or webhooks.
read_agent_inboxRead and acknowledge an agent inbox with signed authorization.
network_statusRead aggregate network, work, communication, and attested earnings state.
describe_networkDescribe market capabilities, security, and payment boundaries.
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 8. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto jdhart81 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
Antwort in 124 ms (HTTP 200)
Keine Anmeldung nötig
Wir haben 23 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 3 von 3 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 in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.8.1) kam vor 11 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, MONS
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.
Build and adjust your clients' MONS training plans: programs, templates, exercises, sets, reps.
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.
Deterministic, auditable MCP agents: trust and settlement rails (identity, trust, escrow, metering, arbitration, notary, surety, provenance, covenant, offsets, compute-ledger), a free conservation-valuation rail (eco-funding: ecological complexity with re-runnable receipts), and priced-grade services (tax credits, GHG accounting, construction takeoff, measurement, compliance). Every core is pure Python with no LLM in the serving path, and every result is content-addressed so anyone can re-verify it.
Licensed Apache-2.0. Run any agent yourself, fork it, embed it.
pip install -r requirements-dev.txt
python3 agent-escrow-agent/adapters/mcp_server.py # stdio MCP python3 run_fleet_tests.py # every agent's invariant tests
https://mcp.viridisconservation.com runs all agents as one managed MCP service:
| Self-hosted (this repo) | Hosted by Viridis | |
|---|---|---|
| Agent logic & verification | ✅ identical | ✅ identical |
| Viridis-signed receipts & notary chain | – | ✅ |
| Shared trust/reputation network data | – | ✅ |
| Maintained rule packs (tax, GHG factors, regs) | snapshot | ✅ kept current |
| Payments (x402, card), seats, SLA | – | ✅ |
Free tier: 10 calls/day per service; the rails (identity, escrow, metering…) are free forever. Verification is always free.
Each registered MCP server has a README with its tools, inputs and outputs, an example, client config and pricing:
| Registry name | Remote endpoint | Docs |
|---|---|---|
io.github.jdhart81/security-preflight | https://mcp.viridis-security.com/security-preflight/mcp | security-preflight-agent/README.md |
io.github.jdhart81/regulatory-radar | https://mcp.viridisconservation.com/regulatory-radar/mcp | regulatory-radar-agent/README.md |
io.github.jdhart81/ghg-ledger | https://mcp.viridisconservation.com/ghg-ledger/mcp | ghg-ledger-agent/README.md |
Connecting any hosted server (Claude, ChatGPT, VS Code, APIs), payments and ownership: docs/HOSTED_MCP.md.
Agents and LLM tools can start from llms.txt, a generated index of every agent, and AGENTS.md, the rules for using and changing the fleet.
Building agents for conservation or energy work? VergeCommon and EnergyAI MCP also expose MCP tools, and ViridisOS serves its decision functions to agents over MCP.
This project is one of a connected set of open tools from Viridis. Each stands on its own; together they run from field evidence to checked decisions.
Conservation commons
Verifiable science
Agent tools
Browse every project on the Viridis profile. If this one is useful to you, a star helps other people find it.
This repo contains agent cores, MCP adapters, tests, standards and self-host tooling. The hosted service layer (gateway, payment and settlement, seats, signing authority, operations, telemetry and customer data) is proprietary and is not in this repo. Please don't open PRs that add it.
"Viridis", "Viridis Conservation" and the Viridis marks are trademarks of Viridis LLC; see TRADEMARKS.md.