Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.isaac-levine/forage

NPM · FORAGE-MCP · SCANNED AUG 3

Self-improving tool discovery for AI agents. Find, install, and use new MCP servers automatically.

Available components

+22 this week 68 Trust /100
Trust breakdown (6 categories)

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 Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), 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 (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).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 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

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 · forage-mcp

# add to Claude Code
claude mcp add isaac-levine-forage -- npx -y forage-mcp
# add to Codex CLI
codex mcp add isaac-levine-forage -- npx -y forage-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "isaac-levine-forage": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "forage-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add isaac-levine-forage --command npx --arg -y --arg forage-mcp
# ~/.hermes/config.yaml
mcp_servers:
  isaac-levine-forage:
    command: "npx"
    args: ["-y", "forage-mcp"]
// mcp.json
{
  "mcpServers": {
    "isaac-levine-forage": {
      "command": "npx",
      "args": [
        "-y",
        "forage-mcp"
      ]
    }
  }
}
Changelog

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 +62
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Security disclosure: fail → unverified functional
    • Tool coverage: unverified → 100 functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Schema quality: unverified → good functional
    • Licence: MIT functional
  • 1 Aug 26 −1
    • Dependency health: partial → unverified functional
  • 31 Jul 26 −40
    • 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 +22
    • Tool coverage: unverified → 100 functional
  • 28 Jul 26 −22
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 46

    First indexed and scored.

Diagnostics

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/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~551 tokens

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.

Tool Tokens
forage_evaluate ~59

Get detailed information about a specific package — version, downloads, README summary, install command. Use this before installing to verify quality.

NameTypeReqDescription
packageNamestringyesnpm 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).

NameTypeReqDescription
argsarrayArguments for the command. Defaults to ['-y', packageName].
commandstringCommand to run the server. Defaults to 'npx'.
confirmbooleanyesMust be true to proceed with installation. This is a safety gate — the user will see and approve the tool call.
envobjectEnvironment variables to pass to the server process.
packageNamestringyesnpm 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.

NameTypeReqDescription
rulesstringyesMarkdown-formatted usage instructions for the agent. Include: when to use the tool, key commands/patterns, any required env vars or config.
targetstringSpecific file path to write to. If omitted, auto-detects based on which agent is in use.
toolNamestringyesName 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.

NameTypeReqDescription
querystringyesNatural language description of the capability you need (e.g. 'query postgres database', 'search slack messages', 'manage github issues')
sourcesarrayWhich 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.

NameTypeReqDescription
confirmbooleanMust be true to proceed with uninstallation.
namestringyesName of the installed tool to remove (as shown in forage_status)

No output schema declared.

No examples provided.