US state NM vs US state SD
US state NM is an MCP server for agent tooling. US state SD is an MCP server for agent tooling.
- US state NM is best for testing an mcp client against a minimal remote server.
- US state SD is best for testing an mcp client's connection to a minimal remote server.
- What it is
- US state NM is an MCP server for agent tooling.US state SD is an MCP server for agent tooling.
- Best for
- Testing an MCP client against a minimal remote serverTesting an MCP client's connection to a minimal remote server
- Kind
- MCP serverMCP server
- Platforms
- APIAPI
- Runs
- RemotelyRemotely
- Open source
- Good for
- Testing an MCP client against a minimal remote server; Giving an agent a lookup endpoint tied to the New Mexico state code; Exploring how single-purpose utility servers are registered and hostedTesting an MCP client's connection to a minimal remote server; Looking up the USPS state code SD from an agent workflow; Studying how single-purpose named MCP endpoints are published
What US state NM does
Remote streamable HTTP
Runs as a hosted endpoint reachable over streamable HTTP, with no local package to install.
Registry-listed name
Published in the official MCP registry as io.github.sadri-dridi/st-nm.
Single-purpose scope
Scoped to one narrow topic, the USPS state code NM, like the other servers in its repository.
Built for autonomous clients
Intended for agents and MCP clients to discover and call directly.
What US state SD does
Remote streamable HTTP
Connects to a hosted endpoint over streamable HTTP, so nothing needs to be installed locally.
Single-purpose scope
Registered under the name io.github.sadri-dridi/st-sd and described as the USPS state code SD.
Registry-listed name
Published under an official MCP registry name, which makes it discoverable by compatible clients.
US state NM vs US state SD: questions
What is the difference between US state NM and US state SD?
US state NM is an MCP server for agent tooling. US state SD is an MCP server for agent tooling.