Schema Validate MCP Server

by cedrickouma Your server? Claim it

answering

Schema Validate is answering right now. Last checked 10 min ago. 30 installs a week from npm.

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

Installs per day peak 26 · avg 7 · +64% w/w

a month agotoday

Uptime history 47 days of history · worst day 93%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

932 ms

Response time

average over 24h

Installs / week

npm and PyPI

Schema Validate missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add schema-validate --transport http https://apim-agentforge-6lfm33.azure-api.net/schema-validate/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "schema-validate": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/schema-validate/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.schema-validate]
url = "https://apim-agentforge-6lfm33.azure-api.net/schema-validate/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "schema-validate": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/schema-validate/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "schema-validate": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/schema-validate/mcp"
    }
  }
}

This one needs environment variables set before it will start: AGENTFORGE_BASE_URL (AgentForge APIM gateway base URL), AGENTFORGE_API_KEY (APIM subscription key (Ocp-Apim-Subscription-Key / x-api-key)). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://apim-agentforge-6lfm33.azure-api.net/schema-validate/mcp	streamable-http	needs key	649 ms	10 min ago

Alternatives to Schema Validate

same job, measured the same way

JSON Repair

by cedrickouma

MCP server (stdio): repair broken/malformed JSON via the AgentForge API

26 installs/wk answering

Openapi Lint

by cedrickouma

MCP server (stdio): lint OpenAPI specs with Spectral via the AgentForge API

25 installs/wk answering

URL Alive Check

by cedrickouma

MCP server (stdio): check if URLs are alive (status, redirects, latency) via the AgentForge API

25 installs/wk answering

Fetch Extract

by cedrickouma

MCP server (stdio): fetch web pages as clean readable markdown via the AgentForge API

26 installs/wk answering

Validator AI MCP

by csoai-org

AI-powered validator ai MCP server for agents. Supports validate json, validate email, validate

156 installs/wk local only

Rlg MCP

by sebastienrousseau

MCP server exposing rlg log streams to LLM agents via JSON-RPC 2.0 over stdio.

local only

Jsonschema

by pipeworx-io

JSON Schema validation MCP.

32 tools answering

JSON Repair MCP

by grupoanesthy-spec

Repairs malformed JSON from LLM output, validated against a schema. Paid per call via Stripe.

36 installs/wk local only

Schema Validate — questions

Answers built from our own checks of this server.

Why is there no tool list for Schema Validate?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Schema Validate working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 932 ms. The bar chart above shows every period we have measured.

How do I connect Schema Validate?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does Schema Validate need an API key?

Yes. Every time we knock, Schema Validate answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Schema Validate?

It answers our handshake in 932 ms on average, which is faster than 10% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Schema Validate?

The npm package agentforge-schema-validate-mcp was installed 30 times in the last week. Week over week that is +64%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.