One URL for any agent runtime: the hosted Hashlock MCP endpoint

When the Model Context Protocol spec landed, the canonical transport was stdio: an agent spawns the MCP server as a child process and talks to it over standard input and output. That choice was reasonable. Stdio is fast, has no network surface, and on a developer's laptop it's the path of least resistance.

It is also a poor fit for almost every production deployment of an agent.

Hashlock Markets ships the same six MCP tools over both transports. The npm package, hashlock-tech/mcp (scoped on npmjs), is the stdio path. The other path is a hosted endpoint at https://hashlock.markets/mcp , served as Streamable HTTP MCP.…