JSONBuddy Data Validator

Created By
Clemens Uhlenhuta year ago
This project provides an MCP-compatible interface for the JSONBuddy Core API, enabling JSON validation against schemas via a secure HTTP-based service. The server exposes two endpoints (`/validator/validate` and `/validator/validate-simple`) for flexible schema validation scenarios. MCP clients and AI agents can integrate this API using the included `mcp.json` definition and standard API key authentication.
Overview

JSONBuddy Core API

The JSONBuddy Core API provides server-side validation of JSON data against JSON Schema definitions. Currently, it offers two endpoints:

  • Simple validation for quick checks with plain JSON strings.
  • Advanced validation supporting structured input.

This MCP Server enables AI agents, workflows, and automation tools to ensure the correctness of JSON data in real-time. The service is fast, secure, and requires an API key for authenticated use.

Server Config

{
  "mcpServers": [
    {
      "url": "https://www.json-buddy.com/core-api/mcp.json",
      "name": "JSONBuddy Core API",
      "description": "Validate JSON data against JSON Schema with server-side processing.",
      "tags": [
        "json",
        "validation",
        "schema",
        "api",
        "developer-tools"
      ],
      "logoUrl": "https://www.json-buddy.com/images-jsonbuddy/jsonbuddy_logo_128.png",
      "command": [
        {
          "name": "Validate JSON (Simple)",
          "description": "Validate a JSON document against a JSON Schema string using the /validate-simple endpoint.",
          "method": "POST",
          "path": "/validator/validate-simple",
          "params": {
            "schema": {
              "type": "string",
              "description": "The JSON Schema to validate against."
            },
            "data": {
              "type": "string",
              "description": "The JSON document to validate."
            }
          }
        },
        {
          "name": "Validate JSON (Advanced)",
          "description": "Validate a JSON document using the /validate endpoint, supporting schema pools and structured JSON input.",
          "method": "POST",
          "path": "/validator/validate",
          "params": {
            "schema": {
              "type": "array",
              "description": "An array of JSON Schema documents to validate against."
            },
            "data": {
              "type": "object",
              "description": "The JSON data object to validate."
            }
          }
        }
      ]
    }
  ],
  "github": "https://github.com/Clemens-U/jsonbuddy",
  "env": {
    "X-Api-Key": "YourSecretApiKey"
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Clemens Uhlenhut
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago