Fidensa MCP Server

MCP server forFidensa-- the independent AI capability certification authority.

[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.

The remaining tools (get_contract,compare_capabilities,verify_artifact) require a free API key. An API key also givesreport_experiencehigher 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"}'

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 (prefixedfid_). Store it securely -- it is shown only once.

Pick your platform and add the MCP server configuration:

{ "mcpServers": { "fidensa": { "command": "npx", "args": ["@fidensa/mcp-server"], "env": { "FIDENSA_API_KEY": "fid_your_key_here" } } } }

{ "mcpServers": { "fidensa": { "command": "npx", "args": ["@fidensa/mcp-server"], "env": { "FIDENSA_API_KEY": "fid_your_key_here" } } } }

{ "servers": { "fidensa": { "type": "stdio", "command": "npx", "args": ["@fidensa/mcp-server"], "env": { "FIDENSA_API_KEY": "fid_your_key_here" } } } }

Omit theFIDENSA_API_KEYline 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).

check_certification,search_capabilities,verify_file, andreport_experiencework without any configuration. The remaining tools requireFIDENSA_API_KEY.

User: "Set up a filesystem watcher that writes logs to SQLite." Agent: 1. check_certification("mcp-server-filesystem") -> Status: valid, Score: 60/F-D, Tier: Verified 2. search_capabilities("sqlite mcp server") -> 2 results found 3. compare_capabilities(["mcp-server-sqlite", "mcp-server-better-sqlite3"]) -> Side-by-side trust comparison 4. Agent selects the higher-scored option and informs the user 5. report_experience( capability_id: "mcp-server-filesystem", content_hash: "abc123...", // from the .cert.json outcome: "success" ) -> Confirmation rate updated

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.

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.

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.

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 theAPI Documentationfor the full specification.

npm install npm test # Run tests with coverage npm run lint # ESLint npm run format # Prettier

- Fidensa-- AI certification authority
- API Documentation
- Certification Catalog
- Badge Integration Guide

Paid remote MCP for agent data-access boundary reviews, permission scope evidence, sensitive data notes, and governance receipts.