Port 143 vs Port 25
Port 143 is an MCP server for developer tools. Port 25 is an MCP server for developer tools.
- Port 143 is best for checking whether a port number is a well-known service port.
- Port 25 is best for testing an mcp client's connection to a remote streamable-http server.
- What it is
- Port 143 is an MCP server for developer tools.Port 25 is an MCP server for developer tools.
- Best for
- Checking whether a port number is a well-known service portTesting an MCP client's connection to a remote streamable-HTTP server
- Kind
- MCP serverMCP server
- Platforms
- APIAPI
- Runs
- RemotelyRemotely
- Open source
- Good for
- Checking whether a port number is a well-known service port; Adding a simple port lookup step to an agent workflow; Testing an MCP client's connection to a remote streamable-http serverTesting an MCP client's connection to a remote streamable-HTTP server; Adding a simple port-classification step to an agent workflow; Demonstrating how small single-purpose MCP utilities are structured
What Port 143 does
Single-question port check
Answers whether a given port number is a common TCP or UDP port.
Hosted streamable-http endpoint
Served from a remote URL, so no local install is needed to connect.
Registry-listed server
Published under the official MCP registry name io.github.sadri-dridi/port-143.
What Port 25 does
Common port check
Reports whether port 25 is a commonly used TCP or UDP port.
Remote streamable HTTP access
Served as a remote endpoint over streamable HTTP, with no local package to install.
Single-purpose tool
Covers one narrow lookup rather than a broad networking toolkit.
Port 143 vs Port 25: questions
What is the difference between Port 143 and Port 25?
Port 143 is an MCP server for developer tools. Port 25 is an MCP server for developer tools.