Repository navigation
Releases
ArborMCP 2.0.0-rc.7
ArborMCP 2.0.0-rc.7 is a release candidate for downstream integration testing, requiring ArborRPC ~> 1.0.0-rc.4.
- Add request forwarding, manual MRTR controls, progress delivery and caller-exit cancellation.
- Make configured authentication providers own Authorization; retain structured startup errors and validate runtime options.
- Correct HTTP request retirement and tool-list cache ordering; preserve caller tool
_metaarguments across transports. - Tighten host/schema/JWT validation and pre-registered OAuth credential binding. Direct JWT claim validation now requires expected
:aud. - Require patched Bandit
~> 1.14 and >= 1.14.1; owned Bandit listeners require exact Bandit 1.14.1 with Thousand Island 1.6.0. Update explicit 1.14.0 pins.
Review the rc.6 migration notes and changelog for breaking behavior changes, runtime restart guidance and exact contracts. Stable promotion remains gated on the unfinished continuous 48-hour qualification and performance acceptance. This release does not claim those gates are complete.
All 27 supported/latest BEAM, coverage, stress, audit, conformance/interoperability and archive-consumer CI jobs pass on the reviewed source. Final Grok and Codex reviews are clean. Tagged source archives match the tested payload, with local physical Bandit and four-package installed/compiler-free release checks.
v1.8.1
ExMCP 1.8.1 is the 1.x maintenance release of the ex_mcp package (ExMCP.* / :ex_mcp), with the completed backports from tracker #113 and PR #200.
- Adds asynchronous ACP handler work and bounded session-update drop notices.
- Keeps circuit-breaker stdio reads with their port owner and bounds discovery even when notifications arrive first.
- Handles provider-token failures, pre-connect stream failures, modern HTTP protocol errors and HTTP/2 SSE response headers consistently.
- Recovers expired legacy HTTP sessions without replaying operations or letting delayed old-session failures retire a replacement.
- Retains the configurable 30-second HTTP cap and existing 1.x error envelopes; the upgrade notes explain longer operations and the new nested error reasons.
{:ex_mcp, "~> 1.8"}See the 1.8 upgrade notes, changelog, and versioned documentation. Elixir 1.17 / OTP 27 remain the minimum. Installed and compiler-free release probes cover all four MCP modes, ACP streaming/async work, package boundaries and confirmed stdio cleanup.
The earlier v1.8.0 tag is an unpublished preparation preserved for provenance; its changes are included here. Stable 1.7.3 remains available. Arbor 2.x packages continue on their separate release-candidate track.
ArborMCP 2.0.0-rc.6
ArborMCP 2.0.0-rc.6 replaces 2.0.0-rc.5. It requires ArborRPC ~> 1.0.0-rc.3 and, for owned or host-managed Bandit listeners, Bandit ~> 1.14. ArborACP and its adapters are at 1.0.0-rc.4.
Security
- A client's
logging/setLevelchanged the host application's global Logger level, so any connected client could silence or flood the host's logs. The level now applies only to that client's connection (not yet over legacy Streamable HTTP). An advisory follows on this repository's Security tab. - Bandit
~> 1.14is required for the eleven HTTP/1, HTTP/2 and WebSocket advisories fixed in 1.14.0. Owned listeners qualify exact Bandit1.14.0with Thousand Island1.6.0. - OAuth token and introspection errors no longer return a non-JSON response body, which may echo the request. Their logs leave out server error descriptions and exception messages.
Breaking changes (each is explained under "Upgrading from 2.0.0-rc.5" in the RC notes):
- Servers handle the requests on a connection concurrently, as the other MCP SDKs do. Callbacks other than
init/1andhandle_initialize/2must return the handler state unchanged, or the server must run withexecution: :stateful. - A connection's responses can arrive in completion order.
- The server's
request_timeout_msdefaults to one hour. - A DSL tool called with invalid arguments returns an
isErrortool result. - Resource-template variables are percent-decoded.
- Elicitations in
input_requiredresults are checked against the ElicitRequest schema in both eras. - Owned Bandit listeners need Bandit
1.14.0.
Added (parity with the other MCP SDKs):
- Client response caching from
ttlMs/cacheScope, and server:cache_hints. - Progress-reset request timeouts.
call_tool/4checks results against the tool'soutputSchema.- Local JWT access-token checks (
JWTVerifier,TokenVerifier). - Server middleware.
Server.Contextrequest, session and auth accessors.- Runtime
add_tool/3and its siblings. - DSL completion and options.
Also
-
The stdio transport follows the MCP shutdown order: stdin EOF,
:eof_grace, then SIGTERM. It needs ArborRPC 1.0.0-rc.3. -
Official conformance:
- 2026-07-28 server 150/150 and client 411/411 (harness
0.2.0-alpha.12); - legacy core server 39/39 and client 218/218 (
0.1.16).
All four suites now gate CI.
- 2026-07-28 server 150/150 and client 411/411 (harness
See the changelog for the full list.
Package checksum: ec491c2d7b052ace6b9f687f5214b0926367e96664bacbe1a6f73dad5d9aa9cc
v1.7.3
ExMCP 1.7.3 is a security patch on the maintained 1.x line. It keeps the ex_mcp Hex package, the :ex_mcp application and the ExMCP.* public namespaces. Use {:ex_mcp, "~> 1.7"} to get it.
Security fixes:
logging/setLevelno longer changes the host application's global Logger level. The defaulthandle_set_log_level/2calledLogger.configure/1, so any connected client could silence or flood the host's logs. It now only checks that the level is valid. A server that relied on the old behavior must callLogger.configure/1in its ownhandle_set_log_level/2. An advisory for this follows on this repository's Security tab once the package is on Hex.ExMCP.ACP.Registry.fetch/1no longer follows HTTP redirects.:httpcre-sent the caller's:headersto the redirect target, even another host or anhttp:URL; on OTP 27 and 28 that includedAuthorizationand cookies. A redirect now returns{:error, {:redirect_refused, status, location}}, with the location's userinfo, query and fragment removed (backport of trust-arbor/arbor_acp#16).
Dependencies: the lockfile pins plug_crypto 2.2.1 and cowlib 2.21.0. The lockfile isn't part of the Hex package.
See the changelog and the 1.7 maintenance notes.
Package checksum: 765193e9dea5dc063006941edfbd73435942c467c919b172e5d93cefc42032bf
v1.7.2
ExMCP 1.7.2 is a security patch on the maintained 1.x line and the first 1.7.x release published to Hex: 1.7.1 was tagged but never published, so this release also carries its argument-injection fix for the Claude and Pi ACP adapters (CVE-2026-96620 class). It keeps the ex_mcp Hex package, the :ex_mcp application and the ExMCP.* public namespaces. Use {:ex_mcp, "~> 1.7"} to get it. Security advisories for the items below are published on this repository's Security tab once the package is on Hex.
Security fixes (ACP client and bundled adapters):
ExMCP.Internal.WorkspacePath.canonical/1resolves symlinks before applying.., the way the kernel does. A path such as<root>/link/../secret, wherelinkpoints outside the workspace, previously passedwithin?/2, and with it the ACP client'sfs/read_text_file,fs/write_text_fileandterminal/createauthorization and the Codex and ZCode:workspace_rootschecks, while the file actually opened lived outside the root. ZCode now uses the shared module instead of a private copy.- A project's
.pi/settings.jsoncan no longer choose the executable the Pi adapter spawns.piCommandis honored from adapter options (:cli_path/:pi_command),PI_ACP_PI_COMMANDor the global agent settings only. Previously an untrusted repository could run an arbitrary program atsession/new. - The Pi edit-snapshot workspace root is the host-supplied session
cwd; thecwdthe agent reports inget_stateno longer replaces it, so an agent cannot widen the snapshot containment. The reportedcwdis still used for session bookkeeping. - Codex gateway
authenticaterequiresadapter_opts[:gateway_auth](matching whatauth_methods/1advertises) and an https or loopbackbaseUrl; it previously redirected model traffic and headers to any client-named URL regardless of the option.
Security fixes (MCP server and client):
- The DSL success path and the deprecated
ExMCP.Server.Toolsnormalizer no longerinspect/1arbitrary handler terms into tool results. A handler that returned a struct or tuple sent its full contents (process state, credentials) to the client; such results now produce a fixed error text and the shape is logged server-side. Binaries, atoms and exception messages still pass through. ExMCP.Clientcaps concurrent server-initiated request handlers (:max_server_requests, default 256). A server floodingsampling/createMessageorelicitation/createcould previously spawn an unbounded number of handler processes; excess requests now get an immediate JSON-RPC internal error.
Fixed:
- The ACP
AdapterBridgeno longer crashes, taking the connection down, when an adapter'stranslate_outbound/2reports a failed check as{:error, reason}without its state; ZCodesession/listwith a relative or unauthorizedcwddid exactly that. Such results now produce a JSON-RPC error reply (backport of arbor_acp#12 and #15).
The ACP fixes were made on ArborACP first (released as 1.0.0-rc.3) and then ported. The 1.7 maintenance release guide records the provenance.
CI validated the released tree (identical to the merged pull request head) on Elixir 1.17.3 / OTP 27.0, 1.18.5 / 27.3.4.19, 1.19.6 / 28.5.0.8 and 1.20.4 / 29.1.2. Checks included the unit and integration suites, the MCP compliance suite, 2026-07-28 external conformance, Node.js interop, the performance and stress suite, coverage, Dialyzer and strict lint/docs checks. On the merge commit itself the 1.17.3 / 27.0 lane stopped at mix hex.audit: plug_crypto's CVE-2026-105963 was published that morning against the locked 2.2.0. ExMCP only calls Plug.Crypto.secure_compare/2 on binaries of equal size, so it does not reach the affected code path, and the lockfile is not part of the Hex package; the lockfile moves to plug_crypto 2.2.1 in a follow-up.
See the changelog and HexDocs. The attached ex_mcp-1.7.2.tar is the Hex source archive built from this tag (SHA-256 03ad16c59f631a66be4624c320181938c99c44de9bdc18ecee12fa3c4b4b79a2).
ArborMCP 2.0.0-rc.5
ArborMCP 2.0.0-rc.5 replaces 2.0.0-rc.4 with TLS trust fixes and CA certificate options for the HTTPS connections that had none. ArborRPC, ArborACP and the ArborACP adapters remain at 1.0.0-rc.1, and the RPC requirement stays ~> 1.0.0-rc.1.
- Fail closed. Some connections passed no CA certificates, so when the OS trust store could not be loaded, Mint silently trusted the
castorebundle instead.- Affected: the legacy HTTP+SSE transport, OAuth metadata, OIDC discovery and JWKS fetches, and remote JSON Schema fetches.
- With an old
castorelocked, that bundle includes the eMudhra roots removed after their compromise. - These connections now fail closed like other HTTPS requests, unless
config :arbor_mcp, :cacerts, fallback: :castoreis set.
- CA certificate options where there were none:
Arbor.MCP.Authorization.MetadataFetchertakes:cacerts(per call, inconfig :arbor_mcp, :oauth_metadata_fetch, or under a flow'smetadata_fetch:);- remote JSON Schema references take
network_refs: [cacerts: ...]; transport: :ssetakessecurity: %{tls: ...}, liketransport: :http.
verify_none:verify: :verify_noneno longer loads the trust store, so those connections keep working while it is unavailable.
Behavior changes:
- The fail-closed fix only matters when the OS trust store cannot be loaded, for example in a minimal container without
ca-certificates. - The legacy HTTP+SSE transport now reads
:security; it used to ignore it. Over HTTPS it uses the HTTP transport's TLS defaults.
Install {:arbor_mcp, "== 2.0.0-rc.5"} and commit the lockfile. See the changelog and RC testing notes.
This is a release candidate for downstream testing. CI passed on the tagged commit: supported BEAM test lanes, Dialyzer, the MCP compliance suite, 2026-07-28 external conformance, Node.js interop, and four-package and HTTP (Cowboy and Bandit) archive consumer checks on Elixir 1.17.3 / OTP 27.0 through Elixir 1.20.4 / OTP 29.1.1. The stable-promotion gates in the RC notes still apply.
The attached arbor_mcp-2.0.0-rc.5.tar is the Hex source archive built from this tag with no local overrides.
v1.7.1
ExMCP 1.7.1 is a security patch on the maintained 1.x line. It fixes GHSA-2q9v-qvwf-3m8w, rated high, which affects ex_mcp 0.8.0 through 1.7.0. It keeps the ex_mcp Hex package, the :ex_mcp application and the ExMCP.* public namespaces. Use {:ex_mcp, "~> 1.7"} to get it.
- Security: the Claude and Pi ACP adapters appended option values to their CLI command lines without checking them, so a value starting with
-became another flag.- This is the argument injection reported upstream as CVE-2026-96620: a value such as
--mcp-config …can make Claude Code start an arbitrary command. - It's exploitable when an application passes untrusted input as an adapter startup option, such as
:resume,:session_id,:model,:additional_directoriesor Pi's:session_path. - Session IDs from ACP
session/loadandsession/resumerequests don't reach the command line.
- This is the argument injection reported upstream as CVE-2026-96620: a value such as
Behavior change:
ExMCP.ACP.Adapters.ClaudeSDK.Protocol.command/1andExMCP.ACP.Adapters.Pi.cli_command/1now return{:error, {:invalid_option, key, reason}}for a value starting with-or one that isn't a string. Claude:resumeand:session_idmust be session UUIDs.ExMCP.ACP.Registry.npx_command/1validates the npm package specifier, puts--before it, and returns{:error, :invalid_npx_package}otherwise.
The fix was made on ArborACP first and then ported. The 1.7 maintenance release guide records the provenance.
CI validated this release on Elixir 1.17.3 / OTP 27.0, 1.18.5 / 27.3.4.19, 1.19.6 / 28.5.0.8 and 1.20.4 / 29.1.2. Checks included the unit and integration suites, the MCP compliance suite, 2026-07-28 external conformance, Node.js interop, the performance and stress suite, coverage, Dialyzer and strict lint/docs checks.
See the changelog and HexDocs. The attached ex_mcp-1.7.1.tar is the Hex source archive built from this tag.
v1.7.0
ExMCP 1.7.0 is a minor release on the maintained 1.x line. It fixes TLS trust handling and adds CA certificate options for the HTTPS connections that had none. It keeps the ex_mcp Hex package, the :ex_mcp application and the ExMCP.* public namespaces. Use {:ex_mcp, "~> 1.7"} to get it.
- Fail closed. Some connections passed no CA certificates, so when the OS trust store could not be loaded, Mint silently trusted the
castorebundle instead.- Affected: the legacy HTTP+SSE transport, OAuth metadata, OIDC discovery and JWKS fetches, and remote JSON Schema fetches.
- These connections now fail closed like other HTTPS requests, unless
config :ex_mcp, :cacerts, fallback: :castoreis set.
- CA certificate options:
ExMCP.Authorization.MetadataFetchertakes:cacerts;- remote JSON Schema references take
network_refs: [cacerts: ...]; transport: :ssetakessecurity: %{tls: ...}, liketransport: :http.
verify_none:verify: :verify_noneno longer loads the trust store.
Behavior changes:
- The fail-closed fix only matters when the OS trust store cannot be loaded, for example in a minimal container without
ca-certificates. - The legacy HTTP+SSE transport now reads
:security; it used to ignore it. Over HTTPS it uses the HTTP transport's TLS defaults.
The fixes were made on ArborMCP first and then ported. The 1.7 maintenance release guide records the provenance.
CI validated this release on Elixir 1.17.3 / OTP 27.0, 1.18.5 / 27.3.4.18, 1.19.6 / 28.5.0.7 and 1.20.4 / 29.1.1. Checks included the unit and integration suites, the MCP compliance suite, 2026-07-28 external conformance, Node.js interop, the performance and stress suite, coverage, Dialyzer and strict lint/docs checks.
See the changelog and HexDocs. The attached ex_mcp-1.7.0.tar is the Hex source archive built from this tag.
ArborMCP 2.0.0-rc.4
ArborMCP 2.0.0-rc.4 replaces 2.0.0-rc.3 with a security fix for request cancellation (GHSA-22m7-hr37-pxg3). The public API is unchanged. ArborRPC, ArborACP and the ArborACP adapters remain at 1.0.0-rc.1, and the RPC requirement stays ~> 1.0.0-rc.1.
-
Security:
Arbor.MCP.MessageProcessorrecordednotifications/cancelledin a VM-global table keyed only by request ID.- A client could make
Context.cancelled?/0return true for another session's in-flight request that had the same ID. - Cancellations for IDs that never ran stayed in the table, so any client could grow it without bound.
Now a cancellation only reaches an in-flight request from the same HTTP session or, for a sessionless request, the same authenticated principal, tenant and endpoint. A cancellation for an unknown ID adds nothing, and the table is swept and capped.
- A client could make
-
Who was affected: applications that call
Arbor.MCP.MessageProcessordirectly. Runtime-mounted servers, which every HTTP mount requires, already scoped their cancellations and were not affected.
Behavior change: for direct MessageProcessor use without authentication, a notifications/cancelled sent in a separate modern (2026-07-28) HTTP POST no longer cancels a request. That protocol revision cancels an HTTP request by closing its response stream, and Runtime-mounted servers already ignored such notifications.
Install {:arbor_mcp, "== 2.0.0-rc.4"} and commit the lockfile. See the changelog and RC testing notes.
This is a release candidate for downstream testing. CI passed on the tagged commit: supported BEAM test lanes, Dialyzer, the MCP compliance suite, 2026-07-28 external conformance, Node.js interop, and four-package and HTTP (Cowboy and Bandit) archive consumer checks on Elixir 1.17.3 / OTP 27.0 through Elixir 1.20.4 / OTP 29.1.1. The stable-promotion gates in the RC notes still apply.
The attached arbor_mcp-2.0.0-rc.4.tar is the Hex source archive built from this tag with no local overrides.
v1.6.2
ExMCP 1.6.2 is a security patch on the maintained 1.x line. It fixes GHSA-22m7-hr37-pxg3, which affects every earlier ExMCP release. It keeps the ex_mcp Hex package, the :ex_mcp application and the ExMCP.* public namespaces. Use {:ex_mcp, "~> 1.6"} to stay on the 1.x line.
-
Security:
ExMCP.Server.Context.cancelled?/0read a VM-global table keyed only by request ID. HTTP (ExMCP.HttpPlug), the stdio server,HandlerServer, and the:beamand:testtransports all wrote to it.- A
notifications/cancelledfrom any HTTP session, stdio peer or in-VM client could mark another connection's in-flight request with the same ID as cancelled, across transports. - Cancellations for IDs that never ran stayed in the table, so any client could grow it without bound.
A cancellation now only reaches an in-flight request from its own scope:
- the same HTTP session;
- for a sessionless HTTP request, the same authenticated principal, tenant and endpoint;
- for stdio and in-VM transports, the same server process.
A cancellation for an unknown ID adds nothing, and the table is swept and capped.
- A
Behavior change: on modern (2026-07-28) Streamable HTTP without authentication, a notifications/cancelled sent in a separate POST no longer cancels a request, because nothing ties the two POSTs to the same client. That protocol revision cancels an HTTP request by closing its response stream instead.
- ExMCP's own client already cancels this way, and that still works.
- Legacy-era HTTP sessions, authenticated modern requests, stdio and in-VM transports are unaffected.
- A third-party client that sends
notifications/cancelledover modern HTTP should close the request stream instead, or the server should authenticate requests so they carry a principal.
The fix was made on ArborMCP first and then ported, and the regression tests run on both lines. The maintenance release guide records it.
CI validated this release on Elixir 1.17.3 / OTP 27.0, 1.18.5 / 27.3.4.18, 1.19.6 / 28.5.0.7 and 1.20.4 / 29.1.1. Checks included the unit and integration suites, the MCP compliance suite, 2026-07-28 external conformance, Node.js interop, the performance and stress suite, coverage, Dialyzer and strict lint/docs checks.
See the changelog and HexDocs. The attached ex_mcp-1.6.2.tar is the Hex source archive built from this tag.