@mockzilla/mcp

MCPattested
v0.2.26io.github.mockzillaMITUpdated 5d agonpmGitHub

MCP server for Mockzilla (github.com/mockzilla/mockzilla-mcp). Lets Claude, Cursor, and Gemini CLI install the Mockzilla CLI, run local mock servers from OpenAPI specs, and mock individual endpoints, no account needed. Log in from the agent to deploy host

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.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
473Downloads/wk
5GitHub stars
5d agoLast update
Reads these credentials
  • MOCKZILLA_TOKENAPI keyoptional

    API key (mz_*) to use instead of logging in with the login tool, for machines without a browser. Leave unset to log in from your agent.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.mockzilla
LicenseMIT
Version0.2.26
Sourcenpm+mcp-registry
npm@mockzilla/mcp
GitHubmockzilla/mockzilla-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—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)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 8f57f44
Dependencies✓ 0 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv0.2.25 · 6d agoHow well does this scan work?
EvalsNone
IndexedSep 15, 2026

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

Tools

No tool declarations found in the source6d ago

Forge read 14 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

MCP server for Mockzilla (github.com/mockzilla/mockzilla-mcp). Lets Claude, Cursor, and Gemini CLI install the Mockzilla CLI, run local mock servers from OpenAPI specs, and mock individual endpoints, no account needed. Log in from the agent to deploy host

Keywords
mockzillamcpmodel-context-protocolclaudeclaude-codeclaude-desktopcursorgemini-cliopenapimockmock-serverapi-mockingapi-simulationapi-testingci-cddeveloper-toolsai-tools
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-17 — observed resolution, not a publisher declaration.

0 packages resolved · 0 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

This package declares no runtime dependencies.

Topics

Related in testing & ci