Fidensa
NPM · @FIDENSA/MCP-SERVER · SCANNED SEP 22
Independent AI certification authority. Trust scores, search, comparison, and verification.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 176 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 839 tokens (~119/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Fidensa MCP server?
Fidensa runs locally as an npm package, launched with npx -y @fidensa/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @fidensa/mcp-server
claude mcp add com-fidensa-mcp-server -- npx -y @fidensa/mcp-server
{
"mcpServers": {
"com-fidensa-mcp-server": {
"command": "npx",
"args": [
"-y",
"@fidensa/mcp-server"
]
}
}
} {
"servers": {
"com-fidensa-mcp-server": {
"command": "npx",
"args": [
"-y",
"@fidensa/mcp-server"
]
}
}
} codex mcp add com-fidensa-mcp-server -- npx -y @fidensa/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-fidensa-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@fidensa/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add com-fidensa-mcp-server --command npx --arg -y --arg @fidensa/mcp-server
mcp_servers:
com-fidensa-mcp-server:
command: "npx"
args: ["-y", "@fidensa/mcp-server"] {
"McpServers": {
"com-fidensa-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@fidensa/mcp-server"
]
}
}
} assistant mcp add com-fidensa-mcp-server -t stdio -c npx -a -y @fidensa/mcp-server
{
"mcpServers": {
"com-fidensa-mcp-server": {
"command": "npx",
"args": [
"-y",
"@fidensa/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Analysed npm/@fidensa/mcp-server@0.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_certification Check Fidensa Certification ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | yes | Capability identifier (e.g. "mcp-server-filesystem") |
| version | string | – | Specific version to check (e.g. "1.0.0"). Omit for latest. |
No output schema declared.
No examples provided.
compare_capabilities Compare Fidensa Certified Capabilities ~73
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).
| Name | Type | Req | Description |
|---|---|---|---|
| capability_ids | array | yes | Array of 2-5 capability IDs to compare |
No output schema declared.
No examples provided.
get_contract Get Fidensa Certification Contract ~78
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).
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | yes | Capability identifier |
| version | string | – | Specific version (omit for latest) |
No output schema declared.
No examples provided.
report_experience Report Experience with a Capability ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | yes | Capability identifier |
| content_hash | string | yes | SHA-256 content hash from the .cert.json artifact or the certification block. This proves you have the certified file. |
| details | object | – | Additional details |
| environment | object | – | Environment context |
| outcome | string | yes | Overall outcome of using the capability |
| version | string | – | Capability version (e.g. "1.0.0"). Server defaults to latest if omitted. |
No output schema declared.
No examples provided.
search_capabilities Search Fidensa Certified Capabilities ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results (default: 10) |
| min_score | integer | – | Minimum trust score (0-100) |
| query | string | yes | Search query (natural language or keywords) |
| tier | string | – | Filter by certification tier |
| type | string | – | Filter by capability type |
No output schema declared.
No examples provided.
verify_artifact Verify Fidensa Certification Artifact ~211
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).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Base64-encoded .cert.json artifact content. Preferred for independent verification. |
| file_hash | string | – | SHA-256 hash of the capability file (excluding the residual comment line). When provided, verifies the file matches the certified original. |
| installed_git_sha | string | – | Git commit SHA of the installed code (from "git rev-parse HEAD"). When provided, verifies that the installed code matches the certified commit. |
| url | string | – | fidensa.com URL to fetch the artifact (convenience, but verification is circular since the artifact comes from the same authority verifying it). |
No output schema declared.
No examples provided.
verify_file Verify Certified File Integrity ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | yes | Capability identifier |
| file_hash | string | yes | SHA-256 hash of the capability file (excluding the residual comment line if present). |
No output schema declared.
No examples provided.
What is the Fidensa MCP server?
Fidensa is an MCP server listed in the public MCP registry as com.fidensa/mcp-server. Independent AI certification authority. Trust scores, search, comparison, and verification. This page covers its npm package (@fidensa/mcp-server).
Is the Fidensa MCP server safe to use?
Fidensa scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Fidensa MCP server expose?
Fidensa exposes 7 tools: check_certification, get_contract, search_capabilities, compare_capabilities, report_experience, and 2 more. Their descriptions and schemas cost roughly 839 tokens of context every time the server is loaded.
Is the Fidensa MCP server still maintained?
Fidensa is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Fidensa MCP server under?
Fidensa declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.