JSON Schema Regression Examples — Free Pilot

pub.akash.hurricane.ingress.s6d4jqn7rlal7d9hkd64h7pn8oPublished by s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pubOfficial publisherv0.1.0Updated Oct 24, 2026

Free pilot: checked JSON Schema regression examples for a limited subset; no compatibility proof.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A free pilot MCP endpoint offering checked JSON Schema regression examples for a limited subset, with no compatibility proof.

What you can do
Provides checked JSON Schema regression examples, limited to a small subset of cases, as reference material an assistant can draw on when discussing schema behavior. The manifest lists no tools, so the exact operations available are not documented. It is a free pilot, so coverage and behavior may be narrow or change.
When to use it
Possibly useful when you want illustrative JSON Schema regression examples during schema-related work and are willing to accept a limited, unproven pilot. Not suitable when you need verified compatibility guarantees or broad coverage.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables, headers or authentication are declared. Network access to the provider's host is needed.
Before you install
The description explicitly states there is no compatibility proof, so results should not be treated as authoritative. No tools, authentication or data-handling details are documented, and it is a free pilot that may change or disappear.

Installation

In SourceWeft

  1. Open JSON Schema Regression Examples — Free Pilot in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/pub.akash.hurricane.ingress.s6d4jqn7rlal7d9hkd64h7pn8o%2Fschema-regression-examples/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "json-schema-regression-examples-free-pil": {
      "type": "http",
      "url": "https://s6d4jqn7rlal7d9hkd64h7pn8o.ingress.hurricane.akash.pub/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 21, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.