# mcp-anything (npm · mcp-anything)

Meta-MCP gateway: search, inspect and call any MCP server from the public registries.

- Trust score: 82/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-23

## Components

- npm · `mcp-anything`: 82/100 (this document), [markdown](https://verifymcp.io/servers/dror-bengal-mcp-anything/mcp-anything.md), [page](https://verifymcp.io/servers/dror-bengal-mcp-anything/mcp-anything)

## Channel facts

- Registry: `npm`
- Package: `mcp-anything`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-23.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 32 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 313 tokens (~62/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add dror-bengal-mcp-anything -- npx -y mcp-anything
```

### Cursor

```json
{
  "mcpServers": {
    "dror-bengal-mcp-anything": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-anything"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dror-bengal-mcp-anything": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-anything"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dror-bengal-mcp-anything -- npx -y mcp-anything
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dror-bengal-mcp-anything": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-anything"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dror-bengal-mcp-anything --command npx --arg -y --arg mcp-anything
```

### Hermes

```yaml
mcp_servers:
  dror-bengal-mcp-anything:
    command: "npx"
    args: ["-y", "mcp-anything"]
```

### Netclaw

```json
{
  "McpServers": {
    "dror-bengal-mcp-anything": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-anything"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dror-bengal-mcp-anything -t stdio -c npx -a -y mcp-anything
```

### Other

```json
{
  "mcpServers": {
    "dror-bengal-mcp-anything": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-anything"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-22 (score 82, +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.

### 2026-09-21 (score 81, −3)

- [functional] Stability: pass → 0.80

### 2026-09-20 (score 84, 0)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 84, +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.

### 2026-09-17 (score 83, +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.

### 2026-09-15 (score 82, +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.

### 2026-09-13 (score 81, +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.

### 2026-09-10 (score 80, +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.

## MCP tools (5)

### `search_mcp_servers` (~89 tokens)

Search MCP servers

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.

Input parameters:

- `limit` (integer): Max results (default 5)
- `query` (string, required): What you want to do, e.g. 'query postgres database' or 'send slack message'

### `describe_mcp_server` (~63 tokens)

Describe an MCP server

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.

Input parameters:

- `name` (string, required): Registry server name, e.g. 'io.github.owner/weather'

### `list_mcp_tools` (~56 tokens)

List a server's tools (live)

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.

Input parameters:

- `server` (string, required): Registry server name from search_mcp_servers

### `call_mcp_tool` (~81 tokens)

Call a tool on an MCP server

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.

Input parameters:

- `arguments` (object): Arguments matching the tool's input schema
- `server` (string, required): Registry server name
- `tool` (string, required): Tool name exactly as returned by list_mcp_tools

### `sync_registry` (~24 tokens)

Refresh the registry index

Re-download the MCP registry index (otherwise refreshed automatically when the cache TTL expires).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dror-bengal-mcp-anything/mcp-anything#diagnostics

## Score history

- 2026-09-23: 82
- 2026-09-22: 82
- 2026-09-21: 81
- 2026-09-20: 84
- 2026-09-19: 84
- 2026-09-18: 83
- 2026-09-17: 83
- 2026-09-16: 82
- 2026-09-15: 82
- 2026-09-14: 81
- 2026-09-13: 81
- 2026-09-12: 80
- 2026-09-11: 80
- 2026-09-10: 80
- 2026-09-09: 79
- 2026-09-08: 79
- 2026-09-07: 78
- 2026-09-06: 78
- 2026-09-05: 77
- 2026-09-04: 77
- 2026-09-03: 76
- 2026-09-02: 76
- 2026-09-01: 75
- 2026-08-31: 75
- 2026-08-30: 74
- 2026-08-29: 74
- 2026-08-28: 70
- 2026-08-27: 70
- 2026-08-26: 70
- 2026-08-25: 70

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/mcp-anything
- Socket report: https://socket.dev/npm/package/mcp-anything
- Repository: https://github.com/Dror-Bengal/mcp-anything
- Website: https://dror-bengal.github.io/mcp-anything
- Changelog RSS feed: https://verifymcp.io/servers/dror-bengal-mcp-anything/mcp-anything.xml
- Changelog JSON feed: https://verifymcp.io/servers/dror-bengal-mcp-anything/mcp-anything.json
- HTML version of this page: https://verifymcp.io/servers/dror-bengal-mcp-anything/mcp-anything