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.

io.github.QWarranto/leafengines

NPM · @ANCIENTWHISPERS54/LEAFENGINES-MCP-SERVER · SCANNED SEP 20

🌱 Agricultural AI: Soil analysis, crop recommendations, weather forecasts. FREE TurboQuant.

0 this week 74 Trust /100
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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.6.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 12 of 44 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 307 tokens (~102/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.github.QWarranto/leafengines MCP server?

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

npm · @ancientwhispers54/leafengines-mcp-server

# add to Claude Code
claude mcp add qwarranto-leafengines -- npx -y @ancientwhispers54/leafengines-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "qwarranto-leafengines": {
      "command": "npx",
      "args": [
        "-y",
        "@ancientwhispers54/leafengines-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "qwarranto-leafengines": {
      "command": "npx",
      "args": [
        "-y",
        "@ancientwhispers54/leafengines-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add qwarranto-leafengines -- npx -y @ancientwhispers54/leafengines-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "qwarranto-leafengines": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@ancientwhispers54/leafengines-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add qwarranto-leafengines --command npx --arg -y --arg @ancientwhispers54/leafengines-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  qwarranto-leafengines:
    command: "npx"
    args: ["-y", "@ancientwhispers54/leafengines-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "qwarranto-leafengines": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@ancientwhispers54/leafengines-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add qwarranto-leafengines -t stdio -c npx -a -y @ancientwhispers54/leafengines-mcp-server
// mcp.json
{
  "mcpServers": {
    "qwarranto-leafengines": {
      "command": "npx",
      "args": [
        "-y",
        "@ancientwhispers54/leafengines-mcp-server"
      ]
    }
  }
}
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.

  • 20 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.

  • 18 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.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 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.

  • 11 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.83 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@ancientwhispers54/leafengines-mcp-server@2.0.8

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 44 packages
Packages resolved 44
Stale 12
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~307 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
agricultural_intelligence ~88

ENHANCED TIER ($0.003/call): AI-powered agricultural insights combining soil, climate, and crop science. Get planting recommendations, yield predictions, risk assessments, and sustainability scores.

NameTypeReqDescription
county_fipsstringyes5-digit US county FIPS code
crop_typestringCrop to analyze
questionstringSpecific agricultural question to answer

No output schema declared.

No examples provided.

county_lookup ~74

COMMODITIZED TIER ($0.001/call): Resolve US location names to FIPS codes. Search by county name, state, or FIPS code. Returns county details needed for other LeafEngines tools.

NameTypeReqDescription
termstringyesSearch term — county name, state name, or partial FIPS code

No output schema declared.

No examples provided.

get_soil_data ~145

COMMODITIZED TIER ($0.001/call): Get USDA SSURGO soil analysis for any US county. Returns pH, nutrients, organic matter, drainage, and texture. Perfect for Claude when you need: agricultural planning, environmental assessments, land evaluation, or basic soil composition data. Optional: county_name and state_code (helpful if you have them from county_lookup).

NameTypeReqDescription
county_fipsstringyes5-digit US county FIPS code
county_namestringCounty name (optional, but recommended with state_code)
state_codestring2-letter state code (optional, but recommended with county_name)

No output schema declared.

No examples provided.

Common questions

What is the io.github.QWarranto/leafengines MCP server?

io.github.QWarranto/leafengines is an MCP server listed in the public MCP registry as io.github.QWarranto/leafengines. 🌱 Agricultural AI: Soil analysis, crop recommendations, weather forecasts. FREE TurboQuant. This page covers its npm package (@ancientwhispers54/leafengines-mcp-server).

Is the io.github.QWarranto/leafengines MCP server safe to use?

io.github.QWarranto/leafengines scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 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.QWarranto/leafengines MCP server expose?

io.github.QWarranto/leafengines exposes 3 tools: get_soil_data, county_lookup, agricultural_intelligence. Their descriptions and schemas cost roughly 307 tokens of context every time the server is loaded.

Is the io.github.QWarranto/leafengines MCP server still maintained?

io.github.QWarranto/leafengines is still listed as active in the MCP registry. We last reached this channel on 20 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.QWarranto/leafengines MCP server under?

io.github.QWarranto/leafengines declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.