mcp-evals

MCP Evals by mclenhard

GitHub Action for evaluating MCP server tool calls using LLM-based scoring

Live Registry Versionv2.0.1Previous: v2.0.0Published 2025-06-28

Stability Grade

B+ (86/100)

90-Day Velocity

0 releases

Stable release cadence

Dependencies

20 direct

NPM manifest

License

MIT

Verified on NPM

Recommended Exact Pin: npx -y mcp-evals@2.0.1

NPM Registry ->GitHub Repo ->

TL;DR Verdict & Quick Citation Summary (2026-10-24)Source: AgentBreakWatch Live NPM Index

MCP Evals (mcp-evals) is currently at v2.0.1 on NPM (published 2025-06-28), with a 90-day stability score of 86/100 (B+) and MEDIUM schema drift risk across 0 releases in the past 90 days. Built on MCP SDK (^1.11.0); recent release v2.0.1 (up from v2.0.0) updates MCP DevTool / Inspector tool schemas and transport handling (0 releases in last 90d). Pin exact version v2.0.1 in .mcp.json to avoid silent parameter drift. Production teams should pin npx -y mcp-evals@2.0.1 rather than using unpinned @latest tags.

Breaking Changes & Tool Schema Drift Analysis

Built on MCP SDK (^1.11.0); recent release v2.0.1 (up from v2.0.0) updates MCP DevTool / Inspector tool schemas and transport handling (0 releases in last 90d). Pin exact version v2.0.1 in .mcp.json to avoid silent parameter drift.

Watched Exports / MCP Tool Signatures:

mcp-evaltools/listtools/call

Before (Deprecated / Unpinned Pattern)

"mcp-evals": {
  "command": "npx",
  "args": ["-y", "mcp-evals@latest"]
}

After (Verified v2.0.1 Pattern)

"mcp-evals": {
  "command": "npx",
  "args": ["-y", "mcp-evals@2.0.1"]
}

Frequently Asked Questions: mcp-evals

What is the latest version of mcp-evals on NPM?

As of 2026-10-24, the latest stable version of mcp-evals (MCP Evals by mclenhard) on NPM is v2.0.1, published on 2025-06-28. It has shipped 0 releases in the last 90 days.

Does mcp-evals v2.0.1 have breaking changes or MCP schema drift risk?

mcp-evals currently carries a MEDIUM schema drift risk rating with a Stability Score of 86/100 (Grade B+). Built on MCP SDK (^1.11.0); recent release v2.0.1 (up from v2.0.0) updates MCP DevTool / Inspector tool schemas and transport handling (0 releases in last 90d). Pin exact version v2.0.1 in .mcp.json to avoid silent parameter drift.

How do I safely pin mcp-evals in production?

Avoid unpinned @latest tags in production agent configs. Pin the exact verified version using `npx -y mcp-evals@2.0.1` and monitor mcp-eval, tools/list, tools/call for parameter or schema changes.

30-Min Registry & Schema Poller