ajv-validator-mcp-server

Created By
mallanispa year ago
Overview

what is ajv-validator-mcp-server?

ajv-validator-mcp-server is a minimal Model Context Protocol (MCP) server designed for validating JSON data against JSON Schema using AJV.

how to use ajv-validator-mcp-server?

To use the ajv-validator-mcp-server, build the project by installing dependencies and compiling TypeScript sources, configure the MCP server with the appropriate settings, and start the server using npm start or by running the built file directly with Node.js.

key features of ajv-validator-mcp-server?

  • Exposes an MCP tool ajv-validator for validating JSON data against a provided schema.
  • Integrates ajv-formats for extended format validation.
  • Designed for easy integration with MCP-compatible clients and tools.

use cases of ajv-validator-mcp-server?

  1. Validating JSON data for compliance with specific schemas in applications.
  2. Integrating with other MCP-compatible tools for enhanced data validation workflows.
  3. Debugging and testing JSON validation processes interactively using the MCP SDK Inspector.

FAQ from ajv-validator-mcp-server?

  • What is the purpose of the ajv-validator tool?

The ajv-validator tool validates JSON data against a provided JSON Schema, ensuring data integrity and compliance.

  • How do I start the MCP SDK Inspector?

You can start the MCP SDK Inspector by running npm run inspector, which connects it to your built MCP server for interactive testing.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mallanisp
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago