"A server or tool for local-only resources or information" 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.

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

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.

Extracts and analyzes key frames from Loom videos or local video files for debugging purposes. Automatically detects scene changes and provides visual context for troubleshooting issues.

A multi-language testing automation server that enables AI assistants to discover, plan, and execute tests across six major programming languages. It provides comprehensive tools for repository scanning, automated test execution, and detailed coverage reporting.

Guarded, profile-driven Charles Proxy automation for macOS and Android testing. Uses immutable TOML profiles and explicit plan/apply confirmation.

A local MCP server that lets Claude Code and Codex delegate repository exploration and test proposals to a remote LM Studio model, while enforcing security boundaries by keeping all repository access read-only and never applying patches or running commands remotely.

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.

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.

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.

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 local MCP server that provides adversarial code review by having one frontier agent (Claude Code or Codex) critique code changes using the other agent (Codex or Claude Code) with full repository access, enabling a genuine second opinion on code and plans.

Audits local package folders to generate publish-readiness reports and previews of NPM tarball contents. It helps developers identify and resolve configuration issues like missing types or broken exports before releasing code.

A reference MCP server that enforces identity-aware tool access using role-based permissions (Reader, Analyst, Auditor) and supports multiple identity routes like Entra RBAC, Copilot Studio, and Okta XAA. It provides read-only access to test evidence with explicit denial paths for unauthorized tools.

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).