Penniless Data Utilities
REMOTE · PENNILESS-JSON-REPAIR.SJAMAN.WORKERS.DEV · SCANNED SEP 20
Ten x402-paid tools for JSON, YAML, cron, diff, text, DNS, WHOIS, GitHub, crypto, and email.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 841 tokens (~93/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Penniless Data Utilities MCP server?
Penniless Data Utilities is a hosted endpoint at https://penniless-json-repair.sjaman.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · penniless-json-repair.sjaman.workers.dev
claude mcp add --transport http danielarif26-penniless-data-utilities 'https://penniless-json-repair.sjaman.workers.dev/mcp'
{
"mcpServers": {
"danielarif26-penniless-data-utilities": {
"url": "https://penniless-json-repair.sjaman.workers.dev/mcp"
}
}
} {
"servers": {
"danielarif26-penniless-data-utilities": {
"type": "http",
"url": "https://penniless-json-repair.sjaman.workers.dev/mcp"
}
}
} [mcp_servers.danielarif26-penniless-data-utilities] url = "https://penniless-json-repair.sjaman.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"danielarif26-penniless-data-utilities": {
"type": "remote",
"url": "https://penniless-json-repair.sjaman.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add danielarif26-penniless-data-utilities --url 'https://penniless-json-repair.sjaman.workers.dev/mcp' --transport streamable-http
mcp_servers:
danielarif26-penniless-data-utilities:
url: "https://penniless-json-repair.sjaman.workers.dev/mcp" {
"McpServers": {
"danielarif26-penniless-data-utilities": {
"Transport": "http",
"Url": "https://penniless-json-repair.sjaman.workers.dev/mcp"
}
}
} assistant mcp add danielarif26-penniless-data-utilities -t streamable-http -u 'https://penniless-json-repair.sjaman.workers.dev/mcp'
{
"mcpServers": {
"danielarif26-penniless-data-utilities": {
"type": "http",
"url": "https://penniless-json-repair.sjaman.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://penniless-json-repair.sjaman.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sjaman.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 676bad790b8ad4cca11b7ecf70cec4c936c |
| SANs: *.sjaman.workers.dev, sjaman.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of penniless-json-repair.sjaman.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://penniless-json-repair.sjaman.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://penniless-json-repair.sjaman.workers.dev/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cron_next_run Penniless Cron Next Run ~91
Computes the next UTC fire time for a 5-field cron expression (supports steps, ranges, lists, and month/weekday names). Body {expr, after?} -> {ok, next, epochMs}. Costs $0.001 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | ISO timestamp to search after (default now) |
| expr | string | yes | 5-field cron expression |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
dns_lookup Penniless DNS Lookup ~95
JSON DNS-over-HTTPS lookup for A, AAAA, CNAME, MX, TXT, NS, SOA, PTR, SRV, CAA. Body {domain, type?} -> {ok, domain, type, status, answers[]}. Costs $0.001 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Hostname to resolve |
| type | string | – | Record type (default A) |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
domain_whois Penniless WHOIS Lookup ~87
Structured WHOIS via RDAP for any domain: registrar, IANA id, statuses, expiry/registration dates, nameservers, DNSSEC. Body {domain} -> {ok, found, domain, registrar, status[], events{}, nameservers[], dnssec}. Costs $0.001 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, no scheme |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
email_validate Penniless Email Validate ~65
Email deliverability check: RFC-style syntax plus live MX probe of the domain. Body {email} -> {ok, valid, formatValid, domainHasMx, mx[]}. Costs $0.001 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
github_repo_stats Penniless GitHub Repo Stats ~83
Popularity and metadata for any public GitHub repo: stars, forks, open issues, watchers, language, license, topics, last push. Body {repo} -> {ok, found, stars, forks, openIssues, language, license, pushedAt}. Costs $0.001 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | owner/name |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
repair_json Penniless JSON Repair ~87
Repairs malformed LLM JSON: strips Markdown fences and prose wrappers, fixes trailing commas, converts Python literals (True/False/None) and single/unquoted keys, removes comments, recovers balanced JSON from truncated output. Body {input} -> {ok, repaired, applied}. Costs $0.001 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Malformed JSON text |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
text_diff Penniless Text Diff ~101
Produces a unified diff plus added/removed counts between two texts (LCS line diff, configurable context lines). Body {old, new, context?} -> {ok, identical, added, removed, hunks, unified}. Costs $0.001 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| context | number | – | Context lines per hunk (default 3) |
| new | string | yes | Changed text |
| old | string | yes | Original text |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
text_extract Penniless Text Extract ~105
Extracts clean text, title, headings, links, URLs, and emails from HTML or plain text. Body {input, numbers?, codeBlocks?} -> {ok, source, title, headings, links, urls, emails, text}. Costs $0.001 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| codeBlocks | boolean | – | Keep pre/code blocks |
| input | string | yes | HTML or plain text |
| numbers | boolean | – | Keep numeric strings in text output |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
yaml_to_json Penniless YAML to JSON ~68
Converts a YAML subset (block maps, sequences, nested indentation, scalars, comments) into JSON with no runtime dependency. Body {input} -> {ok, value, warnings}. Costs $0.001 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | YAML document text |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
What is the Penniless Data Utilities MCP server?
Penniless Data Utilities is an MCP server listed in the public MCP registry as io.github.danielarif26/penniless-data-utilities. Ten x402-paid tools for JSON, YAML, cron, diff, text, DNS, WHOIS, GitHub, crypto, and email. This page covers its hosted endpoint (https://penniless-json-repair.sjaman.workers.dev/mcp).
Is the Penniless Data Utilities MCP server safe to use?
Penniless Data Utilities scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Penniless Data Utilities MCP server expose?
Penniless Data Utilities exposes 9 tools: repair_json, yaml_to_json, cron_next_run, text_diff, text_extract, and 4 more. Their descriptions and schemas cost roughly 782 tokens of context every time the server is loaded.
Does the Penniless Data Utilities MCP server require authentication?
No. We connected to Penniless Data Utilities without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Penniless Data Utilities MCP server still maintained?
Penniless Data Utilities is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.