Skip to main content
Glama

Trefle

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

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

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over 42 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-trefle
GitHub Stars
0
Server Listing
mcp-trefle

TDQS

B3.3/5.0

Scored across 19 tools

Disambiguation2/5

The server mixes plant tools with a large set of Pipeworx data tools. The catch-all 'ask_pipeworx' overlaps with many specific tools like 'validate_claim' and 'compare_entities', making it unclear which tool an agent should use. Plant tools are distinct but coexist with unrelated tools, causing ambiguity.

Naming Consistency2/5

Tool names use mixed conventions: snake_case verbs (ask_pipeworx, compare_entities), single verbs (forget, recall, remember), and noun_noun compounds (entity_profile, polymarket_arbitrage). No consistent pattern is followed, reducing predictability.

Tool Count2/5

With 19 tools spanning two unrelated domains (plant data and Pipeworx data query), the server is overburdened. The plant domain has only 5 tools, while the Pipeworx domain adds 14, making the set feel bloated and unfocused for a server named 'Trefle'.

Completeness3/5

For the plant domain, the tools cover search and retrieval reasonably well, but miss common operations like filtering or listing all plants. The Pipeworx tools are extensive but include meta-tools (e.g., 'discover_tools') that indicate an incomplete surface. Overall, the server's dual purpose leaves gaps in both areas.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Addedpolymarket_arbitrage
    • Addedpolymarket_edges
  2. 1 tool update
    • Addedbet_research
  3. 16 tool updates
    • First observedask_pipeworx
    • First observedcompare_entities
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedget_plant
    • First observedget_species
    • First observedlist_distributions
    • First observedpipeworx_feedback
    • First observedrecall
    • First observedrecent_changes
    • First observedremember
    • First observedresolve_entity
    • First observedsearch_plants
    • First observedsearch_species
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

  • grant-mcp

    vertical-mcp
    A
    license
    B
    quality
    D
    maintenance
    MCP server for searching research grants across NSF (US), ERC (EU), and KRF/NRF (Korea) via a unified interface. NIH excluded—covered by existing connectors.
    3
    8 npm
    MIT

  • hortusfox-mcp

    tomfrenzel
    A
    license
    B
    quality
    A
    maintenance
    MCP server for HortusFox self-hosted plant management system, exposing 38 tools to manage plants, locations, tasks, inventory, calendar, chat, and backups via natural language.
    38
    11 npm
    MIT

  • HealthLens

    lm203688
    A
    license
    A
    quality
    A
    maintenance
    8-axis integrative wellness MCP server: TCM constitution analysis, evidence-graded health signals, wellness knowledge search (6,207 herbs). L1/L2 tools public-safe, L3 personalized opt-in.
    6
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources