Skip to content

postalref MCP server

com.postalref/postalrefpostalref.comstreamable-httpv0.3.0Scanned

USPS package barcodes, service type codes and mailing terms, each cited to its USPS source.

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 5
  • Reads text others write · 1
  • Can send data out · 1
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the postalref MCP server can do

The postalref MCP server is published by postalref.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: lookup and diff), but cannot delete data. 4 tools only read.

5 tools read private data (decode, lookup, diff and 2 more); 1 tool brings in text other people can write (decode); 1 tool can send data out of your system (diff). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 0.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • 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 i…Reads private dataCan send data out1 finding

    Why it is in this group

    • The name "diff" says "diff": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe description's first sentence says "table": it reads databases.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "diff" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "diff" says "diff": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Compare two editions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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 i…Reads private data1 finding

    Why it is in this group

    • The name "lookup" says "lookup": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe input names a table (input.table), and the tool reads: it reads databases.

    Findings

    • Warn

      The server marks "lookup" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "lookup" says "lookup": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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. 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.

    Annotations the server declares

    • title: Look up a code
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • 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, wheth…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "mail": it reads mail.
    • untrusted-inputThe description's first sentence says "read" and "mail": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Read 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.

    Annotations the server declares

    • title: Decode a barcode
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • grepSearch 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 a…Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "document": it reads documents.
    Description, as the server wrote it
    Search 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: grep again with /documents/<id> as `path` 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 path and page read 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. With /documents as `path`, it searches every document on PostalPro by title and file name instead, 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 path read takes. 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 read its `path` at that `page` for the sentences around it. When no hit answers, grep again with the words an answer would say. A title says only that USPS publishes a document: read one grep lists to learn what it says.

    Annotations the server declares

    • title: Search the documents
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • readRead a page of postalref.com by its path.No findings

    Why it is in this group

    • The name "read" says "read": a word for reading.
    Description, as the server wrote it
    Read a page of postalref.com by its path. /glossary/<id> gives what USPS means by a term: its entry, 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 when USPS ended or renamed it, each with USPS's words; /glossary/<words>, such as /glossary/mailer-id or /glossary/MID, gives the entries those words name, in the order search ranks them. /codes/<table>/<code>, such as /codes/service-type-codes/055, gives a code's row as USPS prints it in the newest edition that lists it, the editions that list it and its history. /documents/<id> gives any document postalref holds, page by page as extracted, to quote, and /documents lists them. Any other path is a page of the site, given as its Markdown: a product page (/products/<id>), a guide (/guides/<id>), a code table's home (/codes/<table>), a case (/cases/<id>), a spec (/specs/<id>), a topic (/topics/<id>) or /changes. Quote whole sentences, word for word. A definition's words cite its document and page, and its `read` names the document and page to read for the sentences around them. A document's `text`, or a `found` context, which shows the whole sentence around the words or the lead-in with the list it opens, cites the revision's sha256, the PDF page and the words exactly; 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`. A text without pages, a web page or a product page, reads in parts, and a quote from one cites no page.

    Annotations the server declares

    • title: Read a page of postalref.com
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

5 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__postalref__diff"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:21 UTC, unchanged since Oct 31, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://postalref.com/mcp: tools/list returned 8 tools to an anonymous client, including lookup (write), diff (write), define (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • Warnlookup

    The server marks "lookup" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "lookup" says "lookup": a word for reading.

    What this check looks for
  • Warndiff

    The server marks "diff" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "diff" says "diff": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 4 removed, 3 changed.+2 added−4 removed~3 changedView diff
    • Added:grepOnly reads
    • Added:readOnly reads
    • Removed:define
    • Removed:read_source
    • Removed:search_documents
    • Removed:search_text
    • Changed:decodeOnly readsdescriptioninputSchema
    • Changed:lookupChanges thingsdescriptioninputSchema
    • Changed:searchOnly readsdescription
  2. Tools1 added, 6 changed.+1 added~6 changedView diff
    • Added:search_textOnly reads
    • Changed:decodeOnly readsdescriptioninputSchema
    • Changed:defineChanges thingsdescription
    • Changed:lookupChanges thingsdescriptioninputSchema
    • Changed:read_sourceOnly readsdescriptioninputSchema
    • Changed:searchOnly readsdescription
    • Changed:search_documentsOnly readsdescription
  3. Tools3 changed.~3 changedView diff
    • Changed:defineChanges thingsdescription
    • Changed:lookupChanges thingsdescription
    • Changed:searchOnly readsdescription

Install

Pinned to version 0.3.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http postalref https://postalref.com/mcp
claude mcp add --transport http postalref https://postalref.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__postalref__decode",
      "mcp__postalref__search",
      "mcp__postalref__read",
      "mcp__postalref__grep"
    ],
    "ask": [
      "mcp__postalref__lookup",
      "mcp__postalref__diff"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as postalref. Review it before you use it.

Capability tags behind 5 rules
  • mcp__postalref__decode private-data, untrusted-input
  • mcp__postalref__lookup private-data
  • mcp__postalref__diff private-data, outbound
  • mcp__postalref__search private-data
  • mcp__postalref__grep private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.postalref/postalref/verify?hash=ea3bb1ace34c10dc9614e1b915f8d36457801bf36feb2f76c85095066c8e21d0" | jq -e '.changed == false'

Pinned hash ea3bb1ace34c, from Nov 19, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.postalref/postalref/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.postalref/postalref
[![Anlyon Radar](https://radar.anlyon.com/badge/com.postalref/postalref.svg)](https://radar.anlyon.com/servers/com.postalref/postalref)

Source: MCP Registry. Synced Nov 19, 2026, 20:17 UTC.

postalref MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the postalref MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the postalref MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the postalref MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the postalref MCP server have?

6 tools: 2 write, 4 read. lookup, diff, decode, search, read and grep.

Does the postalref MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the postalref MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): diff.

Has the postalref MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.