mcp-zebrunner

MCPcommunity
v9.2.1io.github.maksimsarychauUnknownUpdated 3mo agonpmGitHub

Advanced analytics, reporting, and safe mutations for Zebrunner. 64 tools, 14 resources, 17 prompts.

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 →
3mo agoLast update
Package
Authorio.github.maksimsarychau
LicenseUnknown
Version9.2.1
Sourcenpm+mcp-registry
npmmcp-zebrunner
GitHubmaksimsarychau/mcp-zebrunner
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—
Dependencies60 resolved · 1 with advisories
Tool surface23 tools · 2 privileged
Security scan⚠ Warnings (1)v9.2.1 · 2mo agoHow well does this scan work?
HIGHsharp@0.34.5sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591
EvalsNone
IndexedJul 9, 2026

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

Tools

23 tools · 2 privileged
Statically extracted from the published packagev9.2.1 · 2mo 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.

pass-rateNo description published

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

runtime-efficiencyNo description published

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

automation-coverageNo description published

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

executive-dashboardprivilegedNo description published

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

release-readinessNo description published

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

suite-coverageNo description published

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

review-test-caseNo description published

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

launch-triageNo description published

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

relaunch-regression-failuresNo description published

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

feature-scoped-launchNo description published

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

flaky-reviewNo description published

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

find-duplicatesNo description published

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

daily-qa-standupNo description published

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

automation-gapsNo description published

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

project-overviewNo description published

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

regression-summaryNo description published

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

session-metricsNo description published

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

quality_dashboardNo description published

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

coverageNo description published

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

pass_rateNo description published

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

runtime_efficiencyNo description published

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

executive_dashboardprivilegedNo description published

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

release_readinessNo description published

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

0 of 23 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

Advanced analytics, reporting, and safe mutations for Zebrunner. 64 tools, 14 resources, 17 prompts.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

19 tools · 2 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.