Fidensa MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Fidensa MCP Server check trust score for mcp-server-filesystem"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@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-server2. 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-serverYou 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).
Related MCP server: TrustMesh MCP Server
Tools
Tool | Auth | Description |
| None | Quick trust check -- status, score, grade, tier |
| None | Search for certified capabilities by keyword, type, tier, or score |
| None | Quick file integrity check -- hash a capability file and verify it matches what Fidensa certified |
| None (API key for higher rate limits) | Submit runtime experience reports for certified capabilities |
| API key | Full certification contract with all evidence |
| API key | Side-by-side comparison of 2-5 capabilities |
| API key | Verify cryptographic signatures on .cert.json artifacts, with optional file and code integrity checks |
Configuration
Variable | Required | Description |
| No | API key for full access (see Getting Started) |
| No | Override API base URL (default: |
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:
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 updatedTrust 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 # PrettierLicense
MIT
Links
Fidensa -- AI certification authority
Available Tools
7 toolscheck_certificationCheck Fidensa CertificationARead-only
Quick trust check for an AI capability (MCP server, skill, plugin, or workflow). Returns certification status, trust score, grade, tier, and supply chain status. No API key required. Use this before invoking any capability to verify it has been independently certified by Fidensa.
Inputs: capability_id (required), version.
compare_capabilitiesCompare Fidensa Certified CapabilitiesARead-only
Side-by-side comparison of 2-5 certified capabilities. Shows trust scores, grades, tiers, and per-signal breakdowns to help choose between alternatives. Requires a free API key (set FIDENSA_API_KEY).
Inputs: capability_ids (required).
get_contractGet Fidensa Certification ContractARead-only
Retrieve the full certification contract for a capability, including identity, supply chain analysis, security scan results, adversarial testing findings, behavioral fingerprint, and trust score breakdown. Requires a free API key (set FIDENSA_API_KEY).
Inputs: capability_id (required), version.
report_experienceReport Experience with a CapabilityA
Submit an experience report for a certified capability. Reports feed into the social proof signal of the trust score. Requires the content_hash from the .cert.json artifact (proves you've encountered the certified file). API key optional but recommended for higher rate limits.
Inputs: capability_id (required), content_hash (required), outcome (required), version, +2 more.
search_capabilitiesSearch Fidensa Certified CapabilitiesARead-only
Search for certified AI capabilities by keyword or description. Use this to discover certified alternatives when a capability is uncertified or scores poorly. Supports filtering by type, tier, and minimum trust score. No API key required.
Inputs: query (required), type, tier, min_score, +1 more.
verify_artifactVerify Fidensa Certification ArtifactARead-only
Verify the cryptographic signature on a Fidensa certification artifact (.cert.json). Checks platform signature, content hash, expiry, and optionally code integrity (git SHA match) and file integrity (file hash match). For true offline verification, pass the .cert.json content from the capability's published package via the content parameter. Requires a free API key (set FIDENSA_API_KEY).
Inputs: content, url, installed_git_sha, file_hash.
verify_fileVerify Certified File IntegrityARead-only
Quick file integrity check: pass the SHA-256 hash of a capability file and its capability_id to verify the file matches what Fidensa certified. This is the simplest verification path — no .cert.json needed. No API key required.
Inputs: capability_id (required), file_hash (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool serves a unique purpose: quick trust check, comparison, detailed contract retrieval, experience reporting, search, cryptographic verification, and file hash check. No overlap.
All tools consistently use verb_noun pattern with underscores (e.g., check_certification, compare_capabilities), making them predictable.
7 tools cover the certification domain without redundancy or deficiency; the count is well-scoped for the server's purpose.
The set provides complete lifecycle coverage: discover, trust check, compare, retrieve details, verify artifacts/files, and submit feedback. No gaps apparent.
Maintenance
Related MCP Connectors
Trust infrastructure for AI agents: read a verifiable Trust Rating, claim an identity, earn a badge.
AI-agent trust infrastructure for discovery, authority, execution, verification, and receipts.
Trust infrastructure for AI agents. Portable reputation (JTS 0-5), agent discovery, vouching.
Trust signals for AI agents: an open agent-readiness standard and developer tool guide. Read-only.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides agent certification and trust verification tools for AI agents, enabling certification checks, trust score calculations, audit ticket issuance, and emergency kill switch activation through the A-SOC trust network.1 npm1-
- AlicenseNot gradedqualityNot gradedmaintenanceProvides AI agents with trust scoring and reputation management capabilities for secure interactions. Enables agents to check trust scores, rate interactions, and manage disputes before transacting with other agents.-
- AlicenseAqualityBmaintenanceThe open registry of AI agents. Every agent gets a free birth certificate (a number and a date) and can timestamp what it creates, or only its SHA-256, with an RFC 3161 timestamp and a Bitcoin anchor that anyone can verify without us. Free, no account.11MIT
- AlicenseNot gradedqualityDmaintenanceTrust infrastructure for AI agents enabling directory browsing, agent submission/verification, job applications, and peer feedback exchange via MCP.MIT