Lewis Wang 5a311d8afe fix(mcp): report Linux-only integrations as unsupported_host off their hosts (#5793) ...

* fix(mcp): report Linux-only integrations as unsupported_host off their hosts

Session discovery folded the host check into each optional integration's
enabled flag, so on macOS or Windows the Linux-only packet, signal,
firmware, pwntools, EVM and Wakaru tools reported provider_missing.
Their execution guards refuse those hosts whatever is configured, so
installing a provider there could never make them available.

The server now records, per integration, when the host is outside its
verified host and no service is injected. Discovery checks that before
configuration and reports unsupported_host with the existing
remediation. Injected services and supported hosts behave as before.

Fixes #5730

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* refactor(mcp): share provider host checks with session discovery

Discovery restated each Linux-only integration's host rule in
createServer while its provider kept a separate execution check, so the
two could drift apart again. Each provider now exports its host
predicate, uses it in its execution guard, and composition hands the
same predicate to createServer for both the host restriction and the
enabled flag.

Observed host restrictions now also apply when an embedder supplies its
own availability policy, as provider load failures already do, because
no policy lets the default providers pass their host checks.

The MCP regression moves to tests/process-global and emulates darwin
arm64, linux arm64 and linux x64 through the real createServer, so CI on
Linux x64 exercises the unsupported-host branch. It also covers a
configured policy and the matching execution refusals.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(mcp): keep caller host restrictions beside observed ones

The observed host restriction replaced a configured policy's whole
hostUnsupported map. For an injected service the observed value is
false, so a caller's own restriction was lost and the tool was reported
available. Combine both per integration: either the caller or the
observed host can mark it unsupported.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(pcap): expect unsupported_host for packet tools off Linux

The host-independent PATH case asserted provider_missing on every host.
Off Linux the packet tools are unavailable because of the host, so
discovery now reports unsupported_host there; Linux still reports
provider_missing for an unusable PATH.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-23 05:14:26 +08:00

..

acceptance

fix(cli): preserve Unicode and text across token windows (#5814)

2026-10-23 05:14:05 +08:00

boundary

fix(mcp): report Linux-only integrations as unsupported_host off their hosts (#5793)

2026-10-23 05:14:26 +08:00

composition

refactor(rizin): share validated command requests across admission and execution

2026-10-23 04:29:35 +08:00

conformance

fix(ghidra): treat format-specific disabled analyzers as not applicable (#5425)

2026-10-23 02:24:16 +08:00

evaluation

fix(hopper): keep automated Linux setup off non-x86_64 hosts (#3422)

2026-10-23 02:39:05 +08:00

fixtures

fix(captures): scope HAR HTTP interpretation to entries (#4351)

2026-10-23 02:30:06 +08:00

process-global

fix(mcp): report Linux-only integrations as unsupported_host off their hosts (#5793)

2026-10-23 05:14:26 +08:00

support

feat(artifacts): make ASAR header admission configurable (#6209)

2026-10-21 21:18:22 -07:00

ciTestSequencer.ts

test(acceptance): run loader ownership once through stdio MCP (#6354)

2026-10-23 00:50:47 +08:00

processOwnershipRunner.ts

test(process): retire native caches at worker teardown

2026-10-09 04:12:49 +08:00