Fidensa
概览
作者提供的说明(英文原文)
Independent AI certification authority. Trust scores, search, comparison, and verification.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i非常新↓ 68/周 · ★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: stdio
- 分类: 搜索与 AI 记忆
- 你需要填写:FIDENSA_API_KEY
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 需要你自己填写:
FIDENSA_API_KEY
标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
- npm已安装 Node.js(用于 npx 命令)
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"fidensa": {
"command": "npx",
"args": [
"-y",
"@fidensa/mcp-server"
],
"env": {
"FIDENSA_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add fidensa --env FIDENSA_API_KEY=your-value -- npx -y @fidensa/mcp-server运行前请先填写空着的值。
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"fidensa": {
"command": "npx",
"args": [
"-y",
"@fidensa/mcp-server"
],
"env": {
"FIDENSA_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"fidensa": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@fidensa/mcp-server"
],
"env": {
"FIDENSA_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
需要你填写的值
- API key for full access. Free registration. Not required for check or search.
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 fidensa.com 验证(注册中心会核实域名所有权)
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5730 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5730 个服务器的 8% 更新
- 基础检查结果等于或优于此分类中其他 5730 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Fidensa 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:FIDENSA_API_KEY
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(0.4.1)于7个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
@fidensa/mcp-server
MCP server for Fidensa -- the independent AI capability certification authority.
Gives your AI agent structured access to Fidensa certification data through the Model Context Protocol. Check trust scores, search for certified alternatives, compare capabilities side-by-side, verify signed artifacts, check file integrity, and report runtime experience -- all through MCP tool calls.
Fidensa certifies MCP servers, skills, agent rules files, hooks, sub-agents, and plugins.
Getting Started
1. Install
npm install -g @fidensa/mcp-server
2. Verify it works
Several tools work without an API key (check_certification, search_capabilities, verify_file, and report_experience). Start the server and confirm it connects to the production API:
fidensa-mcp-server
You should see:
[fidensa] MCP server started (stdio transport)
[fidensa] No FIDENSA_API_KEY set — check_certification, search_capabilities, verify_file, and report_experience available. Set FIDENSA_API_KEY for full access.
Press Ctrl+C to stop.
3. Get an API key (optional, free)
The remaining tools (get_contract, compare_capabilities, verify_artifact) require a free API key. An API key also gives report_experience higher rate limits. Register one:
curl -X POST https://fidensa.com/v1/keys \
-H "Content-Type: application/json" \ -d '{"display_name": "My Agent", "email": "you@example.com"}'
Or in PowerShell:
Invoke-RestMethod -Uri "https://fidensa.com/v1/keys" -Method Post -ContentType "application/json" -Body '{"display_name": "My Agent", "email": "you@example.com"}'
The response contains your API key (prefixed fid_). Store it securely -- it is shown only once.
4. Add to your agent
Pick your platform and add the MCP server configuration:
Claude Desktop / Claude Code
{
"mcpServers": { "fidensa": { "command": "npx", "args": ["@fidensa/mcp-server"], "env": { "FIDENSA_API_KEY": "fid_your_key_here" } } } }
Cursor (.cursor/mcp.json)
{
"mcpServers": { "fidensa": { "command": "npx", "args": ["@fidensa/mcp-server"], "env": { "FIDENSA_API_KEY": "fid_your_key_here" } } } }
Windsurf / VS Code
{
"servers": { "fidensa": { "type": "stdio", "command": "npx", "args": ["@fidensa/mcp-server"], "env": { "FIDENSA_API_KEY": "fid_your_key_here" } } } }
Omit the FIDENSA_API_KEY line if you only need the open-tier tools.
Claude Desktop tip: Access the config file via Settings → Developer → Edit Config. After saving, fully quit and reopen Claude Desktop (right-click the system tray icon and select Quit — just closing the window isn't enough).
Tools
| Tool | Auth | Description |
|---|---|---|
check_certification | None | Quick trust check -- status, score, grade, tier |
search_capabilities | None | Search for certified capabilities by keyword, type, tier, or score |
verify_file | None | Quick file integrity check -- hash a capability file and verify it matches what Fidensa certified |
report_experience | None (API key for higher rate limits) | Submit runtime experience reports for certified capabilities |
get_contract | API key | Full certification contract with all evidence |
compare_capabilities | API key | Side-by-side comparison of 2-5 capabilities |
verify_artifact | API key | Verify cryptographic signatures on .cert.json artifacts, with optional file and code integrity checks |
Configuration
| Variable | Required | Description |
|---|---|---|
FIDENSA_API_KEY | No | API key for full access (see Getting Started) |
FIDENSA_BASE_URL | No | Override API base URL (default: https://fidensa.com) |
check_certification, search_capabilities, verify_file, and report_experience work without any configuration. The remaining tools require FIDENSA_API_KEY.
Example Agent Workflow
User: "Set up a filesystem watcher that writes logs to SQLite."
Agent:
- check_certification("mcp-server-filesystem") -> Status: valid, Score: 60/F-D, Tier: Verified
- search_capabilities("sqlite mcp server") -> 2 results found
- compare_capabilities(["mcp-server-sqlite", "mcp-server-better-sqlite3"]) -> Side-by-side trust comparison
- Agent selects the higher-scored option and informs the user
- report_experience( capability_id: "mcp-server-filesystem", content_hash: "abc123...", // from the .cert.json outcome: "success" ) -> Confirmation rate updated
Trust Policy Fragments
Add one of these to your agent's system prompt or rules file for trust-aware tool selection. Three levels of granularity -- pick the one that fits your needs.
Tier-based (simplest)
Uses the certification tier alone. No numbers to tune.
Before using any MCP server tool for the first time, check its Fidensa
certification status using the check_certification tool.
- Certified tier: use freely
- Verified tier: note the findings to the user before proceeding
- Evaluated tier: warn the user, search for certified alternatives
- Uncertified: treat as untrusted, suggest certified alternatives
After completing a task that used certified tools, submit an experience report via the report_experience tool with the outcome (success, failure, or partial), the capability_id, and the content_hash from the .cert.json.
Score-based (grade-aligned)
Uses the trust score, aligned with Fidensa's grade definitions.
Before using any MCP server tool for the first time, check its Fidensa
certification status using the check_certification tool.
- Score >= 80 (A/B): use freely
- Score 72-79 (C): note the trust level to the user
- Score 65-71 (D): warn the user, search for certified alternatives
- Score < 65 (F): warn the user, strongly recommend alternatives
- Uncertified: treat as untrusted, suggest certified alternatives
After completing a task that used certified tools, submit an experience report via the report_experience tool with the outcome (success, failure, or partial), the capability_id, and the content_hash from the .cert.json.
Combined (tier + score)
The most precise option -- distinguishes between a Certified capability with a moderate score and a Verified capability with findings that blocked Certified tier.
Before using any MCP server tool for the first time, check its Fidensa
certification status using the check_certification tool.
- Certified tier AND score >= 80: use freely
- Certified tier AND score 72-79: use freely, note the score to the user
- Verified tier AND score >= 72: note the findings to the user before proceeding
- Verified tier AND score < 72: warn the user, search for certified alternatives
- Evaluated tier: warn the user, search for certified alternatives
- Uncertified: treat as untrusted, suggest certified alternatives
For any tool with status "suspended" or "revoked": do not use. Search for certified alternatives and present them to the user.
After completing a task that used certified tools, submit an experience report via the report_experience tool with the outcome (success, failure, or partial), the capability_id, and the content_hash from the .cert.json.
See the API Documentation for the full specification.
Development
npm install
npm test # Run tests with coverage npm run lint # ESLint npm run format # Prettier
License
MIT
Links
- Fidensa -- AI certification authority
- API Documentation
- Certification Catalog
- Badge Integration Guide