Repository navigation
Conversation
Allow an explicitly selected read-only MCP tool to validate connection health with JSON arguments and an optional identity field. Keep discovery-only health when no probe is configured. Fixes UsefulSoftwareCo#2354
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Let users select one read-only MCP tool and its JSON arguments as an account health check. Candidates must have matching schemas across visible connections and must not be marked destructive. Error results, malformed responses, and auth or scope failures fail the check. Diagnostics redact credentials and discard upstream error text. Without a configured tool, health remains discovery-only.
Two changes outside the editor:
refreshCatalog, which reports whether discovery completed. A failed refresh offers no tools instead of a stale catalog. Existingrefreshcallers are unchanged.contentfield are now rejected. The SDK previously filled incontent: [], so{}passed as a success. This applies to ordinary tool calls too.Linked issue
Fixes #2354
Related to #2300. A suitable configured probe could detect that failure; its authentication cause remains separate.
Verification
bun run format:checkbun run lintbun run typecheckbun run test: passes with--filter=!@executor-js/cloud(38 tasks). The full run has 3 cloud membership-mirror failures that also fail on the base commit.Positive MCP selection/execution has component and plugin coverage; the published emulator offers no read-only tool for browser coverage.
Checklist
executor.Recordings
MCP without an eligible probe keeps discovery-only health.
Existing HTTP POST arguments still preview, save, and reopen.