postalref
com.postalref/postalrefVersion 0.2.1USPS package barcodes, service type codes and mailing terms, each cited to its USPS source.
Status
Responds408 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:10 UTC
- Latency
- 408 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://postalref.com/mcpResponds408 msNo sign-in
Claude Code
claude mcp add --transport http postalref https://postalref.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: postalref
Remote MCP server URL: https://postalref.com/mcpCursor
{
"mcpServers": {
"postalref": {
"url": "https://postalref.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"postalref","type":"http","url":"https://postalref.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
8 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
decodeRead a package barcode or tracking number (IMpb), or a letter's or flat's Intelligent Mail barcode (IMb) from its digits or bars: its layout, each field's digits and meaning, whether the check digit or the bars' frame check holds, and the service type code's or Service Type ID's row in the USPS list, each with the passage that says so. A field's `meaning` is postalref's words: quote a cite's `lit`, USPS's, with its passage. | No | Yes | Yes | No |
defineWhat USPS means by a name or abbreviation: each registry entry it names, in the order search ranks them, with its kind and tier, 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. An entry USPS ended says when, what replaced it, and USPS's words that say so; one renamed gives its former names, each with USPS's words. Quote a definition's words as they are, citing its document and page; its `read` names the document and page read_source reads them on, with the sentences around them. | No | Yes | Yes | No |
diffWhat 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. | No | Yes | Yes | No |
lookupLook 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. A code is found without the marks USPS prints around it and in a row USPS prints for several codes: 750 finds *750, 858 finds 858 and the dropped 858**, and 13 finds PTR's row 01 / 13. Two digits are also tried as three: 55 finds PTR's 55, then STC's 055. Cite a row by its passage, revision and page, with its cells' words as printed, and a row's `notes`, the footnotes its marks point to, by their own revision and page. | No | Yes | Yes | No |
read_sourceRead any document postalref holds page by page, as extracted, to quote it: a quote cites the revision's sha256, the PDF page and the words exactly. A text without pages, a web page or a product page, reads in parts, and a quote from one cites no page. Quote whole sentences, word for word, from a page's `text` or a `found` context, which shows the whole sentence around the words, or the lead-in with the list it opens. Read another page `found` lists by its `pdf` number, or a part by its number, as `page`. When the text ends mid-sentence or mid-list, `continued` gives the rest of it from `next`, cited by its own page; when it ends mid-table, or a list goes on past `continued`, read `next`. | No | Yes | Yes | No |
searchSearch the codes, terms, banner texts, specs and documents postalref models, by one index: names and codes whose key is the query's first, then those that start with it, then those with words that start with its words, then codes whose row has its words. A term hit carries its kind (mail-class, extra-service, service, program, system, file, identifier, document, facility, container, role or term) and its tier (core, or reference: only in Publication 32, the glossary of July 2013, with that date). A query of 20 or more digits, or an Intelligent Mail barcode's 65 bars as A, D, F and T, comes back as one to decode. A term hit's slug goes to define, and a code's to lookup with its table. | No | Yes | Yes | No |
search_documentsSearch every document on PostalPro by title and file name, with its page and newest file, and the product pages and downloads postalref holds by title. Each one postalref holds the text of carries an `id`, which read_source takes as `document`. A title says only that USPS publishes a document: read one it lists with read_source to learn what it says. | No | Yes | Yes | No |
search_textSearch the text of every document postalref holds, or of one, for the pages that say the words, best first: those that say them as a phrase, then by how much of the page they are and how many of them it says side by side or close together, a table of contents last. A court's filing or a Justice Department release about a fraud case comes after USPS's own pages when one of those says every word, as Publication 52 and a release about a bulk mail fraud both say bulk mail permit; a case's name finds its records first. A document gives at most three pages while other documents' pages fill the list, and `more` gives each document a hit is from that has more pages with the words, and how many: search again with its id as `document` to rank only its pages. A page needn't have the words a question asks with, such as how, get or take. Each word is found in its forms, and a name also as the registry's other names for it, BCG for Business Customer Gateway or Post Office Box for PO Box, and a size as 4x6 or 4 x 6; a hit another wording found gives it as `by`. Each hit gives the id and page read_source reads, and the passage that says most of the words. Use it when no title names what you're looking for, as for a price in the Mail Classification Schedule or a rule in a DMM chapter. A hit's `context` is a whole sentence, list or row of the page unless it starts or ends with …: quote it with the hit's `id` and `page`, or give them to read_source as `document` and `page` for the sentences around it. When no hit answers, search again with the words an answer would say. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Nov 8, 2026
- Updated
- Nov 8, 2026
- Repository
- Not given
- Categories (suggested)
- DocumentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared