原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

PrepLayer.ai

作者:maximusboomerus-afk版本 0.2.1i★ –i在云端运行
注册名称com.maximusmediahouse/preplayer

安装

概览

作者提供的说明(英文原文)

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude:

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址,然后点击 Add
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://api.maximusmediahouse.com/mcp

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "preplayer": {
      "url": "https://api.maximusmediahouse.com/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "preplayer": {
      "type": "http",
      "url": "https://api.maximusmediahouse.com/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

ChatGPT 只能连接互联网上的服务器:

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
  3. 粘贴下面的地址,起个名字,然后保存
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://api.maximusmediahouse.com/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月7日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • 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

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ! 注意

    作者与仓库一致

    发布者(maximusmediahouse.com)不是仓库所有者(maximusboomerus-afk);可能是其他人代为上架的

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • ✓ 通过

    端点有响应

    在 318 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 16 个工具描述,未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 18352 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 18352 个服务器的 79% 更新
  • 基础检查结果等于或优于此分类中其他 18352 个服务器的 36%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

PrepLayer.ai 安全吗?

它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.2.1)于11天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Hunter Killer

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

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

在云端运行★ 211前天更新
安装

Hunter Killer

作者:Irishman-Management-LLC

Liquidation walls, snapshot age, evidence labels and a public record. Managed OAuth.

在云端运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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