Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://apim-agentforge-6lfm33.azure-api.net/schema-validate/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http io.github.cedrickouma-schema-validate https://apim-agentforge-6lfm33.azure-api.net/schema-validate/mcpRun in a terminal.
{ "mcpServers": { "io.github.cedrickouma-schema-validate": { "command": "npx", "args": [ "-y", "mcp-remote", "https://apim-agentforge-6lfm33.azure-api.net/schema-validate/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchTools
No tool list yet. Remote servers get one after the first health check.
FAQ
MCP server (stdio): validate JSON against JSON Schema (draft-07 / 2020-12) via the AgentForge API
{ "mcpServers": { "io.github.cedrickouma-schema-validate": { "url": "https://apim-agentforge-6lfm33.azure-api.net/schema-validate/mcp", "headers": {} } }}Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: AGENTFORGE_BASE_URL, AGENTFORGE_API_KEY.
Schema Validate is reached over HTTP.
Last checked 2026-11-09. MCP server (stdio): validate JSON against JSON Schema (draft-07 / 2020-12) via the AgentForge API
From the publisher
README is not crawled yet. No repository on file.
MCP server (stdio): validate JSON against JSON Schema (draft-07 / 2020-12) via the AgentForge API
© 2026 MCP Directory.