How We Review and Evaluate MCP Servers
Our methodology for discovering, evaluating, documenting, and maintaining MCP server listings on Lord of Claude.
Lord of Claude is building a focused discovery resource for the growing Model Context Protocol (MCP) ecosystem. Our MCP directory is designed to help developers discover servers, understand what they do, evaluate their available capabilities, and find the original project and documentation.
The MCP ecosystem changes rapidly. New servers appear regularly, existing projects release new versions, documentation changes, and repositories may become inactive or move to new locations. For that reason, a useful MCP directory needs more than a collection of names and links.
This page explains how Lord of Claude approaches MCP server discovery, evaluation, classification, and ongoing maintenance.
What We Look For
When evaluating an MCP server for inclusion or continued visibility in our directory, we consider several signals. The exact depth of review can vary depending on the type of project, the information available, and whether the project is undergoing a deeper editorial review.
Our evaluation may consider:
- Identity and source: Whether the project can be traced to an identifiable repository, developer, organization, or other original source.
- Documentation: Whether useful documentation, installation instructions, configuration information, or usage examples are available.
- Purpose and functionality: What the server is designed to do and what tools, resources, prompts, or other MCP capabilities it exposes.
- Installation and configuration: Where practical, whether the documented installation or configuration process is understandable and consistent with the information presented by the project.
- Project activity: Available signals such as recent releases, repository activity, documentation updates, or other evidence that helps describe the current state of a project.
- Compatibility information: Supported clients, transports, runtimes, operating environments, or other compatibility information when it is documented by the project.
- Security considerations: Permissions, credentials, external services, network access, local system access, or other considerations that may be relevant to users connecting an MCP server to their environment.
Discovery and Sources
MCP servers may reach our discovery systems through several routes. These can include public repositories, the official MCP ecosystem, developer submissions, project documentation, public announcements, and automated discovery.
We may use automated systems to identify and collect information at scale. Automated discovery allows us to keep up with a rapidly expanding ecosystem, but discovery is not the same as verification.
Whenever practical, we prefer to associate a listing with its original project repository, official documentation, or another first-party source. This gives users a direct path to the information maintained by the project itself.
Documentation and Technical Review
Documentation is an important part of evaluating an MCP server. Clear documentation helps users understand what a server does, what permissions or credentials it requires, how it is configured, and how it communicates with an MCP client.
Where technical information is available, we compare the information presented in a Lord of Claude listing with the project's available documentation and source material.
Depending on the project and the review being performed, we may examine information such as:
- Available tools and their documented purposes
- Resources and prompts exposed by the server
- Installation and configuration requirements
- Environment variables and required credentials
- Supported transports and deployment models
- Runtime and dependency requirements
- Links to source code and documentation
The MCP protocol supports different server capabilities and deployment patterns. We therefore avoid treating every MCP server as technically identical and evaluate projects according to the functionality and architecture they document.
Security and Permission Considerations
Security is an important consideration when working with MCP servers. Depending on their design, servers may interact with local files, external APIs, databases, websites, cloud services, or other systems.
Our listings may highlight relevant security or permission considerations when those details are identifiable from the project's documentation or implementation.
Users should always review the permissions, credentials, source code, dependencies, configuration, and documentation of an MCP server before connecting it to sensitive systems or data.
Inclusion in the Lord of Claude directory is not a security certification, vulnerability assessment, or guarantee that a server is safe for every environment.
What “Verified” Means
Lord of Claude may use verification indicators when a listing has undergone the corresponding review process.
A verification indicator is intended to communicate that specific information associated with the listing has been checked against available project sources or review criteria at a particular point in time.
Verification does not mean that Lord of Claude endorses the project, guarantees its security, guarantees future availability, or certifies every line of its code.
Because third-party software can change after a review, verification should be understood as a time-sensitive editorial signal rather than a permanent certification.
Automated Discovery vs. Editorial Review
Not every server discovered by our systems receives the same level of manual review.
We distinguish between information that has been automatically discovered or imported and information that has undergone additional editorial review. Where appropriate, our directory may display different statuses or metadata to help communicate this distinction.
This distinction allows us to maintain broad coverage of the MCP ecosystem without representing every automatically discovered project as individually tested or manually verified.
Project Activity and Maintenance
An MCP server that was useful yesterday may become outdated tomorrow. We therefore consider available project activity when maintaining directory information.
Signals may include recent releases, repository changes, updated documentation, issue activity, package versions, or other publicly available information.
Activity signals are not treated as a guarantee of software quality. They are used as contextual information to help describe the current state of a project.
Keeping Listings Current
We may update MCP server listings when new information becomes available, a project changes, documentation is updated, or a previously available resource becomes inaccessible.
Where appropriate, listings may include information such as project versions, repository links, documentation links, supported capabilities, and review or update dates.
If a project is no longer maintained, its source disappears, or important information can no longer be confirmed, we may update, de-emphasize, or remove the corresponding listing.
Developer and Project Submissions
Developers and project maintainers can submit MCP servers for consideration. A submission provides information for our discovery and review process but does not guarantee publication, verification, ranking, or editorial coverage.
Submitted information may be checked against publicly available project information before it is used in a listing. We may request clarification or additional documentation when necessary.
Paid placement, sponsorship, or other commercial arrangements should not be represented as technical verification or independent editorial endorsement.
What Our Review Does Not Guarantee
No directory review can eliminate all risks associated with third-party software. Lord of Claude does not guarantee that an MCP server:
- Is free from security vulnerabilities
- Is free from malicious or unwanted behavior
- Will remain available or maintained
- Will work with every MCP client or environment
- Will meet a particular production, compliance, or security requirement
- Will remain consistent after future updates
Users should perform their own technical and security assessment before deploying third-party software, particularly when an MCP server can access sensitive information, credentials, local systems, databases, or external services.
Reporting Incorrect Information
If you discover incorrect, outdated, misleading, or missing information in an MCP server listing, we encourage you to report it.
Please provide the affected page, describe the issue, and include a reliable source or other evidence where possible.
You can report issues through our Contact page.
Our Goal
The purpose of this methodology is not to declare one MCP server universally better than another. It is to provide developers with useful, structured, and transparent information that makes it easier to discover and evaluate MCP software.
As the Model Context Protocol ecosystem evolves, we expect our review criteria and processes to evolve with it.
Our goal is simple: make MCP server discovery more useful, transparent, and trustworthy for the developers building with AI.
This methodology may be updated as the MCP ecosystem, technical standards, and Lord of Claude's review processes evolve.