This repository contains no code that runs on your machine -- it is a list. The security risk it carries is different, and worth being explicit about.
An MCP server runs as a trusted extension of your AI assistant. Once configured, it can read files, hold API credentials, and act on your behalf. Installing one is closer to installing a shell plugin than to adding a library.
So an entry on this list is an implicit recommendation, and a malicious entry is a supply-chain attack. Every submission is checked for a detectable licence, a real implementation, active maintenance, and an unarchived, non-forked source -- see CONTRIBUTING.md. Those checks catch spam and abandonware. They do not prove any listed server is safe.
Review any MCP server's source and requested permissions before you configure it. A green check on this list is not an audit.
If a server on this list exfiltrates data, takes an undisclosed action, ships a malicious postinstall step, or has had its repository or package taken over, report it privately:
- Use GitHub private vulnerability reporting, or
- email sg85207@gmail.com with
[awesome-mcp-servers]in the subject.
Include the entry name, the repository or package URL, and what you observed. A proof of concept helps but is not required.
Please do not open a public issue first. A public report tells everyone reading the list where the problem is before it can be removed.
- Within 72 hours -- acknowledgement.
- Confirmed -- the entry is removed from
README.mdimmediately, and the commit message states why. - Unclear -- the maintainer contacts the project's author for a response before acting.
- Not reproducible -- you get an explanation of what was checked.
Credit is given in the removal commit unless you ask otherwise.
For issues in this repository's own tooling -- a workflow with an over-broad token, an injection in scripts/, a leaked secret -- use the same private channels above.
- Vulnerabilities in a listed third-party server that are not malicious behaviour. Report those to that project, then open an issue here if the project is unresponsive and the entry should be removed.
- Broken or dead links. Open a normal issue, or wait for the monthly health report.
- Disagreement about whether an entry deserves to be listed. That is a curation question -- open an issue.