MCP Radar is a public, use-case directory that helps developers discover and investigate Model Context Protocol servers. The project is designed for a practical problem: a server can appear in a directory while its repository is stale, its package is difficult to run, or its maintenance status is unclear. MCP Radar puts those signals next to the listing so that users can narrow the field before spending time on installation and testing.
## What it does
MCP Radar organizes servers by use case and gives every indexed entry a visible lifecycle label: active, stale, or abandoned. It also provides a TrustScore built from public registry, GitHub, and npm signals. The score is intended as a maintenance and adoption screening signal. It is not a security certification, a user rating, or a guarantee that a server is suitable for production.
The site includes searchable listings, category pages, a leaderboard, a weekly radar view, comparison tools, and practical guides. The public methodology explains the score dimensions and their limits, allowing readers to inspect the evidence instead of relying on an unexplained ranking.
## Who it is for
MCP Radar is useful for developers, engineering leads, AI-agent builders, and technical researchers who need to compare MCP servers before connecting them to a client or workflow. It is especially helpful when several projects promise a similar integration and the main question is which ones are still maintained.
The directory is not a replacement for a security review. Users should still examine source code, requested permissions, package ownership, network behavior, and deployment requirements before installation.
## Pricing and access
The directory, methodology, leaderboard, and public repository were accessible without a paid account when checked on August 1, 2026. The site is open for browsing, and the implementation is available in a public GitHub repository. This listing does not make a claim about future pricing or access conditions.
## Key features
- Browse MCP servers by use case and category.
- See active, stale, or abandoned lifecycle labels.
- Compare transparent maintenance and adoption signals.
- Review a public TrustScore methodology and its limitations.
- Use leaderboard, radar, comparison, and guide pages for deeper investigation.
- Inspect the open-source repository and published data approach.
## Quick answers
### Does MCP Radar certify that a server is secure?
No. TrustScore summarizes public maintenance and adoption evidence. It does not certify security or production readiness.
### Where does the evidence come from?
The published methodology identifies the official registry, GitHub, and npm as core public signal sources.
### How current is the directory?
The official site states that its data is updated daily. Because ecosystem data changes, users should also verify the linked repository and package before installing a server.
### Is MCP Radar open source?
Yes. The project links to a public GitHub repository where the implementation can be inspected.
Last verified: August 1, 2026. Refresh due: October 30, 2026.
Explore more artificial intelligence tools on IndieHunt.
