"A tool for generating SVG graphics" matching MCP servers:

MCP server enabling Claude Code to capture screenshots of Windows applications through WSL2, allowing AI to diagnose UI errors and verify layouts.

Audits MCP tool descriptions for quality and reliability, scoring them 0-100, detecting smells, and providing rewritten versions for better agent accuracy.

A validation layer for AI coding assistants that enforces explicit LLM evaluations on plans, code diffs, and tests to ensure safer and higher-quality code.

Protects AI agents from bad tool outputs, schema mismatches, and tool poisoning by validating, sanitizing, and scoring reliability of tool responses.

Enables verification of deployment-scoped model-visible DSH tool surface conformance by checking recorded tool identities and schemas against approved locks, reporting only drift categories and hashes.

Analyzes multi-step AI agent tool chains to compute success probability, identify bottlenecks, and suggest better execution orders, enabling more reliable agents via local pure-math computation.

A lightweight multi-provider MCP testing fixture with two providers (eva_air and uk_railway), each exposing 5 tools using in-memory fake data, designed for verifying MCP client tool discovery, tool calls, and multi-provider routing.

This MCP server verifies that an agent’s claimed tool output matches the actual response returned by a tool to prevent invented or distorted results. It flags mismatches, omissions, and invented fields to ensure downstream logic only processes verified tool data.

MCP-first A/B testing server that enables agents to manage experiments (create, update traffic splits, read results, apply winning variants) from tools like Claude Code, with self-hosted Cloudflare backend.

MITM proxy MCP server that intercepts and verifies AI agent tool calls, detecting fabrication, tracking costs, verifying outcomes, and inferring user satisfaction.

A throwaway HTTP MCP server that empirically tests whether Cursor invokes tools by exact name or munges them, to inform case normalization decisions.

An MCP Server that provides access to Google's Cloud Tool Results API, enabling applications to programmatically interact with test results from Firebase Test Lab and mobile app testing through natural language.

Zero-sidecar MCP server embedded directly in the Godot 4 editor as a GDScript EditorPlugin — no Node or Python sidecar. Reflection-driven tools over any engine class, validate-before-write GDScript, scene/script/resource authoring, and a runtime play-test loop (play, screenshot, input, assert).

Enables installing, launching, and inspecting Android APKs on a dedicated emulator, with screen capture, UI tree inspection, and touch/navigation control via MCP tools.

Enables autonomous agents to automatically repair and guard tool-call schemas through deterministic AST analysis and parameter projection validation, ensuring reliable, schema-compliant interactions in MCP-compatible environments.

Generates a pytest suite from acceptance criteria that are withheld from the coding agent, so the tests can disagree with the code. Four tools, and qikly_run never returns the criteria, which a test in the suite enforces.

MCP server that brings Trustabl static reliability scanning into Cursor, letting agents inventory agents/tools, flag risky patterns, score production readiness, and write SARIF reports.

Exposes a fictional smart-home store's REST API to agents as schema-validated MCP tools, resources, and prompts, letting them search products, check inventory, place atomic orders, look up customers and orders, and open support tickets. It also adds auth injection, rate limiting, REST-to-MCP error mapping with actionable hints, per-call JSONL tracing, and a golden-task eval harness for tool selection and argument correctness.

An MCP server that exposes a document store for evaluating agent tool-use accuracy and measuring resistance to indirect prompt injection, with built-in conformance to the 2026-07-28 MCP protocol.

A Unity Editor command bridge that uses JSON files under .codex/unity-commands for request/response, enabling tools to check Unity status, execute editor commands, parse test results, and capture screenshots.