"Developing an application by analyzing specified development and API documentation" matching MCP servers:

Enables AI-assisted development of CodeQL queries for security analysis through the Model Context Protocol. Provides tools for compiling, testing, and executing CodeQL queries across multiple programming languages.

An MCP server providing AI-powered cybersecurity, penetration testing, reconnaissance, vulnerability assessment, and security automation tools through the Model Context Protocol.

A hosted Model Context Protocol server that lets AI agents triage review queues, investigate authors, tune policies and wordlists, respond to incidents, configure projects and webhooks, and report on moderation activity through a Moderation API account.

Dependency health checker for AI agent skills. Analyzes external endpoints for uptime, SSL validity, domain reputation, ownership changes, and abuse scores. Returns a 0-100 trust score per endpoint.

MCP server for inspecting email domains and addresses, providing objective domain-level email infrastructure answers such as MX, SPF, DMARC, MTA-STS, and disposable-domain evidence.

Enables AI assistants to manage Namecheap domains, DNS, contacts, registrar locks, and view SSL certificates and pricing through safe read and configuration tools.

A comprehensive suite of HTTP and API testing tools that enables AI agents to perform requests, check endpoint health, and decode JWTs. It also provides utilities for URL parsing and detailed security analysis of HTTP response headers.

Enables testing API authentication and authorization by probing endpoints with and without Authorization headers, suggesting auth test matrices for roles, and showing current test configuration.

Enables scanning OpenAPI specifications for security gaps and generating security test checklists for APIs.

Signed, offline-verifiable authorization for API-contract changes. Before a contract change (OpenAPI, GraphQL, Protobuf, AsyncAPI, MCP manifests) merges or deploys, the agent calls preflight_change_set; the decision is deterministic, signed, and verifiable without calling CodeRifts. Three tools: preflight_change_set, verify_receipt, get_decision_details. Only a granted change can proceed.

A Model Context Protocol server implementation that provides endpoints for wallet-based authentication, cluster management, and name registration services.

This server provides a Model Context Protocol interface for the FusionAuth API, enabling users to manage users, applications, and authentication configurations through natural language. It supports over 300 tools for various operations, including creating, searching, and retrieving data from a FusionAuth instance.

MCP server for Intelation Nexis. It lets Claude, Cursor, VS Code and other assistants detect and remove names, emails, phone numbers, NHS and SSN numbers from text. Methods include redact, replace, mask, hash, pseudonymize, tokenize and encrypt. Tools: anonymize_text, detect_pii, list_countries, plus an optional decrypt_text that is off by default. Needs a free API key from nexis.intelation.com.

Scan-as-a-Service for MCP servers. Wraps the compuute-scan static security scanner with HTTP and MCP endpoints to analyze public GitHub repos for MCP-specific vulnerabilities.

Enables AI assistants to search and retrieve information from the REMnux malware analysis toolkit documentation, allowing users to ask questions about reverse-engineering tools and get accurate, up-to-date answers from the live documentation.

Enables Claude and ChatGPT to call upstream APIs that existing connectors cannot, by registering credentials and using short-lived gateway tokens relayed through a Cloudflare Workers remote MCP server.

MCP server for deterministic context preflight, token counting, and credential redaction for coding agents, with a free local tier up to 12,000 characters and paid HTTP fallback for larger inputs.

Comprehensive email validation MCP server that checks syntax, MX records, disposable domains, role-based accounts, SPF/DKIM, typo suggestions, and risk scoring.

Turns an OpenAPI specification into a broker-published slot of curated, LLM-ready tools that a human operator reviews, tests, and approves before anything goes live. The resulting tools are declarative and run under the broker's authorization, audit, execution limits, and secret handling.

Enables a private, owner-authenticated MCP client to call approved upstream APIs through a server-owned registry, with server-held credentials, fixed origins, bounded responses, and distinct read/write tools. Writes are opt-in and durably recorded with stable operation identifiers.