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.

Trefle

NPM · @PIPEWORX/MCP-TREFLE · 2 COMPONENTS

Trefle MCP — global plant database (1M+ species)

0 this week 81 Trust /100

Last scanned (1 hour ago)

Scores higher than 68% of npm servers

Category Health and Science

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-trefle). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 401 tokens (~80/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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 81

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-trefle@0.2.0

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-trefle
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-trefle/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3560557938
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:8c5d47796fd46a5cb28ca51e26dcf718365a470966faf04f5568dfe7a37e1eb30552fc397afa41d046d4c41fe3e7e0c548473812da72949b31e7e4356

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 · 5 exposed · ~348 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
get_plant ~47

Full plant record by Trefle ID. Returns scientific/common names, family, status, image, year, main species.

NameTypeReqDescription
plant_idnumberyesTrefle plant ID

No output schema declared.

No examples provided.

get_species ~49

Full species record: growth habit, light/atmospheric humidity/soil requirements, edible / medicinal flags, distribution, images, sources.

NameTypeReqDescription
species_idnumberyesTrefle species ID

No output schema declared.

No examples provided.

list_distributions ~92

Native or introduced distribution zones (TDWG WGSRPD codes — e.g., "NWY" = Norway, "CAL" = California). Returns species lists by zone.

NameTypeReqDescription
pagenumber–1-based page
page_sizenumber–1-100
zonestringyesTDWG zone code (e.g., "CAL", "FRA", "JAP")

No output schema declared.

No examples provided.

search_plants ~95

Search plants by common or scientific name. Returns Trefle plant ID, scientific name, common name, family, image. Filter by edible flags.

NameTypeReqDescription
edibleboolean–Only edible plants
pagenumber–1-based page
page_sizenumber–1-100 (default 20)
querystringyesFree-text query
vegetableboolean–Only vegetables

No output schema declared.

No examples provided.

search_species ~65

Search species (the rank below plants — some plants have multiple species). Returns Trefle species ID + scientific name.

NameTypeReqDescription
pagenumber–1-based page
page_sizenumber–1-100
querystringyesFree-text query

No output schema declared.

No examples provided.

Install

How do I install the Trefle MCP server?

Trefle runs locally as an npm package, launched with npx -y @pipeworx/mcp-trefle. 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-trefle

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

What is the Trefle MCP server?

Trefle is an MCP server listed in the public MCP registry as io.github.pipeworx-io/trefle. Trefle MCP, global plant database (1M+ species). This page covers its npm package (@pipeworx/mcp-trefle).

Is the Trefle MCP server safe to use?

Trefle scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Trefle MCP server expose?

Trefle exposes 5 tools: search_plants, get_plant, search_species, get_species, list_distributions. Their descriptions and schemas cost roughly 348 tokens of context every time the server is loaded.

Is the Trefle MCP server still maintained?

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

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