io.github.isaac-levine/forage
NPM · FORAGE-MCP · SCANNED SEP 22
Self-improving tool discovery for AI agents. Find, install, and use new MCP servers automatically.
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 95 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 (MIT).Pass
- Actively maintained (last published 217 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 551 tokens (~91/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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; "forage_uninstall" implies "uninstall" 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 6 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 io.github.isaac-levine/forage MCP server?
io.github.isaac-levine/forage runs locally as an npm package, launched with npx -y forage-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · forage-mcp
claude mcp add isaac-levine-forage -- npx -y forage-mcp
{
"mcpServers": {
"isaac-levine-forage": {
"command": "npx",
"args": [
"-y",
"forage-mcp"
]
}
}
} {
"servers": {
"isaac-levine-forage": {
"command": "npx",
"args": [
"-y",
"forage-mcp"
]
}
}
} codex mcp add isaac-levine-forage -- npx -y forage-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"isaac-levine-forage": {
"type": "local",
"command": [
"npx",
"-y",
"forage-mcp"
],
"enabled": true
}
}
} openclaw mcp add isaac-levine-forage --command npx --arg -y --arg forage-mcp
mcp_servers:
isaac-levine-forage:
command: "npx"
args: ["-y", "forage-mcp"] {
"McpServers": {
"isaac-levine-forage": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"forage-mcp"
]
}
}
} assistant mcp add isaac-levine-forage -t stdio -c npx -a -y forage-mcp
{
"mcpServers": {
"isaac-levine-forage": {
"command": "npx",
"args": [
"-y",
"forage-mcp"
]
}
}
} 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.
- 21 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.
- 19 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 13 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 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.
- 10 Sept 26 −3
- Stability: pass → 0.80 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 22 Sept 2026 · Analysed npm/forage-mcp@0.1.1
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 95 packages
| Packages resolved | 95 |
|---|---|
| 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 →
forage_evaluate ~59
Get detailed information about a specific package — version, downloads, README summary, install command. Use this before installing to verify quality.
| Name | Type | Req | Description |
|---|---|---|---|
| packageName | string | yes | npm package name to evaluate (e.g. '@modelcontextprotocol/server-postgres') |
No output schema declared.
No examples provided.
forage_install ~163
Install an MCP server and start it as a proxied subprocess. The server's tools become available immediately via Forage — no restart needed. IMPORTANT: Set confirm=true to proceed with installation (user will be prompted to approve the tool call).
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Arguments for the command. Defaults to ['-y', packageName]. |
| command | string | – | Command to run the server. Defaults to 'npx'. |
| confirm | boolean | yes | Must be true to proceed with installation. This is a safety gate — the user will see and approve the tool call. |
| env | object | – | Environment variables to pass to the server process. |
| packageName | string | yes | npm package name to install (e.g. '@modelcontextprotocol/server-filesystem') |
No output schema declared.
No examples provided.
forage_learn ~135
Write usage instructions for an installed tool to agent rule files (CLAUDE.md, AGENTS.md, .cursor/rules/). This persists knowledge across sessions so the agent remembers how to use the tool next time.
| Name | Type | Req | Description |
|---|---|---|---|
| rules | string | yes | Markdown-formatted usage instructions for the agent. Include: when to use the tool, key commands/patterns, any required env vars or config. |
| target | string | – | Specific file path to write to. If omitted, auto-detects based on which agent is in use. |
| toolName | string | yes | Name of the tool (as shown in forage_status) |
No output schema declared.
No examples provided.
forage_search ~86
Search for MCP servers and tools across registries (Official MCP Registry, Smithery, npm). Describe what capability you need and get ranked results.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural language description of the capability you need (e.g. 'query postgres database', 'search slack messages', 'manage github issues') |
| sources | array | – | Which registries to search. Defaults to all. |
No output schema declared.
No examples provided.
forage_status ~38
List all tools that Forage has installed and is currently proxying. Shows which servers are running, what tools they provide, and their install status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
forage_uninstall ~70
Remove a previously installed tool. Stops the server, removes from manifest, and cleans up agent rules. Set confirm=true to proceed.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to proceed with uninstallation. |
| name | string | yes | Name of the installed tool to remove (as shown in forage_status) |
No output schema declared.
No examples provided.
What is the io.github.isaac-levine/forage MCP server?
io.github.isaac-levine/forage is an MCP server listed in the public MCP registry as io.github.isaac-levine/forage. Self-improving tool discovery for AI agents. Find, install, and use new MCP servers automatically. This page covers its npm package (forage-mcp).
Is the io.github.isaac-levine/forage MCP server safe to use?
io.github.isaac-levine/forage scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 io.github.isaac-levine/forage MCP server expose?
io.github.isaac-levine/forage exposes 6 tools: forage_search, forage_evaluate, forage_install, forage_learn, forage_status, forage_uninstall. Their descriptions and schemas cost roughly 551 tokens of context every time the server is loaded.
Is the io.github.isaac-levine/forage MCP server still maintained?
io.github.isaac-levine/forage is still listed as active in the MCP registry. We last reached this channel on 22 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 io.github.isaac-levine/forage MCP server under?
io.github.isaac-levine/forage declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.