penniless-data-utilities
Provides tools for retrieving GitHub repository statistics, such as stars, forks, open issues, language, and license.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@penniless-data-utilitiesrepair this broken JSON: {foo: 'bar',}"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Penniless Data Utilities
Nine deterministic data and lookup tools for AI agents, paid per call in USDC. REST advertises both native MPP and x402; MCP uses x402 v2. No accounts, no API keys, no rate-limit tiers. Every tool is pure computation or a keyless public lookup — none of them call another AI model, so results are reproducible.
Live endpoint (MCP): https://penniless-json-repair.sjaman.workers.dev/mcp
Live endpoint (REST): https://penniless-json-repair.sjaman.workers.dev
Discovery:
/health,/openapi.json,/llms.txt,/.well-known/x402
Pricing
$0.001 USDC per call. REST advertises native MPP plus x402 v2 (eip155:8453, scheme exact); MCP uses x402 v2.
Base x402 settlements are verified by the free-tier PayAI facilitator. Native MPP is negotiated by mppx. Recipient (payTo): 0x3D98800c64C345950E1eAaa076D88C12d1BF5F37.
Related MCP server: obfus.link
Connect over MCP
Any MCP client that speaks streamable HTTP can connect directly:
{
"mcpServers": {
"penniless-data-utilities": {
"type": "http",
"url": "https://penniless-json-repair.sjaman.workers.dev/mcp"
}
}
}The transport is stateless — no session id is issued or required, and every
request is independent. initialize and tools/list are free. An unpaid
tools/call returns an x402 payment-required payload in result.content[0].text
(and result.structuredContent); attach the signed payment as
params._meta["x402/payment"] and repeat the call.
If you use an x402-aware MCP client, @x402/mcp handles that exchange for you.
Tools
MCP name | REST path | Arguments | Returns |
|
|
| repaired JSON + which fixes applied |
|
|
| parsed value + warnings |
|
|
| next UTC fire time |
|
|
| unified diff + counts |
|
|
| text, title, headings, links, URLs, emails |
|
|
| registrar, statuses, expiry, nameservers, DNSSEC |
|
|
| DoH answers for A/AAAA/CNAME/MX/TXT/NS/SOA/PTR/SRV/CAA |
|
|
| stars, forks, open issues, language, license |
|
|
| syntax + live MX deliverability |
POST /diagnose is free: it classifies what is wrong with a malformed JSON
payload without returning the repaired output, so a caller can check whether
paying is worthwhile before paying.
Example (REST + x402 client)
Any x402 v2 client works. With the reference TypeScript client and a viem account:
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { wrapFetchWithPayment } from "@x402/fetch";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client();
registerExactEvmScheme(client, { signer: privateKeyToAccount(key), networks: ["eip155:8453"] });
const pay = wrapFetchWithPayment(fetch, client);
const res = await pay("https://penniless-json-repair.sjaman.workers.dev/repair/json", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({ input: "{foo: 'bar',}" }),
});
// -> { ok: true, repaired: { foo: "bar" }, applied: ["unquoted-keys","single-quotes","trailing-commas"] }wrapFetchWithPayment handles the 402 round-trip: it receives the requirement,
signs the USDC authorization, retries, and only returns a 200 once the
facilitator has settled.
Development
npm install
npm test # 133 tests, runs fully offline (facilitator + upstream are injected)
npx wrangler dev
npx wrangler deployEnvironment (set in wrangler.toml): X402_NETWORK, X402_FACILITATOR,
X402_PRICE, X402_PAY_TO. Production also has an encrypted Cloudflare secret
MPP_SECRET_KEY used only to authenticate MPP challenges. Wallet private keys are
never deployed to the Worker.
Maintainer
GitHub: @danielarif26
This server cannot be deployed
Maintenance
Related MCP Connectors
49 developer tools via MCP: DNS, WHOIS, IP lookup, JWT, hashing, QR, and more.
Repair malformed JSON, DNS lookup, extract URLs, base64, case, hash, time. Pay per call USDC Base.
8 pay-per-call web intel tools over MCP. Free discovery, calls settle in USDC on Base (x402).
Paid MCP tools behind one endpoint. Agents pay per call in USDC on Base via x402.
1
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server providing 22 pay-per-call utility tools for AI agents (scrape, validate, embed, store, moderate, notify, convert, prevent loops) without accounts or API keys, using USDC payments via the x402 protocol.1738 npm1MIT
- AlicenseNot gradedqualityDmaintenanceOffers 31 deterministic developer tools (obfuscators, encoders, converters, validators) on a lean, machine-payable MCP endpoint.MIT
- AlicenseAqualityCmaintenanceProvides deterministic micro-utilities as an MCP server, including free tools for conversion, text processing, hashing, encoding, ID generation, and regex, plus paid per-call tools for timezone, cron, RRULE, currency, diff, JSON Schema validation, and date math.13MIT
- FlicenseNot gradedqualityBmaintenanceProvides coding agents with 19 pay-per-call developer utilities, npm supply-chain security checks, and Base blockchain lookups, paid via USDC on Base using x402. No API key needed—payment acts as authentication.26 npm-