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.MukundaKatta/jmespath-mcp

NPM · @MUKUNDAKATTA/JMESPATH-MCP · SCANNED AUG 5

Run JMESPath queries against JSON. Pure JS, no native binary needed.

+24 this week 70 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 Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), 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 (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT OR Apache-2.0).Pass
  • Actively maintained (last published 86 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 118 tokens (~118/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 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 · @mukundakatta/jmespath-mcp

# add to Claude Code
claude mcp add mukundakatta-jmespath-mcp -- npx -y @mukundakatta/jmespath-mcp
# add to Codex CLI
codex mcp add mukundakatta-jmespath-mcp -- npx -y @mukundakatta/jmespath-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mukundakatta-jmespath-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mukundakatta/jmespath-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mukundakatta-jmespath-mcp --command npx --arg -y --arg @mukundakatta/jmespath-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mukundakatta-jmespath-mcp:
    command: "npx"
    args: ["-y", "@mukundakatta/jmespath-mcp"]
// mcp.json
{
  "mcpServers": {
    "mukundakatta-jmespath-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mukundakatta/jmespath-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.

  • 5 Aug 26 +1
    • CVE-2026-69207 no longer affects this package security
    • Known CVEs: fail → partial security
  • 4 Aug 26 −1
    • CVE-2026-69207 affects this package: medium security
    • Known CVEs: partial → fail security
  • 3 Aug 26 +4
    • Stability: unverified → 0.27 functional
  • 2 Aug 26 +45
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Maintenance: unverified → pass functional
    • Licence: MIT OR Apache-2.0 functional
  • 1 Aug 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 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 5 Aug 2026 · Analysed npm/@mukundakatta/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 94 deprecated · 30 stale.

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

MCP tools — 1 exposed · ~118 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
json_query ~118

Run a JMESPath expression against JSON. Use for deep traversal, projections (e.g. people[*].name), filters (locations[?state == 'WA']), pipes, and built-in functions (length, sort, contains). Pure-JS implementation, no jq binary needed.

NameTypeReqDescription
datayesJSON to query. Pass as a JSON string OR a pre-parsed value.
expressionstringyesJMESPath expression. Examples: foo.bar | items[*].name | locations[?state=='WA'].name | length(@).

No output schema declared.

No examples provided.