TrustedMCP

MCP开发工具

提供方 未标注

开发工具 HTTP · 远程 API Key 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

Ask your agent about any MCP server and get an A-D grade from public signals (login, upkeep, known CVEs, connection) plus better-graded alternatives.

一句话选型结论

按资料字段整理

TrustedMCP 属于开发工具类 MCP 服务器,HTTP · 远程,API Key,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式HTTP · 远程 鉴权API Key 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

Development

安装与配置

HTTP · 远程 API Key
连远程 HTTPS 端点,通常为 Streamable HTTP
npx add-mcp 'https://trustedmcp.io/mcp'

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
TrustedMCP当前 未标注 HTTP · 远程 支持远程部署 有 2026-11-20
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类开发工具本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

6.2 KB
来自项目仓库与上游目录的原文,未做删改

TrustedMCP MCP server

Give your agent the TrustedMCP grades. Ask it "is this MCP server any good?" or "check my MCP setup", and it answers with an A to D grade per server, what to fix first, and better-graded servers in the same category.

Each grade is an assessment from public signals: login, upkeep, known CVEs and how the server connects. Use it as a starting point for your own review. It is not an audit of the code. How we grade.

Tools

Tool What it does
lookup_server One server by name, npm or PyPI package, Docker image, URL, GitHub repo or launch command: its grade, the four checks, what to fix first, its TrustedMCP page.
check_config Every server in your MCP config. With no arguments it reads the usual config files for Claude Desktop, Claude Code, Cursor, VS Code and Windsurf. You can also pass one client, a path or the config JSON.
find_alternatives Graded servers by category, search term or minimum grade. Or instead_of a server, for better-graded ones in its category.
registry_lookup An official MCP Registry entry: packages, remotes, TrustedMCP grade if any, and reported security issues (GHSA/CVE, and whether the listed version is affected).

All four tools only read data.

Get a key

Tool calls need a free API key. Sign up with your email at trustedmcp.io/developers. The server still starts and lists its tools without one, but every tool call returns an error that tells you to add a key.

Keys are scoped. A key can have any of these three scopes:

Scope Covers
servers:read lookup_server and find_alternatives
config:check check_config
registry:read registry_lookup

registry_lookup also falls back to a server search when you give it a package name or search term instead of a registry name, so give the key servers:read as well. If a key lacks the scope a tool needs, the tool says which scope is missing. You can revoke or rotate a key on the same page. A revoked or invalid key is rejected, and the tool tells you to get a new one.

Install

Hosted (no install)

TrustedMCP also runs as a hosted server at https://trustedmcp.io/mcp. It has the same four tools. Nothing to install, no Node.js needed. Send your key as a Bearer token.

Claude Code:```sh
claude mcp add --transport http trustedmcp https://trustedmcp.io/mcp --header "Authorization: Bearer YOUR_KEY"


Cursor (`~/.cursor/mcp.json`):```json
{
  "mcpServers": {
    "trustedmcp": {
      "url": "https://trustedmcp.io/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

VS Code (.vscode/mcp.json):```json
{
"servers": {
"trustedmcp": {
"type": "http",
"url": "https://trustedmcp.io/mcp",
"headers": { "Authorization": "Bearer YOUR_KEY" }
}
}
}


The hosted server can't read files on your machine, so `check_config` needs your config pasted in as the `config` argument. The npx version below reads your config files locally.

**Run locally with npx**

Needs Node.js 18 or later.

**Claude Code**```sh
claude mcp add trustedmcp -e TRUSTEDMCP_API_KEY=YOUR_KEY -- npx -y trustedmcp mcp

Claude Desktop, Cursor, Windsurf (claude_desktop_config.json, ~/.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json)```json
{
"mcpServers": {
"trustedmcp": {
"command": "npx",
"args": ["-y", "trustedmcp", "mcp"],
"env": { "TRUSTEDMCP_API_KEY": "YOUR_KEY" }
}
}
}


**VS Code** (`.vscode/mcp.json`)```json
{
  "servers": {
    "trustedmcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "trustedmcp", "mcp"],
      "env": { "TRUSTEDMCP_API_KEY": "YOUR_KEY" }
    }
  }
}

Then ask: "Check my MCP config with TrustedMCP", or "What grade does @playwright/mcp get, and is there something better?"

What leaves your machine

With the hosted endpoint, whatever you pass to a tool is sent to trustedmcp.io. The rest of this section is about the npx version.

check_config reads your config file on your machine. It sends TrustedMCP only:

  • each server's name in your config, and
  • the package names (npm:@playwright/mcp), image names (oci:ghcr.io/github/github-mcp-server) and server URLs it found, without query strings.

Environment variables, headers, tokens, other arguments and file paths stay on your machine. A server that runs a local file (node ./server.js) is not sent at all; the tool tells you it can't be looked up. The API doesn't store what it receives. The code that builds those identifiers is in src/identifiers.ts and src/config.ts.

Its own grade

TrustedMCP grades this server with the same rubric as every other listing: A, with 3 of 4 checks at full marks. It loses points on upkeep, because it is new and has one maintainer, so pin the version you tested. See its listing and the setup guide.

Settings

Variable Default What it does
TRUSTEDMCP_API_KEY none Required for tool calls. Free key from trustedmcp.io/developers, with the scopes servers:read, config:check and registry:read.
TRUSTEDMCP_API_URL https://trustedmcp.io/api/v1 API base URL, for testing against another copy.

The API

The server is a thin client for the free TrustedMCP JSON API (https://trustedmcp.io/api/v1: /servers, /servers/{slug}, /lookup, /check, /registry/{name}, /categories). Docs and terms: trustedmcp.io/developers. Where you show a grade, credit "Grades by TrustedMCP" and link to the server's page.

Develop```sh

npm install
npm test # vitest
npm run build # tsc to dist/
TRUSTEDMCP_API_URL=http://127.0.0.1:8000/api/v1 node dist/cli.js mcp


Tool calls need a key even when you point `TRUSTEDMCP_API_URL` at a local copy.

Release (maintainers): bump `version` in `package.json` and both `version` fields in `server.json` (top level and `packages[0]`), `npm publish`, then `node scripts/publish-registry.mjs` to publish the same version to the official MCP Registry. That script needs the domain key for `io.trustedmcp/*`; it never leaves the maintainer's machine.

Use it as a library:```ts
import { createServer, TrustedMcpApi } from 'trustedmcp';

Missing a server?

If a server you use has no grade, ask for one.

License

MIT

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
TrustedMCP 怎么安装?

在客户端按下面的安装命令接入:npx add-mcp 'https://trustedmcp.io/mcp'。装完在客户端配置里引用同一个包或端点。

TrustedMCP 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

TrustedMCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

TrustedMCP 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

TrustedMCP 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

TrustedMCP 能提供哪些能力?

资料显示能力标签包括 Development。具体工具清单以官方文档为准。

TrustedMCP 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

TrustedMCP 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。