io.github.dbsectrainer/mcp-eval-runner

MCPcommunity
v1.0.0io.github.dbsectrainerUnknownUpdated 6mo agonpmGitHub

A standardized testing harness for MCP servers and agent workflows

A standardized testing harness for MCP servers and agent workflows. Define test cases as YAML fixtures (steps → expected tool calls → expected outputs), run regression suites directly from your MCP client, and get pass/fail results with diffs — without leaving Claude Code or Cursor. Tool reference | Configuration | Fixture format | Contributing | Troubleshooting | Design principles YAML fixtures:…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
6mo agoLast update
Package
Authorio.github.dbsectrainer
LicenseUnknown
Version1.0.0
Sourcemcp-registry
npmmcp-eval-runner
GitHubdbsectrainer/mcp-eval-runner
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · 1 privileged
Security scan✓ Cleanv1.0.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · 1 privileged
Statically extracted from the published packagev1.0.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

run_suiteNo description published

This tool published no description. Forge does not invent one.

run_caseNo description published

This tool published no description. Forge does not invent one.

list_casesNo description published

This tool published no description. Forge does not invent one.

create_test_caseNo description published

This tool published no description. Forge does not invent one.

regression_reportNo description published

This tool published no description. Forge does not invent one.

compare_resultsNo description published

This tool published no description. Forge does not invent one.

generate_html_reportNo description published

This tool published no description. Forge does not invent one.

scaffold_fixtureNo description published

This tool published no description. Forge does not invent one.

evaluate_deployment_gateprivilegedNo description published

This tool published no description. Forge does not invent one.

discover_fixturesNo description published

This tool published no description. Forge does not invent one.

0 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

A standardized testing harness for MCP servers and agent workflows. Define test cases as YAML fixtures (steps → expected tool calls → expected outputs), run regression suites directly from your MCP client, and get pass/fail results with diffs — without leaving Claude Code or Cursor. Tool reference | Configuration | Fixture format | Contributing | Troubleshooting | Design principles YAML fixtures: Test cases are plain files in version control — diffable, reviewable, and shareable. Two execution…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

10 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.