Postal Lookup MCP
REMOTE · ADS.GETLULU.DEV · SCANNED SEP 26
Free, keyless postal/ZIP code lookup: place name(s), state/region, and coordinates.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability33
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 213 tokens (~71/item across 3 items; 1 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
- Supports UI / widget rendering.Pass
How do I install the Postal Lookup MCP server?
Postal Lookup MCP is a hosted endpoint at https://ads.getlulu.dev/postal/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 · ads.getlulu.dev
claude mcp add --transport http lulu-the-narwhal-postal-lookup-mcp 'https://ads.getlulu.dev/postal/mcp'
{
"mcpServers": {
"lulu-the-narwhal-postal-lookup-mcp": {
"url": "https://ads.getlulu.dev/postal/mcp"
}
}
} {
"servers": {
"lulu-the-narwhal-postal-lookup-mcp": {
"type": "http",
"url": "https://ads.getlulu.dev/postal/mcp"
}
}
} [mcp_servers.lulu-the-narwhal-postal-lookup-mcp] url = "https://ads.getlulu.dev/postal/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lulu-the-narwhal-postal-lookup-mcp": {
"type": "remote",
"url": "https://ads.getlulu.dev/postal/mcp",
"enabled": true
}
}
} openclaw mcp add lulu-the-narwhal-postal-lookup-mcp --url 'https://ads.getlulu.dev/postal/mcp' --transport streamable-http
mcp_servers:
lulu-the-narwhal-postal-lookup-mcp:
url: "https://ads.getlulu.dev/postal/mcp" {
"McpServers": {
"lulu-the-narwhal-postal-lookup-mcp": {
"Transport": "http",
"Url": "https://ads.getlulu.dev/postal/mcp"
}
}
} assistant mcp add lulu-the-narwhal-postal-lookup-mcp -t streamable-http -u 'https://ads.getlulu.dev/postal/mcp'
{
"mcpServers": {
"lulu-the-narwhal-postal-lookup-mcp": {
"type": "http",
"url": "https://ads.getlulu.dev/postal/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −1
- Stability: pass → 0.87 functional
- 6 Sept 26 0
- Stability: 0.97 → pass security
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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 26 Sept 2026 · Probed https://ads.getlulu.dev/postal/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ads.getlulu.dev | CN=WR3,O=Google Trust Services,C=US | 5 Sept 2026 | 4 Dec 2026 | RSA 2048 | SHA256-RSA | 4a2ee78c48c29c300a67cd526bdea921 |
| SANs: ads.getlulu.dev | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ads.getlulu.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| getlulu.dev. | 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://ads.getlulu.dev/postal/mcp | Verified | 200 | |
| http (plaintext) | http://ads.getlulu.dev/postal/mcp | HTTPS enforced | 301 | https://ads.getlulu.dev:443/postal/mcp |
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 →
lookup_postal_code ~199
Resolve a postal/ZIP code to its place name(s), state/region, and coordinates. `country_code` is a 2-letter ISO code (US, GB, DE, ...); `postal_code` format varies by country (e.g. "90210" for the US, "SW1A 1AA" style outward codes for the UK). Use for "what city is ZIP 90210 in", "where is postal code X in country Y", or any question that needs a place name/region/lat-lon from a postal code -- not for the reverse (place name to postal code) or for full street address lookup. Some postal codes span multiple places, in which case all of them are returned. Returns an error dict (never raises) if the code isn't recognized for that country.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | – |
| postal_code | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Postal Lookup MCP server?
Postal Lookup MCP is listed in the public MCP registry as io.github.Lulu-The-Narwhal/postal-lookup-mcp. Free, keyless postal/ZIP code lookup: place name(s), state/region, and coordinates. This page covers its hosted endpoint (https://ads.getlulu.dev/postal/mcp).
Is the Postal Lookup MCP server safe to use?
Postal Lookup MCP scores 68 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 Postal Lookup MCP server expose?
Postal Lookup MCP exposes 1 tool: lookup_postal_code. Their descriptions and schemas cost roughly 199 tokens of context every time the server is loaded.
Does the Postal Lookup MCP server require authentication?
No. We connected to Postal Lookup MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Postal Lookup MCP server still maintained?
Postal Lookup MCP is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.