USPS Address Validation and Standardization MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USPS_CLIENT_ID | Yes | Your USPS Consumer Key (client ID) | |
| USPS_CLIENT_SECRET | Yes | Your USPS Consumer Secret (client secret) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_addressA | Validate and standardize a US address using USPS Address Validation API. Returns corrected address information, delivery point validation, and address standardization. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is unambiguous and clearly defined.
The single tool name 'validate_address' follows a clear verb_noun pattern, which is consistent with best practices. There are no other tools to compare, but the naming is clean and predictable.
The server is narrowly scoped to USPS address validation and standardization. One tool adequately covers this specific function without unnecessary bloat, making the count perfectly appropriate for the purpose.
The tool fully addresses the domain of individual address validation by providing validation, standardization, and delivery point information. There are no obvious gaps for the stated purpose of the server.