A
licenseNot graded
qualityC
maintenanceMCP server that bridges AI agents with external tools, APIs, databases, and services, enabling standardized tool execution and resource access.
MIT
Remote MCP
Server Details
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
A4.1/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusing it with others. The tool's purpose is clearly defined as listing and searching remote MCP servers.
Naming Consistency5/5
The single tool name 'ListRemoteMCPServers' follows a clear verb_noun pattern (List + RemoteMCPServers) in camelCase. With only one tool, consistency is trivially maintained.
Tool Count4/5
The server has exactly one tool, which is slightly below the typical 3-15 range, but the narrow purpose of simply listing and searching remote MCP servers justifies this minimal count.
Completeness5/5
The tool fully covers the server's stated purpose of discovering remote MCP servers from two curated sources. There are no missing operations that would leave an agent stranded.
Available Tools
1 toolListRemoteMCPServersARead-onlyIdempotentInspect
List and search for trusted Remote MCP Servers from https://github.com/jaw9c/awesome-remote-mcp-servers and https://remote-mcp.com
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | No |
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the data sources (GitHub and remote-mcp.com), which is useful context. However, it does not disclose details about search behavior, response format, or any filtering semantics beyond the annotation-covered traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is concise and front-loaded with the action. It includes the essential source URLs without any filler, making every word count.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (one optional parameter, no output schema), and the description covers its core purpose and data sources. However, it lacks any description of the return format or query behavior, which the agent would need to fully understand the tool's output and capabilities. Gaps remain around response structure and search semantics.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has one optional parameter 'query' with no description (0% coverage), so the description must compensate. It only implies 'search' meaning the query is used for searching, but provides no details about supported syntax, matching behavior, or examples. This is insufficient for an agent to know how to properly use the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly state the tool lists and searches trusted Remote MCP Servers from specific sources. It uses a specific verb ('List and search'), a resource ('Remote MCP Servers'), and includes the exact source URLs, leaving no ambiguity about its purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly indicates the tool is for discovering trusted Remote MCP servers by referencing the curated sources. Since there are no sibling tools, no explicit alternatives or exclusions are needed; the context is clear enough for an agent to know when to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
ListRemoteMCPServers1 field changed- removed
Input schema / additionalPropertiesRemoved value: -false
1 tool update
- First observed
ListRemoteMCPServers
Related MCP Connectors
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.
- BoxOAuthcom.box.mcp
The Box MCP server is a secure gateway that connects external AI agents to enterprise content stored in Box, enabling agent-based document access, advanced search, and multi-file analysis while preserving Box security policies. It provides capabilities including keyword search, Box AI-powered Q&A across files, metadata extraction, file management, and authentication, all validated against Box's granular permission controls. The server integrates with major AI platforms like Anthropic Claude, Microsoft Copilot Studio, and Mistral Le Chat, and is available both as a Box-hosted remote server and a self-hosted open-source Python project.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseBqualityAmaintenanceA meta-MCP server that manages and aggregates other MCP servers, enabling LLMs to dynamically extend their own capabilities by searching for, adding, and configuring tool servers.16142AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.1MIT
- AlicenseNot gradedqualityBmaintenanceRemote MCP server that aggregates multiple SaaS integrations behind meta-tools, enabling clients to search a catalog by task description and invoke tools by exact name, with an admin portal for managing plugins, API keys, roles, and usage.24Business Source 1.1