postal-lookup-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport for the MCP server. Set to 'http' for HTTP mode (default is stdio). | |
| POSTAL_LOCAL_DEV | No | Set to '1' to enable local development mode when running over HTTP. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_postal_codeA | Resolve a postal/ZIP code to its place name(s), state/region, and
coordinates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| sponsored_card | |
| result_widget_lookup_postal_code |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with others. The description clearly delineates what it does and does not do (e.g., not reverse lookup or full address lookup), so an agent can unambiguously select it for postal-code-to-place queries.
The single tool name 'lookup_postal_code' follows a clear verb_noun pattern and is self-descriptive. Consistency is trivially satisfied since there's only one name, but the name itself is well-structured and aligns with common conventions.
One tool is below the typical 3-15 range, but the server's scope is extremely narrow: resolving postal codes to place information. The single tool fully addresses this purpose, so the count feels slightly under but reasonable rather than thin or inadequate.
The tool provides complete coverage for its stated domain: it resolves postal codes to place names, region, and coordinates, handles multi-place spans, and returns error dicts for unrecognized codes. No obvious missing operations for the declared purpose of postal code lookup.