US state SD vs US state UT
US state SD is an MCP server for agent tooling. US state UT is an open-source MCP server for agent tooling.
- US state SD is best for testing an mcp client's connection to a minimal remote server.
- US state UT is best for testing connections to a remote mcp endpoint from an agent client.
- What it is
- US state SD is an MCP server for agent tooling.US state UT is an open-source MCP server for agent tooling.
- Best for
- Testing an MCP client's connection to a minimal remote serverTesting connections to a remote MCP endpoint from an agent client
- Kind
- MCP serverMCP server
- Pricing
- Open source
- Platforms
- APIAPI
- Runs
- RemotelyRemotely
- Open source
- Good for
- Testing 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 publishedTesting connections to a remote MCP endpoint from an agent client; Exploring small single-purpose MCP servers registered by one publisher; Studying how agents discover and call minimal registry entries
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.
What US state UT does
Streamable HTTP transport
Connects to MCP clients as a remote server over streamable HTTP, with no local install.
Registry-listed name
Published in the official MCP registry as io.github.sadri-dridi/st-ut.
Part of a utility collection
One of many small named MCP endpoints maintained in the same repository.
US state SD vs US state UT: questions
What is the difference between US state SD and US state UT?
US state SD is an MCP server for agent tooling. US state UT is an open-source MCP server for agent tooling.