Freshness-first trust layer for MCP servers
Find MCP servers that are alive, maintained, and worth using.
MCP Signal starts with the official MCP registry and adds the context you need to evaluate a server: when it was last checked, recent project activity, and whether it appears to be official, community-built, or unclear.
Public launch home: mcpsignal.dev
Why this exists
A long list is not the same as a trusted directory.
Finding an MCP server is easy. Deciding whether it is current enough to try takes more work.
A listing can exist long after the project has gone quiet. Similar servers can be hard to compare. Teams may need to know who maintains a project before it enters a workflow.
MCP Signal puts those first checks in one place.
Core listing signals
The first questions, answered on the listing.
Status
See MCP Signal's current status label: alive, stale, or dead.
Last verified
See when MCP Signal last checked the listing.
Project activity
Review recent GitHub activity and release information when it is available.
Project context
See whether a server appears to be official, community-built, or unclear.
Spend less time opening tabs just to decide where to start.
Listing preview
One listing should make the first evaluation easier.
Use the listing to review the server's status, last verified time, project context, and source links before you add it to your workflow.
A preview of the fields every listing shows: status, last verified, project context, and source links.
What the MVP should make obvious
- Start with freshness and maintenance signals, not marketing claims.
- Keep the first review in one place before the team opens ten tabs.
- Give maintainers a clearer way to identify and explain the project.
Who it serves
For people choosing, publishing, and reviewing MCP servers.
For builders
Find useful servers without sorting through projects that look abandoned.
For maintainers
Give your server a clear, current listing that people can evaluate.
For teams
Start with a better view of the servers under consideration before a team adopts them.
Maintainer offer
Maintain a server? Get the details right.
MCP Signal offers early listing options for maintainers who want a claimed, more complete project page. Paid options can improve how a listing is presented and identified. They do not change status, freshness, or other trust signals.
Paid listings do not change trust signals.
Team workflow
Evaluating MCP servers for a team?
Tell us what your team is reviewing. We are collecting early requests for a monitoring service built around a team's MCP shortlist, public maintenance signals, and change notes.
FAQ
Common questions
Is MCP Signal another MCP directory?
The directory is the starting point. MCP Signal adds freshness and maintenance context so visitors can make a more informed first call.
Do paid listings change a server status?
No. Payment can change listing ownership, presentation, and approved visibility options. It does not change trust signals.
Is a verified listing a security certification?
No. Verification confirms the public listing details and publisher context described on the listing. It is not a security audit, compliance attestation, or guarantee that a server is right for every use.
How is status determined?
MCP Signal uses available registry and project signals to assign a current status label. The listing shows when it was last checked. Status is a practical indicator, not a guarantee.
Public MVP path
Choose MCP servers with more context.
Browse the directory if you are evaluating tools. Get listed if you maintain one. Request team monitoring if your team needs a closer look at a shortlist.