"A comparison for backend service architecture" matching MCP servers:

Provides tools to communicate with a service dependency API, enabling users to query and interact with service relationship data and dependency mappings.

A unified HTTP/HTTPS service that exposes Model Context Protocol (MCP) functionality over HTTP endpoints, allowing clients to list available tools and call them through a standardized API.

A CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.

Enables AI assistants to interact with the Post For Me API, allowing them to explore endpoints, make test requests, and use documentation to help integrate this SDK into your application.

MCP server for Akamai APIs. 198 tools covering Property Manager, Edge DNS, CPS, WAF, and reporting. Built with TypeScript, featuring modular architecture, comprehensive testing, and multi-account support. Make Akamai accessible to AI assistants.

Free x402 endpoint checker plus paid report and metadata tools. Remote MCP server for agents. Written by AI named Nock, not a human.

A bridge that converts HTTP APIs into MCP tools with dynamic toolkit loading, flexible authentication, and automatic documentation.

Provides AI assistants with access to OpenAPI specifications, enabling API discovery, schema retrieval, and direct API execution with support for OAuth 2.0 and other authentication methods.

This server enables interacting with the National Digital Health Mission's Health Information User (HIU) API, allowing agents to access and manage health information through the Multi-Agent Conversation Protocol.

A Model Context Protocol service registry and connector framework that enables seamless integration with multiple services and models through a standardized API interface. Provides an extensible architecture for custom service adapters, API integrations, and model registries.

Lets AI assistants safely explore a Matrix42 instance by discovering web services and the data model, running validated ASQL queries, searching the service desk, and previewing ticket actions — read-only by default and without exposing credentials.

Provides a generic HTTP client tool allowing AI agents to make arbitrary HTTP requests from their environment, with support for environment-variable placeholders for secrets.

CLIRank - API discovery for AI agents. APIs scored on CLI relevance: auth method, JSON responses, headless operation, pricing transparency. Search by capability, compare alternatives, read agent-contributed docs. 6 MCP tools for discovery, comparison, and documentation. Agents contribute observations back - crowdsourced API docs by machines, for machines.

An MCP server that makes backend API requests and packages request+response pairs as evidence to prove an endpoint works.

A standalone MCP server for API debugging, login authentication, API configuration management, and indexed API execution.

MCP server for gRPC — service discovery via server reflection, method invocation, and type schema inspection for AI agents.

MCP server for scanning smart contracts for security vulnerabilities. It detects issues like reentrancy, overflow, access control, and provides security scores with NEAR-specific recommendations.

A lightweight MCP server for searching SmugMug documentation and calling the live SmugMug API.

API documentation drifts away from the running service, so consumers integrate against a contract nobody keeps. Routebase keeps API design, testing, mocking and documentation on one living source of truth, and this MCP server lets AI agents work in that workspace under the permissions of the connected account.

A Model Context Protocol server that provides Claude Code with seamless access to Binance exchange API functionality for market data retrieval, account management, and trading operations.