Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Fidensa

by fidensaversion 0.4.1i★ –iRuns on your computer
Registry namecom.fidensa/mcp-server

Install

Overview

Description from the maker (original English)

Independent AI certification authority. Trust scores, search, comparison, and verification.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Search & AI memory
  • You need to fill in: FIDENSA_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: FIDENSA_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add fidensa --env FIDENSA_API_KEY=your-value -- npx -y @fidensa/mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • FIDENSA_API_KEY secret env
    API key for full access. Free registration. Not required for check or search.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain fidensa.com (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7249 servers in this category
  • Published to the registry more recently than 7% of the other 7249 servers in this category
  • Basic checks equal to or better than 100% of the other 7249 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Fidensa safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: FIDENSA_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.1) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@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

ToolAuthDescription
check_certificationNoneQuick trust check -- status, score, grade, tier
search_capabilitiesNoneSearch for certified capabilities by keyword, type, tier, or score
verify_fileNoneQuick file integrity check -- hash a capability file and verify it matches what Fidensa certified
report_experienceNone (API key for higher rate limits)Submit runtime experience reports for certified capabilities
get_contractAPI keyFull certification contract with all evidence
compare_capabilitiesAPI keySide-by-side comparison of 2-5 capabilities
verify_artifactAPI keyVerify cryptographic signatures on .cert.json artifacts, with optional file and code integrity checks

Configuration

VariableRequiredDescription
FIDENSA_API_KEYNoAPI key for full access (see Getting Started)
FIDENSA_BASE_URLNoOverride 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:

  1. check_certification("mcp-server-filesystem") -> Status: valid, Score: 60/F-D, Tier: Verified
  1. search_capabilities("sqlite mcp server") -> 2 results found
  1. compare_capabilities(["mcp-server-sqlite", "mcp-server-better-sqlite3"]) -> Side-by-side trust comparison
  1. Agent selects the higher-scored option and informs the user
  1. 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

Ask PopNx