"How to create a remote directory" matching MCP servers:

Remote MCP server for verifying API key authentication header propagation and debugging inbound HTTP headers.

Enables Claude to create local, persistent mock REST APIs on demand from plain-language descriptions, with data written to disk so it survives restarts.

Automated QA for .NET microservice backends and React frontends, enabling API contract testing, UI crawling, YAML flows, and run diffing against a stage environment.

Enables MCP-capable agents to search the curated gold-402 directory of x402 services, probe any endpoint for valid 402 payment terms, and optionally purchase a human editorial verdict for a resource.

A stdio MCP server that audits other MCP servers over the live protocol. It connects to any MCP target (stdio or HTTP), lints every tool's schema for agent-usability, then actually calls the tools with deliberately broken inputs to see how the server handles them, and returns a 0–100 conformance score with a per-dimension breakdown rendered as Markdown.

Enables testing how different MCP clients handle tool results containing both content and structuredContent, including outputSchema enforcement and mismatch scenarios.

A read-only API change deploy gate for AI coding agents that analyzes OpenAPI specs to determine if changes are safe to deploy. It provides tools for comparing specs, explaining breaking changes, and generating migration guides.

Enables AI agents to create, run, and manage HTTP requests using the Invoker API client's .ivk format. It provides tools for scanning collections, executing requests, managing environments, and building documentation sites.

An MCP server for interacting with Treasure Data API, allowing users to retrieve database information and check server status through natural language queries.

Autonomous synthetic health checks, JSON-RPC 2.0 handshake validation, breaking schema drift detection, and credential leak scanning for remote MCP servers.

Probes your live API and classifies why each endpoint failed (root cause, evidence, and a calibrated confidence level), exposed over MCP so your AI assistant debugs from evidence instead of guessing. Works with FastAPI, Express, Next.js, tRPC, and GraphQL.

Enables MCP agents to create test webhook endpoints, read incoming requests, validate payloads against Hookline validators, and manage mock responses directly from the editor.

Enables AI agents to discover and read Typeship API documentation and execute API operations through schema-validated MCP tools, with optional read-only mode and configurable result limits.

A generic MCP server that dynamically exposes any OpenAPI-documented REST API to LLMs by auto-discovering endpoints. It provides tools for exploring API capabilities and making authenticated requests directly through natural language interfaces.

An MCP server for Tern that enables the generation, verification, and management of webhook handlers across over 16 platforms and various frameworks. It provides tools to create verified endpoints, debug signature failures, and manage failed event replays via dead letter queues.

Converts any OpenAPI/REST API into MCP tools with dynamic server switching, variable substitution, and runtime configuration. Enables seamless interaction with multiple API environments through natural language without pre-configuration.

Enables interaction with Webhook.site to create, manage, and monitor endpoints for capturing HTTP requests, emails, and DNS lookups. It provides 16 tools for testing webhooks and inspecting incoming data through the Model Context Protocol.

A TypeScript-based MCP server that enables AI assistants to execute HTTP requests with full control over methods, headers, and body content. It facilitates seamless interaction with web APIs and endpoints through a versatile tool that handles automatic JSON formatting and response truncation.

A reusable MCP server for QA automation testing that enables running tests across web apps, APIs, CLI tools, and more directly from Claude Desktop.

Enables local analysis of OpenAPI 3 and Swagger 2 JSON/YAML spec files on disk, with no remote fetching of specs or credentials. It groups endpoints by tag, flags operations that appear to lack security, lists deprecated operations, and produces short markdown cheat sheets for agents.