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

Forager

NPM · @PIPEWORX/MCP-FORAGER · 2 COMPONENTS

Forager MCP — wraps the Forager person-phone-lookup API (forager.ai)

82 Trust /100

Last scanned (21 hours ago)

Scores higher than 72% of npm servers

Category CRM and Sales

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-forager). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 216 tokens (~216/item across 1 items; 1 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 Management17
  • Stability observed for 5 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
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 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.10 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 80

    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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-forager@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-forager
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-forager/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637318008
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:8c857306d940243ceade7ed86ae3d29a4e84a2c7ab114b78a70d3d7d5873794c4a81634bd1020f86cd450413a0d53887af782b89cba641af6539adad0

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~164 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. 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 →

Tool Tokens
forager_find_phone ~164

Find a person's phone number from their LinkedIn profile URL, via Forager. Requires both your Forager account id and API key. Example: forager_find_phone({ linkedin_url: "https://www.linkedin.com/in/patrickcollison/", _accountId: "your-forager-account-id", _apiKey: "your-forager-key" })

NameTypeReqDescription
_accountIdstring–Your Forager account id (shown alongside your API key on the Forager dashboard).
_apiKeystring–Your Forager API key.
linkedin_urlstring–The person's LinkedIn profile URL.
person_idstring–Optional Forager person id, if already known from a prior Forager lookup, used instead of linkedin_url.

No output schema declared.

No examples provided.

Install

How do I install the Forager MCP server?

Forager runs locally as an npm package, launched with npx -y @pipeworx/mcp-forager. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-forager

# add to Claude Code
claude mcp add pipeworx-io-forager -- npx -y @pipeworx/mcp-forager
Common questions

What is the Forager MCP server?

Forager is an MCP server listed in the public MCP registry as io.github.pipeworx-io/forager. Forager MCP, wraps the Forager person-phone-lookup API (forager.ai). This page covers its npm package (@pipeworx/mcp-forager).

Is the Forager MCP server safe to use?

Forager scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Forager MCP server expose?

Forager exposes 1 tool: forager_find_phone. Their descriptions and schemas cost roughly 164 tokens of context every time the server is loaded.

Is the Forager MCP server still maintained?

Forager is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Forager MCP server under?

Forager declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.