[KryptosAI]

This adds a lightweight MCP Observatory check for the reference server-everything MCP server.\n\nWhy it helps:\n\n- verifies MCP tools, prompts, and resources still respond correctly\n- catches schema drift and common security footguns before release\n- posts a readable PR report for maintainers\n- gives users a compatibility signal when evaluating MCP servers\n\nI validated the target locally with:\n\nbash\nnpx @kryptosai/mcp-observatory@latest test --target mcp-observatory.target.json --security --deep\n\n\nResult: passed, with 13 tools, 4 prompts, and 7 resources detected from npx -y @modelcontextprotocol/server-everything@latest.\n\nIt runs in GitHub Actions and does not require an MCP Observatory account. If this is too broad for the repo, I can scope it differently or adjust the workflow.

[cliffhall]

Thank you for this pull request, and apologies for the long wait for a response.

These servers are reference implementations: they exist to show how each part of MCP is used, not to be general-purpose products, so new features are taken selectively, and this change isn't one the maintainers plan to take. This repository also now accepts issues, not pull requests, from anyone but its maintainers; the policy is in CONTRIBUTING.md.

This is not a judgment on the idea or on you. A server in the MCP Registry may well offer it, and anyone is welcome to build on these servers to do so. If you think we've misread it, please open an issue describing the problem and the expected behavior.

This is part of the backlog triage in #4875.