# Penniless Data Utilities (remote · penniless-json-repair.sjaman.workers.dev)

Ten x402-paid tools for JSON, YAML, cron, diff, text, DNS, WHOIS, GitHub, crypto, and email.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `penniless-json-repair.sjaman.workers.dev`: 62/100 (this document), [markdown](https://verifymcp.io/servers/danielarif26-penniless-data-utilities/penniless-json-repair.md), [page](https://verifymcp.io/servers/danielarif26-penniless-data-utilities/penniless-json-repair)

## Channel facts

- Endpoint: `https://penniless-json-repair.sjaman.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 841 tokens (~93/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http danielarif26-penniless-data-utilities 'https://penniless-json-repair.sjaman.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "danielarif26-penniless-data-utilities": {
      "url": "https://penniless-json-repair.sjaman.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "danielarif26-penniless-data-utilities": {
      "type": "http",
      "url": "https://penniless-json-repair.sjaman.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.danielarif26-penniless-data-utilities]
url = "https://penniless-json-repair.sjaman.workers.dev/mcp"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add danielarif26-penniless-data-utilities --url 'https://penniless-json-repair.sjaman.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  danielarif26-penniless-data-utilities:
    url: "https://penniless-json-repair.sjaman.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "danielarif26-penniless-data-utilities": {
      "Transport": "http",
      "Url": "https://penniless-json-repair.sjaman.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add danielarif26-penniless-data-utilities -t streamable-http -u 'https://penniless-json-repair.sjaman.workers.dev/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 62, +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.

### 2026-09-18 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 61)

First indexed and scored.

## MCP tools (9)

### `repair_json` (~87 tokens)

Penniless JSON Repair

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.

Input parameters:

- `input` (string, required): Malformed JSON text

Output parameters:

- `ok` (boolean)

### `yaml_to_json` (~68 tokens)

Penniless YAML to JSON

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.

Input parameters:

- `input` (string, required): YAML document text

Output parameters:

- `ok` (boolean)

### `cron_next_run` (~91 tokens)

Penniless Cron Next Run

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.

Input parameters:

- `after` (string): ISO timestamp to search after (default now)
- `expr` (string, required): 5-field cron expression

Output parameters:

- `ok` (boolean)

### `text_diff` (~101 tokens)

Penniless Text Diff

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.

Input parameters:

- `context` (number): Context lines per hunk (default 3)
- `new` (string, required): Changed text
- `old` (string, required): Original text

Output parameters:

- `ok` (boolean)

### `text_extract` (~105 tokens)

Penniless Text Extract

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.

Input parameters:

- `codeBlocks` (boolean): Keep pre/code blocks
- `input` (string, required): HTML or plain text
- `numbers` (boolean): Keep numeric strings in text output

Output parameters:

- `ok` (boolean)

### `domain_whois` (~87 tokens)

Penniless WHOIS Lookup

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.

Input parameters:

- `domain` (string, required): Domain name, no scheme

Output parameters:

- `ok` (boolean)

### `dns_lookup` (~95 tokens)

Penniless DNS Lookup

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.

Input parameters:

- `domain` (string, required): Hostname to resolve
- `type` (string): Record type (default A)

Output parameters:

- `ok` (boolean)

### `github_repo_stats` (~83 tokens)

Penniless GitHub Repo Stats

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.

Input parameters:

- `repo` (string, required): owner/name

Output parameters:

- `ok` (boolean)

### `email_validate` (~65 tokens)

Penniless Email Validate

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.

Input parameters:

- `email` (string, required): Email address

Output parameters:

- `ok` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/danielarif26-penniless-data-utilities/penniless-json-repair#diagnostics

## Score history

- 2026-09-20: 62
- 2026-09-19: 62
- 2026-09-18: 61
- 2026-09-17: 61

## Common questions

### 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.

## Links

- Remote endpoint: https://penniless-json-repair.sjaman.workers.dev/mcp
- Repository: https://github.com/danielarif26/penniless-data-utilities
- Website: https://penniless-json-repair.sjaman.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/danielarif26-penniless-data-utilities/penniless-json-repair.xml
- Changelog JSON feed: https://verifymcp.io/servers/danielarif26-penniless-data-utilities/penniless-json-repair.json
- HTML version of this page: https://verifymcp.io/servers/danielarif26-penniless-data-utilities/penniless-json-repair