MCPfinder - MCP Server Discovery
NPM · @MCPFINDER/SERVER · SCANNED SEP 20
Your AI discovers and installs MCP servers across Official Registry, Glama, and Smithery.
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 97 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 (AGPL-3.0-or-later).Pass
- Actively maintained (last published 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 573 tokens (~143/item across 4 items; 4 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 MCPfinder - MCP Server Discovery server?
MCPfinder - MCP Server Discovery runs locally as an npm package, launched with npx -y @mcpfinder/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 · @mcpfinder/server
claude mcp add dev-mcpfinder-server -- npx -y @mcpfinder/server
{
"mcpServers": {
"dev-mcpfinder-server": {
"command": "npx",
"args": [
"-y",
"@mcpfinder/server"
]
}
}
} {
"servers": {
"dev-mcpfinder-server": {
"command": "npx",
"args": [
"-y",
"@mcpfinder/server"
]
}
}
} codex mcp add dev-mcpfinder-server -- npx -y @mcpfinder/server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-mcpfinder-server": {
"type": "local",
"command": [
"npx",
"-y",
"@mcpfinder/server"
],
"enabled": true
}
}
} openclaw mcp add dev-mcpfinder-server --command npx --arg -y --arg @mcpfinder/server
mcp_servers:
dev-mcpfinder-server:
command: "npx"
args: ["-y", "@mcpfinder/server"] {
"McpServers": {
"dev-mcpfinder-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mcpfinder/server"
]
}
}
} assistant mcp add dev-mcpfinder-server -t stdio -c npx -a -y @mcpfinder/server
{
"mcpServers": {
"dev-mcpfinder-server": {
"command": "npx",
"args": [
"-y",
"@mcpfinder/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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
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 20 Sept 2026 · Analysed npm/@mcpfinder/server@1.1.0
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 97 packages
| Packages resolved | 97 |
|---|---|
| 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 →
browse_categories ~130
Single-call category browser for broad discovery. Call with no `category` to list all categories with counts; call with a `category` to get the highest-signal servers in that category. Prefer search_mcp_servers when the user names a concrete technology like Slack, Postgres, GitHub, or Notion; use this when discovery is domain-driven (database, filesystem, communication, security, ai, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category name; omit to list all categories |
| limit | number | – | Maximum results when category is provided (default: 20, max: 50) |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | – |
| category | string | – | – |
| next_actions | array | yes | – |
| results | array | – | – |
No examples provided.
get_install_config ~96
Use this after get_server_details to generate a ready-to-paste JSON config snippet for the target client. Returns structured config, file paths, required env vars, restart guidance, and safety flags like requires_user_secrets and safe_to_autoinstall.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Server name or slug (e.g., "filesystem", "io.modelcontextprotocol/filesystem") |
| platform | string | – | Target platform for install config |
| Name | Type | Req | Description |
|---|---|---|---|
| autoInstallable | boolean | – | – |
| config | object | – | – |
| configFilePath | object | – | – |
| envVarsNeeded | array | – | – |
| found | boolean | yes | – |
| installType | string | – | – |
| name | string | – | – |
| next_actions | array | yes | – |
| platform | string | – | – |
| requires_user_secrets | boolean | – | – |
| safe_to_autoinstall | boolean | – | – |
| server | string | – | – |
| warningFlags | array | – | – |
No examples provided.
get_server_details ~105
Always call this before recommending or installing a server. It returns the metadata you need to judge safety and fit: install method, transport, environment variables, source count, trust signals, warnings, and any discovered tools/capabilities. Use it to warn the user about secrets, stale projects, or weak metadata before calling get_install_config.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Server name (e.g., "io.modelcontextprotocol/filesystem") or slug (e.g., "filesystem") |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| name | string | – | – |
| next_actions | array | yes | – |
| server | object | – | – |
No examples provided.
search_mcp_servers ~242
Call this first whenever the user needs a capability you do not already have. Use it when the user mentions an external service, a database, a filesystem, a SaaS tool, or asks "can you connect to X?". Examples: "connect to postgres" -> query "postgres"; "read my Slack" -> query "slack"; "browse local files" -> query "filesystem". If results are weak, retry with a broader term. After choosing a candidate, call get_server_details before recommending or installing it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum results to return (default: 10, max: 50) |
| query | string | – | Search query — a keyword (e.g., "filesystem"), use case ("query databases"), or technology ("postgres"). Common aliases work: "gh" → github, "pg" → postgres, "k8s" → kubernetes, "db" → database. Leav… |
| registrySource | string | – | Filter by registry source |
| registryType | string | – | Filter by package registry type |
| transportType | string | – | Filter by transport type |
| Name | Type | Req | Description |
|---|---|---|---|
| next_actions | array | yes | – |
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
What is the MCPfinder - MCP Server Discovery server?
MCPfinder - MCP Server Discovery is listed in the public MCP registry as dev.mcpfinder/server. Your AI discovers and installs MCP servers across Official Registry, Glama, and Smithery. This page covers its npm package (@mcpfinder/server).
Is the MCPfinder - MCP Server Discovery server safe to use?
MCPfinder - MCP Server Discovery scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 MCPfinder - MCP Server Discovery server expose?
MCPfinder - MCP Server Discovery exposes 4 tools: search_mcp_servers, get_server_details, get_install_config, browse_categories. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.
Is the MCPfinder - MCP Server Discovery server still maintained?
MCPfinder - MCP Server Discovery is still listed as active in the MCP registry. We last reached this channel on 20 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 MCPfinder - MCP Server Discovery server under?
MCPfinder - MCP Server Discovery declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.