Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Web pages to clean Markdown for AI agents. 5 free calls/day, then pay per call via x402 on Base.
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://agentread.omar-cv.workers.dev/mcpFühre das in deinem Terminal aus
claude mcp add --transport http agentread https://agentread.omar-cv.workers.dev/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"agentread": {
"url": "https://agentread.omar-cv.workers.dev/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": {
"agentread": {
"type": "http",
"url": "https://agentread.omar-cv.workers.dev/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://agentread.omar-cv.workers.dev/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.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
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 omarhassanatef 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
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
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 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.2.0) kam vor 14 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, Rystic
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.
Start, seed, clock, inspect and diff Rystic API simulators from your agent.
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.
Clean web content for AI agents, paid per request.
AgentRead is a Cloudflare Worker that turns public web pages into clean, structured Markdown for LLMs and autonomous agents. It is exposed as both an HTTP API and a remote MCP server. Paid operations are charged per successful request with x402 micropayments (USDC on Base). There are no accounts, API keys or subscriptions.
| Operation | HTTP | MCP tool | Price (default) |
|---|---|---|---|
| Inspect a URL | POST /v1/inspect | inspect_url | free |
| Clean Markdown extraction | POST /v1/extract | extract_url | $0.003 |
| Structured extraction | POST /v1/extract/structured | extract_url_structured | $0.005 |
Free allowance: the first 5 successful extractions per day per client are free; just call without payment. Only successful extractions count, and the x-free-tier-remaining response header (MCP: _meta["agentread/free-tier"]) shows what's left. A global cap of 1,000 free calls per day protects the service. Prices and allowances are configuration, not code (see Configuration).
Service: https://agentread.omar-cv.workers.dev · MCP: https://agentread.omar-cv.workers.dev/mcp · Listed in the official MCP Registry as io.github.omarhassanatef/agentread and on x402scan
Try the free inspection:
curl -s -X POST https://agentread.omar-cv.workers.dev/v1/inspect \
-H 'content-type: application/json' -d '{"url":"https://example.com/"}'
Add it to an MCP client (inspect_url works in any client; the paid tools need an x402-capable client such as @x402/mcp):
claude mcp add --transport http agentread https://agentread.omar-cv.workers.dev/mcp
{ "mcpServers": { "agentread": { "url": "https://agentread.omar-cv.workers.dev/mcp" } } }
Pay per call from code with an x402 client: see Paying with an x402 client and MCP. Agent-readable docs: /llms.txt, /openapi.json, /.well-known/x402.
Status: MVP, live.
- Production (Base mainnet, real USDC): https://agentread.omar-cv.workers.dev. Payments settle via the CDP facilitator to
0xb866dD8C8401438Efb29b538ec4df11b6b407Ce6.
- Testnet: no hosted testnet.
npm run devruns locally against Base Sepolia and the free x402.org facilitator.
What has been verified:
- Automated tests: all pass (237 tests, run inside the Workers runtime).
- Directory checks: both paid endpoints pass the CDP Bazaar validator (all preflight checks) and the AgentCash/x402scan discovery audit, and are registered on x402scan.
- Local smoke test (9/9): run against
wrangler devusing the live x402.org facilitator. A genuinely signed payment from an unfunded wallet passes signature and requirement checks and is rejected forinsufficient_balance, so the live wire path is proven up to the transfer itself.
- Production deployment: passes all smoke checks from GitHub Actions (
gh workflow run CI). The live CDP facilitator authenticates AgentRead and verifies signed payments. The development network blocks theworkers.devIP range, hence the CI vantage point.
- Runs on the Workers Free plan. The deployed
liteengine had no CPU-limit kills in about 180 benchmark requests on Cloudflare's edge (Free account); thereadabilityengine was killed in up to 84% of them. See Extraction engines.
- Not yet exercised on the deployed edge: a *paid* extraction through the product Worker. The same extraction code was benchmarked on the edge, but no funded payment has gone through.
A funded payment has not yet been made (see Testnet payment demo). Read Limitations before relying on it.
Raw HTML is mostly noise: navigation, cookie banners, ads, scripts, styling. An agent that fetches pages itself wastes tokens and has to maintain HTML cleaning, SSRF protection, encoding detection, redirect handling and size limits. AgentRead does that once and returns predictable, versioned JSON.
x402 lets an agent pay a fraction of a cent per call from its own wallet. There is no sign-up and no stored credentials. Failed extractions are not charged.
That is a hypothesis to validate, not a proven market. The service logs the numbers needed to test it (see Observability).
AI agent ──HTTP (x402 headers)──┐ ┌── POST /v1/inspect ──────────────┐
▼ │ │ Cloudflare Worker (Hono) ▼ AI agent ──MCP Streamable HTTP──► /mcp ────┤ validate input + URL policy + DNS guard (x402 in _meta) │ (rejects bad input BEFORE any 402) │ │ ├── POST /v1/extract[/structured] │ │ └─ @x402/hono paymentMiddleware ──► facilitator /verify │ │ └── MCP paid tools ▼ └─ @x402/mcp wrapper shared operations (inspectUrl / extractUrl / extractUrlStructured) │ bounded fetch (manual redirects, re-validated each hop, timeout, byte cap) → linkedom → boilerplate removal → Readability → Turndown │ handler OK (2xx) → facilitator /settle → result + PAYMENT-RESPONSE handler failed → settlement cancelled → error (not charged)
@x402/hono for HTTP, @x402/mcp for MCP, and @x402/evm for the exact EVM scheme. No x402 protocol logic is reimplemented here.More detail: docs/architecture.md · docs/payments.md · docs/security.md · docs/demo.md
Machine-readable docs: GET / (discovery: operations, prices, limits) and GET /openapi.json (OpenAPI 3.1, generated from the zod schemas the service validates with).
All errors use one shape:
{ "error": { "code": "blocked_destination", "message": "Internal, reserved, or loopback hostnames are not allowed.", "details": {} } }
GET /healthcurl -s http://localhost:8787/health
POST /v1/inspect: freeChecks reachability and extractability before you pay. It downloads at most 64 KB and builds no DOM. Upstream problems (timeouts, 404s, non-HTML) are reported in the 200 body as reachable: false or a limitation. Only invalid or blocked URLs return 4xx.
curl -s -X POST http://localhost:8787/v1/inspect \
-H 'content-type: application/json' \ -d '{"url":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/402"}'
{
"schemaVersion": "1.0", "operation": "inspect_url", "requestedUrl": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/402", "normalizedUrl": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/402", "hostname": "developer.mozilla.org", "reachable": true, "statusCode": 200, "finalUrl": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/402", "redirects": 1, "contentType": "text/html", "contentLength": 209180, "isHtml": true, "title": "402 Payment Required - HTTP | MDN", "mayRequireJavaScript": false, "extractionSupported": true, "limitation": null }
POST /v1/extract: paidRequest body (JSON, max 8 KB; unknown fields are rejected):
| Field | Type | Default | Notes |
|---|---|---|---|
url | string | required | Absolute public http(s) URL, default port, no credentials, no IP literal, ≤ 2048 chars |
maxCharacters | integer | 20000 | 100 – 100000; Markdown is cut at a paragraph boundary |
includeLinks | boolean | true | false keeps link text but drops URLs and images |
Without payment, the response is HTTP 402. The PAYMENT-REQUIRED header carries the base64 x402 PaymentRequired object; the JSON body is a human/agent-readable summary:
curl -si -X POST http://localhost:8787/v1/extract \
-H 'content-type: application/json' -d '{"url":"https://example.com/"}'
Decoded PAYMENT-REQUIRED (accepts[0]): {"scheme":"exact","network":"eip155:84532","amount":"3000","asset":"0x036CbD53842c5426634e7929541eC2318f3dCF7e","payTo":" ","maxTimeoutSeconds":120,...}. 3000 is $0.003 in 6-decimal USDC.
With a valid PAYMENT-SIGNATURE header, the response is 200 with a PAYMENT-RESPONSE header containing the settlement receipt:
Real output for https://example.com/ (captured Oct 2026 by running the operation code directly):
{
"schemaVersion": "1.0", "operation": "extract_url", "requestedUrl": "https://example.com/", "finalUrl": "https://example.com/", "title": "Example Domain", "description": null, "markdown": "This domain is for use in documentation examples without needing permission. This is not a service; avoid relying on it for testing and monitoring purposes.", "headings": [], "truncated": false, "extraction": { "method": "readability", "statusCode": 200, "contentType": "text/html", "charset": "utf-8", "redirects": 0, "bytesFetched": 577, "characters": 156, "totalCharacters": 156, "words": 25, "warnings": [], "durationMs": 854 } }
extraction.method is one of readability, main-content-fallback, body-fallback, plain-text.
POST /v1/extract/structured: paidSame request body as /v1/extract. Returns metadata, Markdown, headings and links separately:
{
"schemaVersion": "1.0", "operation": "extract_url_structured", "requestedUrl": "...", "finalUrl": "...", "metadata": { "title": "...", "description": "...", "canonicalUrl": "...", "language": "en-GB", "siteName": "...", "byline": "...", "publishedTime": "2026-03-14T09:00:00Z" }, "markdown": "...", "headings": [{ "level": 2, "text": "Zones of the intertidal" }], "headingsTruncated": false, "links": [{ "text": "official tide tables", "url": "https://example.org/tide-tables" }], "linksTruncated": false, "truncated": false, "extraction": { "...": "same as extract_url" } }
Missing metadata is null; nothing is guessed. includeLinks affects only the Markdown; links is always returned (max 200, deduplicated, absol
Nur der Anfang wird gezeigt; den Rest findest du im Repo