Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Bewertungen und Benutzerkonten folgen in einem späteren Schritt.
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt
Einsteigermodus An
FarbenSystemHellDunkel
SpracheไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenüEinstellungen
Einsteigermodus An
FarbenSystemHellDunkel
SpracheไทยEnglish中文日本語한국어EspañolDeutsch

PrepLayer.ai

von maximusboomerus-afkVersion 0.2.1i★ –iLäuft in der Cloud
Name in der Registrycom.maximusmediahouse/preplayer

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

Deterministic text prep for agents. Pay per call via x402 USDC.

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

  • Verbindung: Läuft in der Cloud
  • Transport: Streamable HTTP
  • Kategorie: Sonstiges

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

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:

  1. Öffne Settings → Connectors
  2. Tippe auf Add custom connector
  3. Füge die Adresse unten ein und tippe auf Add
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Add2https://…3
https://api.maximusmediahouse.com/mcp

Führe das in deinem Terminal aus

claude mcp add --transport http preplayer https://api.maximusmediahouse.com/mcp

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "preplayer": {
      "url": "https://api.maximusmediahouse.com/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 VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "preplayer": {
      "type": "http",
      "url": "https://api.maximusmediahouse.com/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:

  1. Öffne ChatGPT im Web → Settings → Connectors (Apps)
  2. Tippe auf Create oder Add (bei manchen Tarifen musst du zuerst Developer mode unter Advanced einschalten)
  3. Füge die Adresse unten ein, gib ihr einen Namen und speichere
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Create2https://…3
https://api.maximusmediahouse.com/mcp

Menü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.

Was er kann

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.

  • normalize

    Deterministic text normalization: Unicode NFKC, zero-width/bidi stripping, smart-quote and dash folding, whitespace collapse, case folding. Returns a stable content hash so two texts can be compared for exact equality. $0.002 USDC per successful call (x402, client-paid); failed c

  • validate

    Validate and canonicalize one identifier: email, URL, E.164 phone, IBAN (mod-97), payment card (Luhn), UUID, SHA-256, git SHA, EVM address (EIP-55) or domain. Returns {valid, canonical, fingerprint}. $0.002 USDC per successful call (x402, client-paid); failed calls are not charge

  • extract

    Extract structured fields from unstructured text with byte offsets and normalized values: emails, URLs, IPv4, phones, money amounts, ISO dates, UUIDs, EVM addresses, SKUs, semver. $0.005 USDC per successful call (x402, client-paid); failed calls are not charged.

  • redact

    Redact PII from text before it is stored or logged. Returns redacted text plus exact byte spans and counts per class: credit_card, iban, email, private_key, evm_address, phone, ipv4, url. $0.005 USDC per successful call (x402, client-paid); failed calls are not charged.

  • classify

    Rule-based multi-label text classification over a fixed taxonomy (urgency, financial_promise, credential_request, crypto_mention, cta, legal_offer, medical_claim, seo_spam, url_shortener, press_release, question, has_contact). Deterministic - identical text always yields identica

  • dedupe

    Near-duplicate detection across a batch of documents. Exact Jaccard similarity over word-3-shingle sets decides duplication; a 64-bit SimHash is returned per document as a compact content fingerprint. Up to 200 documents per call. $0.01 USDC per successful call (x402, client-paid

  • diff

    Line-level LCS diff of two text blobs. Returns a structured edit script with insertions, deletions, unchanged line counts and per-operation metadata; with format='unified' also returns a unified-diff string. $0.005 USDC per successful call (x402, client-paid); failed calls are no

  • chunk

    Split long text into pieces for RAG retrieval. Strategies: 'sentence' packs whole sentences into a size budget and never splits mid-sentence; 'paragraph' prefers \n\n boundaries; 'fixed' is a hard char window with overlap. The highest-value endpoint for agents that build retrieva

  • extract_custom

    Pull caller-defined structured fields from text using regex patterns with deterministic type coercion. Supported types: string, bool, date, url, email, number. Returns {fields: {name: value|null}, found, missing}. Pure deterministic — no LLM call. $0.005 USDC per successful call

  • validate_json

    Deterministic JSON-Schema subset validator. Catches malformed JSON before it breaks a pipeline. Supports: type, required, properties, items, minLength, maxLength, pattern, enum, minimum, maximum, additionalProperties. No external dependencies. $0.003 USDC per successful call (x40

  • slugify

    URL-safe slug from arbitrary text. NFKD-decomposes unicode (é -> e), lowercases, replaces every non-[a-z0-9] run with a separator, strips leading/trailing separators, truncates on separator boundaries (never mid-word). $0.002 USDC per successful call (x402, client-paid); failed c

  • hash

    Content-addressable hashing for caching and dedup. Three algorithms: sha256 (via node:crypto / Web Crypto), xxhash64 and murmur3 (inline pure-JS, deterministic across runs). Returns hex digest + algorithm + byte count. $0.002 USDC per successful call (x402, client-paid); failed c

  • batch

    Run up to 10 primitive calls in one round trip for one x402 payment of $0.02 (= $0.0020 per call, below the priciest single-call route at $0.01). Each request names an `endpoint` (normalize, validate, extract, redact, classify, dedupe, diff, chunk, extract_custom, validate_json,

  • batch50

    Run up to 50 primitive calls in one round trip. One x402 payment of $0.075 (=$0.0015 per call — cheaper per call than the 10-slot batch). Same `{endpoint, input}` request shape as /v1/batch; the response carries up to 50 results in order. Built for a production buyer running a wh

  • batch100

    Run up to 100 primitive calls in one round trip. One x402 payment of $0.100 (=$0.0010 per call — the deepest rung of the batch ladder, cheaper per call than the 10- and 50-slot batches). Same `{endpoint, input}` request shape as /v1/batch. The volume mechanic for a corpus-holding

  • subscription

    Recurring tier: a PREPAID CALL BALANCE. One x402 payment of $1.00 credits 1,000 units of prepaid capacity (= $0.0010 per call), drawn down across sessions on the cheap deterministic routes (<= $0.01). The funded balance is the source of truth, queryable at GET /v1/subscription/ba

Basischecksi

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

  • ! Vorsicht

    Entwickler passt zum Repo

    Der Herausgeber (maximusmediahouse.com) ist nicht der Repo-Inhaber (maximusboomerus-afk); vielleicht hat jemand anderes ihn eingetragen

  • … Noch nicht geprüft

    Wird noch gepflegt

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Hat eine Lizenz

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 318 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 16 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Sonstigesi

  • Mehr Sterne als 0 % der anderen 32683 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 77 % der anderen 32683 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 37 % der anderen 32683 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist PrepLayer.ai sicher?

Er hat 2 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.

Welche Schlüssel oder Codes braucht er?

Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.

Läuft er auf meinem Computer oder in der Cloud?

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.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.2.1) kam vor 10 Tagen in die Registry.

Welche Apps können ihn nutzen?

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.

Was kann ich stattdessen nutzen?

In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper

Alternativen

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

Spec Driven Development

von formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Läuft auf deinem Computer★ 440MITAktualisiert vor 14 Monaten
Installieren

Remote Desktop Commander

von desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Läuft in der Cloud★ 211Aktualisiert vorgestern
Installieren

README vom Entwickler

README öffnen

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.

PrepLayer.ai

Twelve x402-paid deterministic text primitives for AI agents.

Pay per call in USDC. No API keys, no accounts, no signup.

Base URL: https://preplayer.maximusboomerus.workers.dev Mirror URL (production): https://api.maximusmediahouse.com MCP endpoint: https://preplayer.maximus-boomerus.workers.dev/mcp (streamable-http, POST) Service version: 0.2.0

What this is

PrepLayer is a single Cloudflare Worker exposing twelve deterministic text prep primitives behind one MCP server. Each call costs a few cents in USDC and is paid for on the wire via the x402 protocol — the agent signs a TransferWithAuthorization (EIP-3009) against USDC, the Worker verifies the signature with the Coinbase Developer Platform facilitator, and the call runs.

The primitives are the boring text work an agent has to do before it can think: normalize whitespace, validate an identifier, hash content for a cache key, dedupe a document set, redact PII before logging, chunk for RAG, diff two blobs. Each primitive is pure — identical input always produces identical output — so results are content-addressable and safe to cache.

What's not in this repo

The MCP server and Worker source live in a private working tree. This repo is the public landing surface: discovery, manifest, license, security contact, and a small example showing how a payer actually executes a paid call. If you want to self-host the worker, see docs/METHODOLOGY.md for what you'd need to stand up — none of the secrets are here on purpose.

Endpoints

Every paid endpoint is POST and gated with x402. The first call without payment returns 402 Payment Required with a PAYMENT-REQUIRED header (base64 JSON) and a PAYMENT-REQUIRED JSON body describing the challenge. The second call carries a PAYMENT-SIGNATURE header (base64 JSON) and returns 200.

Twelve text primitives
EndpointPathSingle price (Base)Per call
normalize/v1/normalize$0.0022 000 atomic units
validate/v1/validate$0.0022 000 atomic units
slugify/v1/slugify$0.0022 000 atomic units
hash/v1/hash$0.0022 000 atomic units
classify/v1/classify$0.0033 000 atomic units
validate_json/v1/validate_json$0.0033 000 atomic units
extract/v1/extract$0.0055 000 atomic units
redact/v1/redact$0.0055 000 atomic units
diff/v1/diff$0.0055 000 atomic units
chunk/v1/chunk$0.0055 000 atomic units
extract_custom/v1/extract_custom$0.0055 000 atomic units
dedupe/v1/dedupe$0.0110 000 atomic units

Prices on Polygon and Arbitrum One are ×1.2; prices on Base, Base Sepolia, and Solana mainnet are ×1.0. Atomic units are 6-decimal USDC.

Three additional endpoints
EndpointPathPriceStatus
batch/v1/batch$0.40 / 10 calls ($0.04 each)real — single x402 payment, up to 10 sub-requests
subscription/v1/subscription$200 / 10 000 calls / monthspec only — returns 501; the design is documented in docs/METHODOLOGY.md, will not charge real USDC until the D1 store is in place
priority/v1/priorityn/aspec only — returns 501; we will not charge 2× for a latency SLA we cannot guarantee on a single-instance Worker
Free endpoints (never charged)
PathPurpose
/.well-known/x402x402 Bazaar service descriptor (15 resources, networks, prices)
/v1/manifest.jsonMCP tool list with full JSON-Schema and per-network pricing
/server.jsonMCP registry manifest (this file's companion)
/landingHTML landing page
/llms.txt, /llms-full.txtPlain-text references for LLM crawlers
/robots.txt, /bazaar-extension.jsonDiscovery aids

Payment flow

PrepLayer is paid through x402 — HTTP's 402 Payment Required made useful. The wire:

  1. POST an endpoint with the tool's JSON body and no payment header. The server returns 402 with a PAYMENT-REQUIRED header (base64 JSON challenge) describing the scheme, network, asset, amount, treasury address, and an EIP-712 domain.
  2. The caller signs an EIP-3009 TransferWithAuthorization message against the USDC contract on the selected network and base64-encodes the resulting PaymentPayload into a PAYMENT-SIGNATURE header.
  3. POST again with that header. The server verifies the signature with the CDP facilitator (https://api.cdp.coinbase.com/platform/v2/x402), executes the tool, and returns 200 with a PAYMENT-RESPONSE header containing the settlement receipt.

The v2 protocol on the wire:

  • Header on 402: PAYMENT-REQUIRED (base64 JSON; lowercase header name as the Worker emits it).
  • Header on 200: PAYMENT-SIGNATURE (base64 JSON; ditto).
  • Header on 200 (settle receipt): PAYMENT-RESPONSE (base64 JSON).
  • Scheme: exact. Networks: eip155:8453, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, eip155:137, eip155:42161, eip155:84532 (Base Sepolia, test only).
  • Asset: USDC.
  • Treasury: 0x8cb59b1bffb39c130ab85a8177e93eae9ddbaf10.
  • Facilitator: https://api.cdp.coinbase.com/platform/v2/x402 (Coinbase Developer Platform; the path matters — /v2/x402 404s and is the wrong URL).
Example: probe-only (no payment required)

The probe below is always safe to run — it returns the 402 challenge and never spends anything. Use it to verify connectivity, the treasury address, and the per-network price.

curl -i -X POST https://preplayer.maximus-boomerus.workers.dev/v1/normalize \

-H 'content-type: application/json' \ --data '{"text":"Hello\u200b, World!"}'

The response is HTTP/2 402, with:

PAYMENT-REQUIRED: eyJ4NDAyVmVyc2lvbiI6...

Decoded, the body is a JSON object describing the accepted (scheme, network, amount, asset, payTo). See examples/probe.mjs for a runnable version that decodes the base64 challenge and prints it.

Example: a paid call (Node.js, viem + @x402/core/evm)

The real paid flow needs a wallet — there is no honest way to do it with bare curl. examples/paid-call.mjs shows the verified-working pattern (EIP-3009 signing via @x402/evm/exact/client, header encoding via @x402/core/client's x402HTTPClient.encodePaymentSignatureHeader). To run it:

npm install viem @x402/core @x402/evm

PAYER_PRIVATE_KEY=0x<64 hex chars> node examples/paid-call.mjs

The script signs a single call to /v1/dedupe, prints the first 18 chars of the EIP-712 signature (never the key, never the full signature), and prints the PAYMENT-RESPONSE settlement receipt on success. The same machinery handles the other 11 primitives and batch.

Never commit, log, or paste your `PAYER_PRIVATE_KEY`. A leaked private key is unrecoverable loss of USDC.

MCP install

Any MCP client that supports streamable-http can drive PrepLayer by pointing at:

https://preplayer.maximus-boomerus.workers.dev/mcp

The server returns the full tool list (normalize, validate, extract, redact, classify, dedupe, diff, chunk, extract_custom, validate_json, slugify, hash, batch, subscription, priority) on tools/list. Each tool call goes through x402 like any other HTTP call — the MCP layer is a thin transport.

If you are writing your own MCP client: the initialize handshake is JSON-RPC 2.0 over HTTP POST with Content-Type: application/json and Accept: application/json, text/event-stream. tools/call is a paid request that returns the same 402 / PAYMENT-SIGNATURE round-trip as the bare HTTP path.

Known limitations (read this)

This service is honest about what it is and what it isn't.

1. The character-fidelity ceiling is approximately 6.5 out of 10

normalize, slugify, and extract do Unicode folding to a fixed ASCII surface. That's the whole point — content hashes stay stable across whitespace, smart-quote, and accent variants — but it means we strip diacritics, we don't preserve them round-trip. "naïve café" becomes "naive cafe". If you need Unicode-preserving normalization (e.g. NFKC without NFKD), this is the wrong tool.

2. Two tiers are spec-only, not live

subscription ($200 / 10 000 calls / month) and priority (X-Priority: high, no published price) both return 501 Not Implemented today. The manifest advertises them so x402 directories render the full tier ladder, but the Worker has no D1 store backing subscriptions and no SLA behind the priority tier. Do not pay into either yet — the server will refuse the call regardless of whether the signature is valid.

3. Single-instance Worker, no SLA

One Cloudflare Worker, no Durable-Object-backed request queueing. Latency P99 is unmeasured but the Worker can be cold-started after a deploy, and a single misbehaving caller can pin a CPU slot for several seconds on extract_custom with a malicious regex (we have a static guard and a 10 KB subject cap, but no economic rate limit beyond that). Treat this as a beta: useful for research workloads, not yet a fit for time-sensitive production pipelines.

4. CDP facilitator dependency

Settlement goes through Coinbase Developer Platform's x402 endpoint. If the CDP facilitator is down, every paid call will 503 regardless of how good the signature is. We have no in-process fallback. Mirror status: https://status.coinbase.com/.

5. No replay window other than the per-payload nonce

A successfully-paid call cannot be replayed against the same endpoint (the Worker uses a Durable Object keyed by payment nonce, exactly-once under concurrency), but the same signed payment can be replayed once per Worker instance across different endpoints if the JSON body changes to fit. If you fork this for production, add a per-tool-keyed replay set on top of the per-payload nonce.

6. Receipt contents have changed once and may change again

Between 0.1.0 and 0.2.0 the receipt field list moved (the facilitator field used to read "mock-cdp" during Phase 1; it now reads the real facilitator URL). Anything that scrapes receipts and pins the field names needs an update if the settlement envelope changes in a future minor version.

Discovery

These URLs never charge and never rate-limit:

Status

The Worker is in 0.2.0. It was red-teamed (preplayer_redteam_2026-10-19.md in the project notes) before paid real USDC was accepted; the payment bypass, replay, ReDoS, and price-tier findings are closed. Two P3 items (HEAD → 404 not 405, duplicate 402 in MCP structuredContent) remain open. The Worker has been serving real EIP-3009-signed USDC calls against the CDP facilitator since Phase 2.

License

MIT — see LICENSE. Service source is private; this repo and the endpoints it documents are MIT.

PopNx fragen