postalref
REMOTE · POSTALREF.COM
USPS package barcodes, service type codes and mailing terms, each cited to its USPS source.
Available components
Last scanned (9 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, 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 Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1498 tokens (~187/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 5 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “read_source” rewrote its description, which is the text the model reads security
- Tool “search_documents” rewrote its description, which is the text the model reads security
- Schema quality: 157 → 187 ▼ functional
- New tool “search_text” functional
- “lookup” reworded the description of “table” cosmetic
- “read_source” reworded the description of “document” cosmetic
- “read_source” reworded the description of “page” cosmetic
- 3 Nov 26 0
- Tool “define” rewrote its description, which is the text the model reads security
- 2 Nov 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.
- 1 Nov 26 0
- Tool “define” rewrote its description, which is the text the model reads security
- Tool “lookup” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Schema quality: 127 → 153 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 0.2.0 functional
- 31 Oct 26 65
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 5 Nov 2026 · Probed https://postalref.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=postalref.com | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 51a174dfae63103313afabd8bd3466a0 |
| SANs: postalref.com, www.postalref.com, *.www.postalref.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of postalref.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| postalref.com. | 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://postalref.com/mcp | Verified | 400 | |
| http (plaintext) | http://postalref.com/mcp | Inconclusive | 405 |
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 →
decode Decode a barcode ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| barcode | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| digits | string | yes | – |
| fields | array | yes | – |
| format | object | yes | – |
| spec | object | yes | – |
| tracking | string | yes | – |
| verdict | string | yes | – |
No examples provided.
define Define a USPS term ~143
What 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | At most this many entries; 5 when absent. |
| name | string | yes | A name or abbreviation USPS uses: mailer id, MID, CRID, banner text. |
| Name | Type | Req | Description |
|---|---|---|---|
| entries | array | yes | – |
| match | string | – | – |
| query | string | yes | – |
| total | integer | yes | – |
No examples provided.
diff Compare two editions ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | One code of the table. |
| from | string | – | The older edition's date. The edition before `to` when absent. |
| limit | integer | – | At most this many changes; 50 when absent. |
| severity | string | – | Only changes rated this. |
| subject | string | yes | A code table, such as stc, ptr or extra-services, or a document, such as pub-199 or impb-spec. |
| to | string | – | The newer edition's date. The newest when absent. |
| Name | Type | Req | Description |
|---|---|---|---|
| changes | array | yes | – |
| counts | object | yes | – |
| editions | array | yes | – |
| from | string | – | – |
| subject | object | yes | – |
| to | string | yes | – |
| total | integer | yes | – |
No examples provided.
lookup Look up a code ~278
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. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | A code as USPS prints it: 055, 920, PM, 01. |
| table | string | – | One table to look in: stc, extra-services, mail-classes, channel-application-ids, container-types, delivery-option-indicators, rate-indicators, destination-rate-indicators, discount-types, open-and-d… |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | yes | – |
No examples provided.
read_source Read a USPS document ~277
Read 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.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | A document's id, as search_documents gives it: a modeled one, such as pub-199 or impb-spec; node-4649 for another PostalPro file; postalpro-855 for a PostalPro product page; or a download such as pdf… |
| find | string | – | 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 | integer | – | The first PDF page, sheet or part to read, counting from 1. Absent with `find`: the pages that have the words. |
| pages | integer | – | How many to read, up to 5; 1 when absent. |
| revision | string | – | A revision's sha256, or its slug, such as 2026-07-02. The newest when absent. |
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | yes | – |
| found | array | – | – |
| match | string | – | – |
| next | integer | – | – |
| parts | integer | yes | – |
| revision | – | yes | – |
| revisions | array | yes | – |
| text | array | yes | – |
No examples provided.
search Search codes and terms ~184
Search 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 comes back as one to decode.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | At most this many hits; 10 when absent. |
| query | string | yes | A code, a term or words from a code's row: 055, mailer id, ground advantage. |
| Name | Type | Req | Description |
|---|---|---|---|
| decode | string | – | – |
| hits | array | yes | – |
| query | string | yes | – |
| total | integer | yes | – |
No examples provided.
search_documents Search PostalPro documents ~103
Search 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 the id read_source reads it by.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | At most this many; 10 when absent. |
| query | string | yes | Words from a document's title or file name. |
| topic | string | – | Only documents a model put under this topic. |
| Name | Type | Req | Description |
|---|---|---|---|
| documents | array | yes | – |
| query | string | yes | – |
| total | integer | yes | – |
No examples provided.
search_text Search the text of documents ~200
Search the text of every document postalref holds 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, and at most three pages a document. A page needn't have the words a question asks with, such as how, get or take. Each hit gives the id and page read_source reads, and the words around them. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | At most this many pages; 10 when absent. |
| query | string | yes | Words a page says: a price, a rule, a size, a name. Each word is found in its forms: one or many, -ed, -ing, -able. |
| Name | Type | Req | Description |
|---|---|---|---|
| hits | array | yes | – |
| match | string | yes | – |
| query | string | yes | – |
| total | integer | yes | – |
No examples provided.
How do I install the postalref MCP server?
postalref is a hosted endpoint at https://postalref.com/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 · postalref.com
claude mcp add --transport http com-postalref-postalref 'https://postalref.com/mcp'
What is the postalref MCP server?
postalref is an MCP server listed in the public MCP registry as com.postalref/postalref. USPS package barcodes, service type codes and mailing terms, each cited to its USPS source. This page covers its hosted endpoint (https://postalref.com/mcp).
Is the postalref MCP server safe to use?
postalref scores 66 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 postalref MCP server expose?
postalref exposes 8 tools: decode, lookup, diff, search, define, and 3 more. Their descriptions and schemas cost roughly 1,401 tokens of context every time the server is loaded.
Does the postalref MCP server require authentication?
No. We connected to postalref without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the postalref MCP server still maintained?
postalref is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.