_ registry / mcp http-sse · checked 50m ago

princeofpost

https://princeofpost.com

Registry code: f93367b1dd9b6eb5

api record

Prince of Post turns a Royal Mail QR code (the kind shown at a Post Office counter) into a printable 6x4 label. Use create_royal_mail_label. When the user has a screenshot, photo or PDF of the QR code, call it with no arguments: a panel lets them pick the file, which is read on their device. Never transcribe a QR code from an image. Pass qr_text only when you have the exact text a QR decoder returned.

endpoint
https://princeofpost.com/mcp
protocol
http-sse ·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 princeofpost live?
Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.
Is princeofpost free to use?
Not measured yet.
What tools does princeofpost have?
1 tool: create_royal_mail_label.
Is princeofpost 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
393ms

last good check

priced tools
0

of 1 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

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

  • create_royal_mail_label unknown never probed

    Turns a Royal Mail QR code (the kind you show at a Post Office: Vinted digital labels, eBay Royal Mail QR codes, ASOS returns and other Royal Mail "Labels to Go" QR codes) into a 6x4 shipping label the user can print at home instead of queuing. If the user has an image or PDF of the QR code, call this with no arguments: a panel lets them pick the file, which is read on their device. Only pass qr_text if you already have the exact decoded text from a QR decoder. Never transcribe a QR code from an image.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "qr_text": {
      "type": "string",
      "maxLength": 4000,
      "description": "The exact text a QR decoder returned for the QR code, unchanged, including every space. It is fields like QRCode=..., 1DBarcode=... and SendersDetails=... separated by |. Omit this if you only have an image of the QR code."
    }
  }
}
    arguments 11 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 f93367b1dd9b6eb5.

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

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.