gekro
GitHub LinkedIn
AI

MCP Server Tester

Paste your MCP server's tools/list output, validate against the protocol spec, simulate a tool call without any LLM cost.

Tool schemas

Paste either a full tools/list response (with tools: [...]) or a raw array of tool definitions.

Try a tool call Pick a tool

Tool args are validated against the tool's inputSchema. This simulates the JSON-Schema check an MCP server would do before invoking the tool function.

What the LLM sees

This is the actual JSON formatted as it would appear in an LLM's tool-use context. Token estimate uses ~4 chars/token.

 

— tokens

Validation

Paste tools to validate

Total tools
Valid
Errors
Warnings

Findings

    Call result

    🔒 All validation runs in your browser. MCP servers are never contacted.

    As-is, no warranty. These apps are free under their listed license and run entirely in your browser. Use at your own risk — don't blame me if your PC catches fire, your dog runs away, or the math turns out wrong. Verify anything that actually matters. None of this is professional financial, medical, legal, or engineering advice.

    © 2026 Rohit Burani · MIT · Built at gekro.com · View source ↗

    Guide

    What It Does

    The Model Context Protocol (MCP) is the standard for exposing tools to LLMs (Anthropic’s Claude Code, Cursor, Continue, and many other clients use it). MCP servers ship tools whose schemas the LLM reads to decide when and how to call them. Bad schemas = bad tool selection = burned tokens.

    This tool catches schema issues before they ship:

    1. Paste your server’s tools/list response (or just an array of tools)
    2. Validator runs against MCP protocol requirements + LLM-friendliness heuristics
    3. See exactly the JSON-context format the LLM would receive
    4. Simulate a tools/call to verify arguments validate against your inputSchema

    Checks Performed

    Spec requirements (errors):

    • Missing name field
    • Missing inputSchema field
    • inputSchema.type must be "object"

    Best practices (warnings):

    • Name contains chars outside [a-zA-Z0-9_-] (some clients restrict)
    • No description (LLM tool selection works better with detailed descriptions)
    • Description shorter than 20 chars (under-specified)
    • Properties without description (argument purpose unclear)
    • Properties without type (LLMs may guess wrong)

    Tool-Call Simulation

    Pick a tool from the dropdown - the tool auto-generates a starter argument stub from your schema. Edit the JSON, watch the validator catch violations in real time:

    • Type mismatches ("5" where "integer" was expected)
    • Missing required properties
    • Enum violations ("meters" not in ["imperial", "metric"])
    • Number range violations (limit: 30 when maximum: 20)
    • String length / unknown property warnings

    This is the same JSON-Schema check your server probably does in code - run it in the browser before round-tripping through an actual LLM.

    What the LLM Sees

    The tool also shows you the exact JSON your tools become in the LLM’s context window, formatted as the major clients format it. The token estimate is your per-request cost when the tools are loaded (use Prompt Cache Optimizer to see if you can cache them).

    What’s NOT In Scope

    • Live server testing - no network calls. Paste-only.
    • MCP transport protocols (stdio/SSE/HTTP) - just the schema layer
    • OAuth flows - MCP authentication isn’t covered here
    • Tool result validation - only input validation

    For informational purposes only. Not financial, medical, or legal advice. You are solely responsible for how you use these tools.