MCP Radar

MCP Radar is a public discovery and evaluation directory for Model Context Protocol servers. Its purpose is not to tell developers that every indexed server is safe or production-ready. Instead, it helps them create a more defensible shortlist by exposing public maintenance, adoption, lifecycle, and usability signals before they install anything.

Start with the maintenance question

The MCP ecosystem changes quickly. A server may still appear in a directory even when its repository has slowed down, its package is difficult to run, or its maintainers have stopped responding. MCP Radar places an active, stale, or abandoned lifecycle label beside each indexed entry so readers can see whether a project appears to be maintained before investing time in setup.

Each listing also includes a TrustScore derived from public signals associated with the official registry, GitHub, and npm. The score is a maintenance and adoption screening signal. It is not a security audit, user review score, or guarantee of production readiness.

A practical shortlist workflow

Developers can begin with a use-case or category page, remove abandoned or unclear candidates, compare the remaining entries, and then open the underlying repository and package evidence. The public leaderboard and radar views provide additional ways to notice actively maintained projects or meaningful changes. Methodology pages explain how the score is constructed and where the data has limitations.

A reasonable workflow is:

1. Search for the integration or use case you need.

2. Check the lifecycle label and most recent public evidence.

3. Compare maintenance and adoption signals across candidates.

4. Open the repository, package, permissions, and deployment instructions.

5. Test the chosen server in an isolated environment before production use.

MCP Radar supports the first three steps and links readers toward the evidence needed for the remaining review.

Who should use it

The directory is intended for developers, AI-agent builders, engineering leads, and technical researchers comparing MCP servers. It is most useful when several projects offer similar capabilities but differ in maintenance history, adoption, packaging, or transparency.

It is not a replacement for source-code review, permission analysis, network inspection, or sandbox testing. A healthy maintenance signal can reduce research time, but it cannot prove that a server is secure or appropriate for a particular environment.

Public access and transparency

When verified on August 1, 2026, the directory, methodology, leaderboard, guides, and implementation repository were publicly accessible. The project exposes its methodology so readers can understand the purpose and boundary of TrustScore rather than treating it as an unexplained ranking.

Quick answers

What makes MCP Radar different from a plain directory?

It combines use-case discovery with lifecycle labels and public-data maintenance and adoption signals.

Does it certify MCP servers as secure?

No. It provides screening evidence only. Security and production suitability still require independent verification.

Can users inspect the implementation?

Yes. MCP Radar links to a public GitHub repository.

How often should the evidence be rechecked?

The site states that data is updated daily, but developers should still reopen the linked repository and package immediately before installation.

Last verified: August 1, 2026. Refresh due: October 30, 2026.

Explore more artificial intelligence tools on EarlyHunt.