Release status
Release notes
Windows ZIP and Linux tarball artifact smoke tested.
MCP Boundary v0.2.3
Both packaged archives were unpacked and smoke-tested. This release includes the simulated local email demo, public docs, license notes, terms, and third-party notices.
Windows · Windows .zip
mcpboundary-v0.2.3-windows-amd64.zip
Windows ZIP artifact smoke passed.
sha256:b1df85bf093366c4299169be348e5386d536b72c96f3386c254b0a15fce3e83cLinux · Linux .tar.gz
mcpboundary-v0.2.3-linux-amd64.tar.gz
Linux tarball artifact smoke passed.
sha256:0f2f8551f3fc501820d628f0bf503a0bfde01356425fc580278d3ca9e4c19f0cGetting started
From an extracted Windows ZIP folder, run .\mcpboundary.exe quickstart email. From an extracted Linux tarball, run ./mcpboundary quickstart email. If the binary is on PATH, use mcpboundary quickstart email.
Release scope
The included Local Email Demo is simulated: no provider account, no provider credentials, no OAuth, no real inbox, and no real email send.
Both v0.2.3 archives were unpacked and smoke-tested. That is not a claim that every operating system, distribution, shell, package manager, or MCP client has been tested.
Private use and evaluation are free of charge. Commercial production use by companies requires a paid license from Impact Boundary Labs.
MCP Boundary works best with local command-based stdio MCP servers and selected controlled loopback profiles. Only calls routed through MCP Boundary are covered.
Download links count aggregate download events. The local MCP Boundary tool does not send local tool lists, policy files, activity logs, or downstream results back to Impact Boundary Labs.