Add CanMCP endpoint diagnostics skill - #41
Open
OlegNickeshin wants to merge 1 commit into
Open
Conversation
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
Add CanMCP, an agent skill for diagnosing public remote MCP endpoints with the existing local Python CLI.
Typical intent: Diagnose why this MCP endpoint fails to connect, without executing any server tools.
Scope
This entry is
application/ai-skill, not an MCP server. CanMCP remains a CLI requiring command execution, Python 3.11+ and direct DNS/HTTP(S) access. There is no hosted scanner or remote connector endpoint.The skill explains how to run a bounded scan, read JSON and nonzero exit codes, distinguish protocol failures from incomplete inspections, and preserve the scanner's public-target/TLS boundary. Normal inspection does not sign in, register clients or call server tools. Optional OAuth requires user authorization; Dynamic Client Registration may leave a provider-side registration. The browser for the loopback callback must run on the CLI machine. Results are local diagnostics, not conformance certification or proof that a particular ChatGPT/Claude account can connect.
No endpoint credentials, private targets, conversation content or tokens are published. Secret path segments require redaction before sharing reports.
Validation
python3 scripts/generate_ai_catalog.pyand--checkpassed.Only
catalog/OlegNickeshin/canmcp.jsonis committed here.metadata.sourceSetisOlegNickeshin/canmcp, as required by the validator. Regeneratingai-catalog.jsonalso changes unrelated live upstream metadata (1,844 diff lines); it was validated locally but omitted from this focused source-entry PR. The documented main-branch fallback can regenerate the ingestion artifact after merge. No generator or workflow changes.