Skip to content
Back to search

servers

Model Context Protocol Servers

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/modelcontextprotocol/servers with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/modelcontextprotocol/servers'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/modelcontextprotocol--servers/badge.svg)](/listings/modelcontextprotocol--servers)

HTML

<a href="/listings/modelcontextprotocol--servers"><img src="/api/listings/modelcontextprotocol--servers/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Using MCP Servers in this Repository

TypeScript-based servers in this repository can be used directly with `npx`.

For example, this will start the [Memory](src/memory) server:

npx -y @modelcontextprotocol/server-memory

Python-based servers in this repository can be used directly with [`uvx`](https://docs.astral.sh/uv/concepts/tools/) or [`pip`](https://pypi.org/project/pip/). `uvx` is recommended for ease of use and setup.

For example, this will start the [Git](src/git) server:

# With uvx
uvx mcp-server-git

# With pip
pip install mcp-server-git
python -m mcp_server_git

Follow [these](https://docs.astral.sh/uv/getting-started/installation/) instructions to install `uv` / `uvx` and [these](https://pip.pypa.io/en/stable/installation/) to install `pip`.

Using an MCP Client

However, running a server on its own isn't very useful, and should instead be configured into an MCP client. For example, here's the Claude Desktop configuration to use the above server:

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-memory"]
    }
  }
}

On Windows, wrap `npx` with `cmd /c`:

{
  "mcpServers": {
    "memory": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-memory"]
    }
  }
}

Additional examples of using the Claude Desktop as an MCP client might look like:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/allowed/files"]
    },
    "git": {
      "command": "uvx",
      "args": ["mcp-server-git", "--repository", "path/to/git/repo"]
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    },
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres", "postgresql://localhost/mydb"]
    }
  }
}

On Windows, apply the same wrapper to each `npx`-based entry above by changing `"command"` to `"cmd"` and prepending `"/c", "npx"` to the existing `args`. Leave `uvx` entries unchanged.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 187 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Model Context Protocol servers
  2. This repository is a collection of *reference implementations* for the [Model Context Protocol](https://modelcontextprotocol.io/) (MCP), as well as references to community-built servers and additional resources.
  3. > [!IMPORTANT]
  4. > If you are looking for a list of MCP servers, you can browse published servers on [the MCP Registry](https://registry.modelcontextprotocol.io/). The repository served by this README is dedicated to housing just the small number of reference servers maintained by the MCP steering group.
  5. > [!WARNING]
  6. > The servers in this repository are intended as **reference implementations** to demonstrate MCP features and SDK usage. They are meant to serve as educational examples for developers building their own MCP servers, not as production-ready solutions. Developers should evaluate their own security requirements and implement appropriate safeguards based on their specific threat model and use case.
  7. The servers in this repository showcase the versatility and extensibility of MCP, demonstrating how it can be used to give Large Language Models (LLMs) secure, controlled access to tools and data sources.
  8. Typically, each MCP server is implemented with an MCP SDK:
  9. - [C# MCP SDK](https://github.com/modelcontextprotocol/csharp-sdk)
  10. - [Go MCP SDK](https://github.com/modelcontextprotocol/go-sdk)
  11. - [Java MCP SDK](https://github.com/modelcontextprotocol/java-sdk)
  12. - [Kotlin MCP SDK](https://github.com/modelcontextprotocol/kotlin-sdk)
  13. - [PHP MCP SDK](https://github.com/modelcontextprotocol/php-sdk)
  14. - [Python MCP SDK](https://github.com/modelcontextprotocol/python-sdk)
  15. - [Ruby MCP SDK](https://github.com/modelcontextprotocol/ruby-sdk)
  16. - [Rust MCP SDK](https://github.com/modelcontextprotocol/rust-sdk)
  17. - [Swift MCP SDK](https://github.com/modelcontextprotocol/swift-sdk)
  18. - [TypeScript MCP SDK](https://github.com/modelcontextprotocol/typescript-sdk)
  19. ## 🌟 Reference Servers
  20. These servers aim to demonstrate MCP features and the official SDKs.
  21. - **[Everything](src/everything)** - Reference / test server with prompts, resources, and tools.
  22. - **[Fetch](src/fetch)** - Web content fetching and conversion for efficient LLM usage.
  23. - **[Filesystem](src/filesystem)** - Secure file operations with configurable access controls.
  24. - **[Git](src/git)** - Tools to read, search, and manipulate Git repositories.
  25. - **[Memory](src/memory)** - Knowledge graph-based persistent memory system.
  26. - **[Sequential Thinking](src/sequentialthinking)** - Dynamic and reflective problem-solving through thought sequences.
  27. - **[Time](src/time)** - Time and timezone conversion capabilities.
  28. ### Archived
  29. The following reference servers are now archived and can be found at [servers-archived](https://github.com/modelcontextprotocol/servers-archived).
  30. - **[AWS KB Retrieval](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/aws-kb-retrieval-server)** - Retrieval from AWS Knowledge Base using Bedrock Agent Runtime.
  31. - **[Brave Search](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/brave-search)** - Web and local search using Brave's Search API. Has been replaced by the [official server](https://github.com/brave/brave-search-mcp-server) ([`@brave/brave-search-mcp-server`](https://www.npmjs.com/package/@brave/brave-search-mcp-server)).
  32. - **[EverArt](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/everart)** - AI image generation using various models.
  33. - **[GitHub](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/github)** - Repository management, file operations, and GitHub API integration.
  34. - **[GitLab](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/gitlab)** - GitLab API, enabling project management.
  35. - **[Google Drive](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/gdrive)** - File access and search capabilities for Google Drive.
  36. - **[Google Maps](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/google-maps)** - Location services, directions, and place details.
  37. - **[PostgreSQL](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/postgres)** - Read-only database access with schema inspection.
  38. - **[Puppeteer](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/puppeteer)** - Browser automation and web scraping.
  39. - **[Redis](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/redis)** - Interact with Redis key-value stores.
  40. - **[Sentry](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/sentry)** - Retrieving and analyzing issues from Sentry.io.
  41. - **[Slack](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/slack)** - Channel management and messaging capabilities. Now maintained by [Zencoder](https://github.com/zencoderai/slack-mcp-server)
  42. - **[SQLite](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/sqlite)** - Database interaction and business intelligence capabilities.
  43. ## 🚀 Getting Started
  44. ### Using MCP Servers in this Repository
  45. TypeScript-based servers in this repository can be started with `npx`.
  46. For example, this will start the [Memory](src/memory) server:
  47. ```sh
  48. npx -y @modelcontextprotocol/server-memory
  49. ```
  50. Python-based servers in this repository can be started with [`uvx`](https://docs.astral.sh/uv/concepts/tools/) or [`pip`](https://pypi.org/project/pip/). `uvx` is recommended for ease of use and setup.
  51. For example, this will start the [Git](src/git) server:
  52. ```sh
  53. # With uvx
  54. uvx mcp-server-git
  55. # With pip
  56. pip install mcp-server-git
  57. python -m mcp_server_git
  58. ```
  59. Follow [these](https://docs.astral.sh/uv/getting-started/installation/) instructions to install `uv` / `uvx` and [these](https://pip.pypa.io/en/stable/installation/) to install `pip`.
  60. ### Using an MCP Client
  61. However, running a server on its own isn't very useful, and should instead be configured into an MCP client. For example, here's the Claude Desktop configuration to use the above server:
  62. ```json
  63. {
  64. "mcpServers": {
  65. "memory": {
  66. "command": "npx",
  67. "args": ["-y", "@modelcontextprotocol/server-memory"]
  68. }
  69. }
  70. }
  71. ```
  72. On Windows, wrap `npx` with `cmd /c`:
  73. ```json
  74. {
  75. "mcpServers": {
  76. "memory": {
  77. "command": "cmd",
  78. "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-memory"]
  79. }
  80. }
  81. }
  82. ```
  83. Additional examples of using the Claude Desktop as an MCP client might look like:
  84. ```json
  85. {
  86. "mcpServers": {
  87. "filesystem": {
  88. "command": "npx",
  89. "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/allowed/files"]
  90. },
  91. "git": {
  92. "command": "uvx",
  93. "args": ["mcp-server-git", "--repository", "path/to/git/repo"]
  94. },
  95. "fetch": {
  96. "command": "uvx",
  97. "args": ["mcp-server-fetch"]
  98. }
  99. }
  100. }
  101. ```
  102. On Windows, apply the same wrapper to the `npx`-based `filesystem` entry above by changing its `"command"` to `"cmd"` and prepending `"/c", "npx"` to its existing `args`. Leave the `uvx` entries unchanged.
  103. ### Transports: stdio and Streamable HTTP
  104. An MCP server talks to its client over a **transport**. The protocol defines two standard ones, and they run very differently:
  105. | Transport | How the server runs | How a client reaches it |
  106. |---|---|---|
  107. | **stdio** | The client launches the server as a subprocess and talks to it over the process's stdin and stdout. The server opens no port. | A `command` and `args` in the client's configuration, as in the examples above |
  108. | **Streamable HTTP** | The server runs on its own as an HTTP service, and can serve many clients | A URL, such as `http://localhost:3001/mcp` |
  109. **Every server in this repository serves stdio by default, and every one can also serve Streamable HTTP** on `http://127.0.0.1:3001/mcp` (set `PORT` and `HOST` to move it): [Everything](src/everything) with its `streamableHttp` argument (its README also covers its deprecated HTTP+SSE transport), and the others with `--transport streamable-http`, as each server's README shows. Started without one, a server uses stdio, so when you run `uvx mcp-server-git` or `npx -y @modelcontextprotocol/server-memory` in a terminal, it opens no port, prints at most a one-line startup notice, and then appears to hang. That is expected: it is waiting for a client to send it messages on stdin. You do not normally start a stdio server yourself; your MCP client starts it from its configuration and stops it when it is done.
  110. To try a server without setting up a client, use the [MCP Inspector](https://github.com/modelcontextprotocol/inspector). Given a stdio server's command, it launches the server for you and lets you browse and call its tools; given a URL, it connects to a running Streamable HTTP server:
  111. ```sh
  112. # A stdio server: the Inspector launches it
  113. npx @modelcontextprotocol/inspector uvx mcp-server-git
  114. # A Streamable HTTP server: start it first, then connect to its URL
  115. npx @modelcontextprotocol/server-everything streamableHttp # or: uvx mcp-server-time --transport streamable-http
  116. npx @modelcontextprotocol/inspector --transport http --server-url http://localhost:3001/mcp
  117. ```
  118. For more, see the [transport layer](https://modelcontextprotocol.io/docs/learn/architecture#transport-layer) in the MCP architecture overview, and [Transports](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports) in the specification.
  119. ## 🛠️ Creating Your Own Server
  120. Interested in creating your own MCP server? Visit the official documentation at [modelcontextprotocol.io](https://modelcontextprotocol.io/introduction) for comprehensive guides, best practices, and technical details on implementing MCP servers.
  121. ## 📚 Learn More
  122. See [ADDITIONAL.md](ADDITIONAL.md) for a curated list of frameworks and resources that simplify building MCP servers and clients.
  123. ## 🤝 Contributing
  124. See [CONTRIBUTING.md](CONTRIBUTING.md) for information about contributing to this repository.
  125. ## 📦 Releasing
  126. See [RELEASING.md](RELEASING.md) for how packages are published (OIDC trusted publishing from CI — no registry tokens) and how to retry a failed publish.
  127. ## 🔒 Security
  128. See [SECURITY.md](SECURITY.md) for reporting security vulnerabilities.
  129. ## 📜 License
  130. This project is licensed under the Apache License, Version 2.0 for new contributions, with existing code under MIT - see the [LICENSE](LICENSE) file for details.
  131. ## 💬 Community
  132. - [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions)
  133. ## ⭐ Support
  134. If you find MCP servers useful, please consider starring the repository and contributing new servers or improvements!
  135. ---
  136. Managed by Anthropic, but built together with the community. The Model Context Protocol is open source and we encourage everyone to contribute their own servers and improvements!

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.