US state MI vs US state MN
US state MI is an MCP server for developer tools. US state MN is an MCP server for developer tools.
- US state MI is best for testing an mcp client against a minimal remote server.
- US state MN is best for testing a remote mcp client connection against a minimal endpoint.
- What it is
- US state MI is an MCP server for developer tools.US state MN is an MCP server for developer tools.
- Best for
- Testing an MCP client against a minimal remote serverTesting a remote MCP client connection against a minimal endpoint
- 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 simple state-code reference for Michigan; Studying how single-purpose MCP endpoints are registeredTesting a remote MCP client connection against a minimal endpoint; Experimenting with tiny single-purpose MCP servers; Referencing the MN state code in an agent workflow
What US state MI does
Remote streamable HTTP
Connects to a hosted endpoint over streamable HTTP, with no local package to install.
Single-purpose scope
Dedicated to one value, the USPS state code MI.
Registry-listed name
Published in the MCP registry as io.github.sadri-dridi/st-mi.
Part of a utility collection
One of many small named MCP servers kept in the same repository.
What US state MN does
Streamable HTTP transport
Exposed as a remote MCP server over streamable HTTP, with no local package to install.
Single-purpose utility
Registered under the name io.github.sadri-dridi/st-mn and described as the USPS state code MN.
Part of a named collection
Lives alongside many other small MCP utilities in the same repository, each with its own registry name.
US state MI vs US state MN: questions
What is the difference between US state MI and US state MN?
US state MI is an MCP server for developer tools. US state MN is an MCP server for developer tools.