_ registry / mcp streamable-http · checked 1h ago

postalref

https://postalref.com

Registry code: 59955d05426699f7

api record

postalref answers from USPS's PostalPro documents, each answer with the passage that says it. decode reads a package barcode or tracking number; lookup gives a code's row and history; diff says what changed between editions; search finds codes, terms and specs; search_documents finds any PostalPro document; read_source reads a modeled document's text to quote.

endpoint
https://postalref.com/mcp
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 postalref live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is postalref free to use?
Yes — the hub reached it with no key and no payment.
What tools does postalref have?
7 tools: lookup, search, read_source, search_documents, decode, define, diff.
Is postalref 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
100%

90 days 100%· all time 100%

latency
1,501ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 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.

  • lookup unknown never probed

    Look up a USPS code: its row as USPS prints it in the newest edition that lists it, the codes its cells name, the editions that list it and its history, each row with its passage id.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "maxLength": 40,
      "description": "A code as USPS prints it: 055, 920, PM, 01."
    },
    "table": {
      "type": "string",
      "description": "One table to look in: stc, extra-services, mail-classes, ptr, ptr2 or stid. Every table when absent."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • search unknown never probed

    Search the codes, terms, specs and documents postalref models, exact names and codes first. A query of 20 or more digits comes back as one to decode.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "At most this many hits; 10 when absent."
    },
    "query": {
      "type": "string",
      "maxLength": 120,
      "description": "A code, a term or words from a code's row: 055, mailer id, ground advantage."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • read_source unknown never probed

    Read a revision of a modeled USPS document page by page, as extracted, to quote it: a quote cites the revision's sha256, the PDF page and the words exactly.

    mcp-tool

    {
  "type": "object",
  "required": [
    "document"
  ],
  "properties": {
    "find": {
      "type": "string",
      "maxLength": 200,
      "description": "Words to find, as one phrase, or when no page has the phrase, each word anywhere on a page. Without `page`, the text read is the first pages that have them."
    },
    "page": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 1,
      "description": "The first PDF page, or sheet, to read, counting from 1. Absent with `find`: the pages that have the words."
    },
    "pages": {
      "type": "integer",
      "maximum": 5,
      "minimum": 1,
      "description": "How many to read, up to 5; 1 when absent."
    },
    "document": {
      "type": "string",
      "description": "A modeled document: pub-199, impb-spec, stc-list, ptr-events, ptr2-events, stid-table, imb-spec or parcel-labeling-guide."
    },
    "revision": {
      "type": "string",
      "maxLength": 64,
      "description": "A revision's sha256, or its slug, such as 2026-07-02. The newest when absent."
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • search_documents unknown never probed

    Search every document on PostalPro by title and file name, with its page and newest file. postalref models a few of them; those carry a slug for read_source.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "At most this many; 10 when absent."
    },
    "query": {
      "type": "string",
      "maxLength": 120,
      "description": "Words from a document's title or file name."
    },
    "topic": {
      "enum": [
        "mailing",
        "shipping",
        "address-quality",
        "visibility",
        "promotions",
        "operations",
        "accounts",
        "industry",
        "international",
        "other"
      ],
      "type": "string",
      "description": "Only documents a model put under this topic."
    }
  },
  "additionalProperties": false
}
    arguments 36 lines
  • decode unknown 1h ago

    Read a package barcode or tracking number (IMpb): its layout, each field's digits and meaning, whether the check digit holds, and the service type code's row in the USPS list, each with the passage that says so.

    mcp-tool

    {
  "type": "object",
  "required": [
    "barcode"
  ],
  "properties": {
    "barcode": {
      "type": "string",
      "maxLength": 80
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • define unknown 1h ago

    What USPS means by a name or abbreviation: each registry entry it names, with the USPS words that define it and the page they're on, its other names, postalref's own explanation where it has one, and postalref's page about it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 120,
      "description": "A name or abbreviation USPS uses: mailer id, MID, CRID, banner text."
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "At most this many entries; 5 when absent."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • diff unknown 1h ago

    What changed in a code table or document between two editions: each code added, removed or changed and each changed section, rated editorial, additive or breaking, with who rated it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "subject"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "The newer edition's date. The newest when absent."
    },
    "code": {
      "type": "string",
      "maxLength": 40,
      "description": "One code of the table."
    },
    "from": {
      "type": "string",
      "description": "The older edition's date. The edition before `to` when absent."
    },
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "At most this many changes; 50 when absent."
    },
    "subject": {
      "type": "string",
      "description": "A code table, such as stc, ptr or extra-services, or a document, such as pub-199 or impb-spec."
    },
    "severity": {
      "enum": [
        "editorial",
        "additive",
        "breaking"
      ],
      "type": "string",
      "description": "Only changes rated this."
    }
  },
  "additionalProperties": false
}
    arguments 41 lines
_ try it 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 59955d05426699f7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/59955d05426699f7/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/59955d05426699f7/badge.svg)](https://brick.blue/agent/59955d05426699f7?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 know
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.