Schema Validate

io.github.CedricKoumaPublished by GitHub account CedricKoumav0.1.0Updated Oct 24, 2026

MCP server (stdio): validate JSON against JSON Schema (draft-07 / 2020-12) via the AgentForge API

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant validate JSON documents against JSON Schema (draft-07 or 2020-12) through the AgentForge API.

What you can do
This MCP server exposes schema validation: it sends JSON content and a JSON Schema to the AgentForge API and returns whether the document conforms, using draft-07 or 2020-12. It runs either as a local stdio process from the npm package agentforge-schema-validate-mcp or as a remote streamable HTTP endpoint. The manifest lists no individual tools, so the exact tool names and parameters are not documented here.
When to use it
Useful when an assistant needs to check that generated or edited JSON matches a schema, for example validating configuration files, API payloads, or structured output before it is used.
Requirements
Either a local Node.js runtime for the npm package or the remote endpoint. An AgentForge APIM subscription key is required, supplied as the AGENTFORGE_API_KEY environment variable or the Ocp-Apim-Subscription-Key header; the optional AGENTFORGE_BASE_URL sets the gateway base URL. Network access to the AgentForge gateway is needed.
Before you install
The server requires an API subscription key, which is a secret; keep it out of logs and shared configuration. JSON documents and schemas you submit are sent to the third-party AgentForge API for validation, so avoid sending sensitive payloads. The manifest notes a free tier works for smoke tests, implying paid tiers may exist.

Installation

In SourceWeft

  1. Open Schema Validate in the dashboard and add it to a workspace.
  2. Connect Ocp-Apim-Subscription-Key credentials. They are stored privately and never shown on public pages.
  3. 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/io.github.CedricKouma%2Fschema-validate/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": {
    "schema-validate": {
      "type": "http",
      "url": "https://apim-agentforge-6lfm33.azure-api.net/schema-validate/mcp",
      "headers": {
        "Ocp-Apim-Subscription-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

60% 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 listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.