JSON Schema Regression Examples — Free Pilot
REMOTE · S6D4JQN7RLAL7D9HKD64H7PN8O.INGRESS.HURRICANE.AKASH.PUB
Free pilot: checked JSON Schema regression examples for a limited subset; no compatibility proof.
Available components
Last scanned (21 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pub/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.hurricane.akash.pub | CN=YR2,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 5d6587ace79d44753640e9447a803ab43a4 |
| SANs: *.hurricane.akash.pub, *.ingress.hurricane.akash.pub | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pub. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pub. | present | 53776 | 8 | Verified |
| akash.pub. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pub/mcp | HTTP error | 404 | |
| http (plaintext) | http://s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pub/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
acknowledge_package_received ~92
Explicitly acknowledge receiving one generated package in this anonymous session. Call only after the user or client confirms receipt; never call automatically. This is a client-reported acknowledgment, not evidence of file verification, purchase, payment or human identity.
| Name | Type | Req | Description |
|---|---|---|---|
| attempt_id | string | yes | Attempt id returned with the generated package. |
| session_token | string | yes | Anonymous session token returned by this MCP tool; not an operator credential. |
No output schema declared.
No examples provided.
generate_regression_examples Generate JSON Schema regression examples ~261
Free pilot: generate bounded old-accepted, new-rejected JSON Schema examples. An inconclusive result never proves compatibility. Schemas and results are processed in memory; only anonymous coarse usage outcomes are retained. Supply schemas as JSON strings to preserve large integers. Read value_json for exact examples. No API key, model call or payment is needed. Keep the returned anonymous session_token and attempt_id for optional, explicit receipt acknowledgment and nonbinding future-price interest. Never acknowledge receipt or price interest automatically. Supported subset: one explicit type, properties, required, boolean additionalProperties, items, enum, minimum/maximum, minLength/maxLength and minItems/maxItems. No references, composition, patterns, formats or full OpenAPI. Both the HTTP JSON envelope and the combined UTF-8 schema text are limited to 64 KiB; escaping may make the envelope limit stricter. The complete response is limited to 1 MiB. Returns exact example strings and generated file contents for local verification.
| Name | Type | Req | Description |
|---|---|---|---|
| new_schema_json | string | yes | New schema encoded as a JSON string. |
| old_schema_json | string | yes | Old schema encoded as a JSON string. |
| session_token | string | – | Anonymous session token returned by this MCP tool; not an operator credential. |
No output schema declared.
No examples provided.
record_price_interest ~153
Record explicit, voluntary, nonbinding interest in a future package priced at 29 USD. Call only when the user or client has expressly indicated this interest; never infer interest from generating or receiving a package. Requires the same custom supported schema attempt to have produced a verified counterexample and received an explicit receipt acknowledgment. This is not an order, checkout, subscription, purchase or payment; no money moves and no external contact is made. The current pilot remains free.
| Name | Type | Req | Description |
|---|---|---|---|
| attempt_id | string | yes | Attempt id returned with the generated package. |
| price_usd | integer | yes | – |
| session_token | string | yes | Anonymous session token returned by this MCP tool; not an operator credential. |
| voluntary | boolean | yes | – |
No output schema declared.
No examples provided.
How do I install the JSON Schema Regression Examples — Free Pilot MCP server?
JSON Schema Regression Examples — Free Pilot is a hosted endpoint at https://s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pub/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pub
claude mcp add --transport http pub-akash-hurricane-ingress-s6d4jqn7rlal7d9hkd64 'https://s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pub/mcp'
What is the JSON Schema Regression Examples — Free Pilot MCP server?
JSON Schema Regression Examples — Free Pilot is an MCP server listed in the public MCP registry as pub.akash.hurricane.ingress.s6d4jqn7rlal7d9hkd64h7pn8o/sche…. Free pilot: checked JSON Schema regression examples for a limited subset; no compatibility proof. This page covers its hosted endpoint (https://s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pub/mcp).
Is the JSON Schema Regression Examples — Free Pilot MCP server safe to use?
JSON Schema Regression Examples — Free Pilot scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the JSON Schema Regression Examples — Free Pilot MCP server expose?
JSON Schema Regression Examples — Free Pilot exposes 3 tools: generate_regression_examples, acknowledge_package_received, record_price_interest. Their descriptions and schemas cost roughly 506 tokens of context every time the server is loaded.
Does the JSON Schema Regression Examples — Free Pilot MCP server require authentication?
Its publisher declares no required credentials for JSON Schema Regression Examples — Free Pilot. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the JSON Schema Regression Examples — Free Pilot MCP server still maintained?
JSON Schema Regression Examples — Free Pilot is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.