Skip to content
Back to search

mcpsvr

Discover Exceptional MCP 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/nanbingxyz/mcpsvr 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/nanbingxyz/mcpsvr'

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/nanbingxyz--mcpsvr/badge.svg)](/listings/nanbingxyz--mcpsvr)

HTML

<a href="/listings/nanbingxyz--mcpsvr"><img src="/api/listings/nanbingxyz--mcpsvr/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.

npm install

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 · 147 lines

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

  1. <p align="center">
  2. <img src="./public/logo.png" width="68" alt="MCPSvr logo" />
  3. </p>
  4. # MCPSvr
  5. > A community-driven directory for discovering, reviewing, and contributing MCP servers.
  6. <p align="center">
  7. <a href="https://github.com/nanbingxyz/mcpsvr/stargazers"><img src="https://img.shields.io/github/stars/nanbingxyz/mcpsvr?style=flat-square" alt="GitHub stars" /></a>
  8. <a href="https://github.com/nanbingxyz/mcpsvr/commits/master"><img src="https://img.shields.io/github/last-commit/nanbingxyz/mcpsvr?style=flat-square" alt="Last commit" /></a>
  9. <img src="https://img.shields.io/badge/Next.js-15-black?style=flat-square" alt="Next.js 15" />
  10. <img src="https://img.shields.io/badge/MCP-community%20directory-6f42c1?style=flat-square" alt="Community directory" />
  11. </p>
  12. [中文说明](./README_cn.md)
  13. MCPSvr is a lightweight web directory for Model Context Protocol servers. It helps developers browse available servers, understand how each one is configured, and contribute new entries through pull requests.
  14. The repository centers on a curated `public/servers.json` registry, so MCP clients such as [5ire](http://github.com/nanbingxyz/5ire) can install and run supported servers directly.
  15. https://github.com/user-attachments/assets/3d1ec8db-2041-4f2d-b72c-eb8ae17ab31c
  16. ## Table of Contents
  17. - [Why MCPSvr](#why-mcpsvr)
  18. - [What You Can Do](#what-you-can-do)
  19. - [Project Structure](#project-structure)
  20. - [Run Locally](#run-locally)
  21. - [How to Add a Server](#how-to-add-a-server)
  22. - [Server Schema](#server-schema)
  23. - [Parameter Placeholders](#parameter-placeholders)
  24. - [Contribution Notes](#contribution-notes)
  25. ## Why MCPSvr
  26. MCP servers are growing fast, but good discovery is still fragmented. MCPSvr gives the ecosystem a simple shared registry with enough metadata for humans to evaluate tools and for clients to automate setup.
  27. ## What You Can Do
  28. - Discover MCP servers from a single browsable directory
  29. - Review runtime commands, arguments, environment variables, and homepage links
  30. - Contribute new servers or improve existing metadata via pull requests
  31. - Reuse the registry in MCP clients that support direct installation
  32. ## Project Structure
  33. ```text
  34. .
  35. ├── app/ # Next.js app router pages
  36. ├── components/ # Reusable UI components
  37. ├── lib/ # Utility helpers
  38. ├── public/
  39. │ ├── logo.png
  40. │ └── servers.json # Central MCP server registry
  41. └── README_cn.md # Chinese README
  42. ```
  43. ## Run Locally
  44. ### Prerequisites
  45. - Node.js 18+
  46. - npm (or another package manager compatible with `package-lock.json`)
  47. ### Install
  48. ```bash
  49. npm install
  50. ```
  51. ### Start the development server
  52. ```bash
  53. npm run dev
  54. ```
  55. Then open `http://localhost:3000`.
  56. ### Build for production
  57. ```bash
  58. npm run build
  59. npm run start
  60. ```
  61. ## How to Add a Server
  62. All registered MCP servers are maintained in `public/servers.json`. To contribute a new entry:
  63. 1. Fork the repository
  64. 2. Add or update a server object in `public/servers.json`
  65. 3. Keep keys consistently ordered
  66. 4. Open a pull request with links to the project homepage or docs
  67. ## Server Schema
  68. ```json
  69. {
  70. "name": "Server Identifier",
  71. "key": "Unique alphanumeric identifier",
  72. "description": "Concise implementation overview",
  73. "command": "Execution environment specifier (for example uvx, npx, python, node)",
  74. "args": [
  75. "Required runtime arguments"
  76. ],
  77. "env": {
  78. "ENVIRONMENT_VARIABLE": "Value assignment"
  79. },
  80. "homepage": "Official documentation URL"
  81. }
  82. ```
  83. ### Field Guidelines
  84. - `key` must be unique, alphanumeric, and start with a letter
  85. - `name` is optional and falls back to `key` when omitted
  86. - `env` and `homepage` are optional but strongly recommended
  87. - Keep descriptions short and practical so clients can display them cleanly
  88. ## Parameter Placeholders
  89. When a server needs user-provided input, use the placeholder format below:
  90. ```text
  91. {{paramName@paramType::paramDescription}}
  92. ```
  93. Example:
  94. ```json
  95. {
  96. "name": "File System Access Control",
  97. "key": "FileSystem",
  98. "command": "npx",
  99. "description": "Enforces directory-level operation restrictions through specified arguments",
  100. "args": [
  101. "-y",
  102. "@modelcontextprotocol/server-filesystem",
  103. "{{dirs@list::directories you are about to access, include trailing slash}}"
  104. ],
  105. "homepage": "https://github.com/modelcontextprotocol/servers"
  106. }
  107. ```
  108. Supported placeholder types include `string`, `list`, and `number`.
  109. ## Contribution Notes
  110. - Prefer accurate metadata over marketing copy
  111. - Double-check command arguments before submitting
  112. - Include a homepage or docs link whenever possible
  113. - If you add a new field in the future, keep the schema backwards compatible for downstream clients

Ratings and comments

Sign in to rate this skill.

Sign in

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