MCPfinder - MCP Server Discovery
NPM · @MCPFINDER/SERVER · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. 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 48 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @mcpfinder/server
claude mcp add dev-mcpfinder-server -- npx -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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +25
- Install scripts: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Maintenance: pass → unverified ▼ functional
- License: pass → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Licence: AGPL-3.0-or-later functional
- 31 Jul 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −31
- Malware scan: pass → unverified ▼ security
- Known CVEs: partial → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- 29 Jul 26 +52
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Schema quality: unverified → good ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: AGPL-3.0-or-later functional
- 28 Jul 26 −19
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 45
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@mcpfinder/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 96 packages
96 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.