JSON Schema Regression Examples — Free Pilot
Free pilot: checked JSON Schema regression examples for a limited subset; no compatibility proof.
needs work
No valid MCP answer at last check (HTTP 404).
Rule R2g · what this means · Not tested in Copilot Studio.
| Registry name | pub.akash.hurricane.ingress.s6d4jqn7rlal7d9hkd64h7pn8o/schema-regression-examples |
| Endpoint used for verdict | https://s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pub/mcp |
| Transports | streamable-http |
| Auth (Copilot Studio setting) | Unknown |
| Last endpoint check | 2026-10-23T22:50:08Z · HTTP 404 |
| Website | https://s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pub/?ref=official-mcp-registry |
| Version | 0.1.0 |
| Registry updated | 2026-09-21 |
Standards signals
| Official MCP Registry | Listed (active) MCP Registry |
| server.json schema | 2025-12-11 · currentserver.json schema changelog |
| Transport | Streamable HTTP (remote) Transports: Streamable HTTP |
| Answers MCP | No valid MCP answer at last check Lifecycle: initialization |
| Spec version spoken | Not observed Versioning |
| Supports 2026-07-28 | Not detected server/discover |
Observed from public registry data and a read-only, unauthenticated check on 2026-10-23. Not a certification: AAIF and the MCP project don't certify servers, and these lines are signals, not pass/fail. They don't change the Copilot Studio verdict. Own this server? modelcontextprotocol/conformance: test your own server.
Track changes like this weekly. New Copilot-ready MCP servers, breakages and auth changes, in one short email.
Is this wrong or out of date? Email us. Data built 2026-10-24.