_ registry / mcp + a2a streamable-http · checked 34m ago

penny-press

https://www.pennypress.org

Registry code: 6c869a3a1727a531

api record

Short essays and fragments. Free for humans; machines pay pennies per read via x402.

from a public catalogue that lists it, not from the operator

endpoint
https://www.pennypress.org/mcp also at https://pennypress.org/mcp
door code
f377ab9340af0129
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is penny-press live?
Yes — it answered the hub's last check (checked 34m ago). It answered 100% of checks over the last 30 days.
Is penny-press free to use?
Yes — the hub reached it with no key and no payment.
What tools does penny-press have?
7 tools: essay_payment_info, lexicon_lookup, common_cents_info, lexicon_snapshot_info, witness_verify, witness_attest_info, list_essays.
Is penny-press safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.7%

90 days 99.4%· all time 99.7%

latency
507ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1326 checks · signed record
  • degraded → live
  • live → degraded· endpoint unreachable (timeout after 20000ms); card still served
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • list published essays
  • get payment details for an essay
takes → gives
text → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 1 other origin: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
16

distinct

settlements
51

last 2026-11-08

received on chain
1.64 USDC

concentrated, shared-payto

_ what it can do 7 tools
6 open 1 never probed 6 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • lexicon_lookup open 10h ago

    Look up a term in the Penny Press Lexicon (the author's own definitions of his political-economy vocabulary). Returns free metadata — part of speech and the essays where the term appears — plus payment info for the $0.01 full definition.

    mcp-tool

    {
      "type": "object",
      "required": [
        "term"
      ],
      "properties": {
        "term": {
          "type": "string",
          "description": "The term or its slug, e.g. 'fiat-order'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • common_cents_info open 15h ago

    Overview of Common Cents, the Penny Press collection of 20 author-curated quotations in five themed clusters: the themes, quote count, and payment info for the $0.01 full machine-readable set.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • lexicon_snapshot_info open 15h ago

    Payment details for the Penny Press Lexicon full dataset snapshot ($0.25): every author-defined term with part of speech, definition, verbatim usage example, and source essays, as versioned JSON.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • witness_verify open 10h ago

    Check whether a SHA-256 content hash has been witnessed by LitWit, the Penny Press literary notary. Free. Returns the matching attestation entries (entry id, sequence, timestamp, title) or an empty result.

    mcp-tool

    {
      "type": "object",
      "required": [
        "content_hash"
      ],
      "properties": {
        "content_hash": {
          "type": "string",
          "description": "Hex SHA-256 fingerprint of the work"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • witness_attest_info open 15h ago

    How to attest a work's fingerprint with LitWit ($0.05): what to submit, what the tamper-evident receipt contains, and the x402 payment details. The service never sees your work — only its hash.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_essays reads open 34m ago

    List all published essays and fragments: titles, descriptions, prices, and reading URLs. Full text is free for humans at /read/{slug}; machine reads at /essays/{slug} are paid via x402 (USDC on Base).

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • essay_payment_info reads unknown never probed

    Get the x402 payment details for one essay (price, network, asset, recipient wallet) so a machine buyer knows how to pay.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Essay slug, e.g. river-of-time"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6c869a3a1727a531.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6c869a3a1727a531/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6c869a3a1727a531/badge.svg)](https://brick.blue/agent/6c869a3a1727a531?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.