mcp-anything
NPM · MCP-ANYTHING · SCANNED SEP 23
Meta-MCP gateway: search, inspect and call any MCP server from the public registries.
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 & Transparency48
- 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 32 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 313 tokens (~62/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "call_mcp_tool" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 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 mcp-anything server?
mcp-anything runs locally as an npm package, launched with npx -y mcp-anything. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-anything
claude mcp add dror-bengal-mcp-anything -- npx -y mcp-anything
{
"mcpServers": {
"dror-bengal-mcp-anything": {
"command": "npx",
"args": [
"-y",
"mcp-anything"
]
}
}
} {
"servers": {
"dror-bengal-mcp-anything": {
"command": "npx",
"args": [
"-y",
"mcp-anything"
]
}
}
} codex mcp add dror-bengal-mcp-anything -- npx -y mcp-anything
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dror-bengal-mcp-anything": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-anything"
],
"enabled": true
}
}
} openclaw mcp add dror-bengal-mcp-anything --command npx --arg -y --arg mcp-anything
mcp_servers:
dror-bengal-mcp-anything:
command: "npx"
args: ["-y", "mcp-anything"] {
"McpServers": {
"dror-bengal-mcp-anything": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-anything"
]
}
}
} assistant mcp add dror-bengal-mcp-anything -t stdio -c npx -a -y mcp-anything
{
"mcpServers": {
"dror-bengal-mcp-anything": {
"command": "npx",
"args": [
"-y",
"mcp-anything"
]
}
}
} 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 +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.
- 21 Sept 26 −3
- Stability: pass → 0.80 functional
- 20 Sept 26 0
- Stability: 0.97 → pass security
- 19 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.
- 17 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.
- 15 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 23 Sept 2026 · Analysed npm/mcp-anything@0.2.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 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 →
call_mcp_tool Call a tool on an MCP server ~81
Execute a specific tool on a downstream MCP server with the given arguments. Use list_mcp_tools first to get the exact tool name and input schema.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | Arguments matching the tool's input schema |
| server | string | yes | Registry server name |
| tool | string | yes | Tool name exactly as returned by list_mcp_tools |
No output schema declared.
No examples provided.
describe_mcp_server Describe an MCP server ~63
Show a server's full registry metadata: transports (remote endpoints / installable packages), required environment variables and secrets, and whether the current security policy allows connecting to it.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Registry server name, e.g. 'io.github.owner/weather' |
No output schema declared.
No examples provided.
list_mcp_tools List a server's tools (live) ~56
Connect to an MCP server (per security policy) and list its actual tools with their input schemas. Connection is reused for subsequent call_mcp_tool calls.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | Registry server name from search_mcp_servers |
No output schema declared.
No examples provided.
search_mcp_servers Search MCP servers ~89
Search the MCP registry index for servers matching a task description (keyword search over names and descriptions). Returns candidate servers with their connectability. Follow up with describe_mcp_server / list_mcp_tools.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 5) |
| query | string | yes | What you want to do, e.g. 'query postgres database' or 'send slack message' |
No output schema declared.
No examples provided.
sync_registry Refresh the registry index ~24
Re-download the MCP registry index (otherwise refreshed automatically when the cache TTL expires).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the mcp-anything server?
mcp-anything is listed in the public MCP registry as io.github.Dror-Bengal/mcp-anything. Meta-MCP gateway: search, inspect and call any MCP server from the public registries. This page covers its npm package (mcp-anything).
Is the mcp-anything server safe to use?
mcp-anything scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 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 mcp-anything server expose?
mcp-anything exposes 5 tools: search_mcp_servers, describe_mcp_server, list_mcp_tools, call_mcp_tool, sync_registry. Their descriptions and schemas cost roughly 313 tokens of context every time the server is loaded.
Is the mcp-anything server still maintained?
mcp-anything is still listed as active in the MCP registry. We last reached this channel on 23 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 mcp-anything server under?
mcp-anything declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.