@ecocitizenz/ecz-id-mcp-verifier

Name: @ecocitizenz/ecz-id-mcp-verifier
Author: EcoCitizenZ

MCPattested

v0.9.0EcoCitizenZSEE LICENSE IN LICENSE.mdUpdated 1mo agonpm GitHub

Check public ECZ-ID Resolver posture from the CLI, CI or an MCP host. Local-first, privacy-first: classifies a target, checks its public ECZ-ID Resolver posture where available, reports, explains and routes. Never inspects artifact contents, writes truth,

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.

78Downloads/wk

1mo agoLast update

Package

AuthorEcoCitizenZ

LicenseSEE LICENSE IN LICENSE.md

Version0.9.0

Sourcenpm+mcp-registry

npm@ecocitizenz/ecz-id-mcp-verifier

GitHubEcocitizenz/ecz-id-mcp-verifier

SBOMCycloneDX 1.6 ↓

Trust Status

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 · ca2029f

Dependencies60 resolved · 1 with advisories

Tool surface3 tools · none privileged

Security scan✓ Cleanv0.8.2 · 1mo agoHow well does this scan work?

MODERATE@hono/node-server@1.19.17Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`) · transitive

EvalsNone

IndexedJul 2, 2026

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

Tools

3 tools · none privileged

Statically extracted from the published packagev0.8.2 · 1mo 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.

ecz_check_targetNo description published

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

ecz_recheck_resolverNo description published

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

ecz_explain_resultNo description published

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

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

Keywords

ecz-idmcpmodel-context-protocolmcp-servermcp-verifierverifierresolverresolver-postureagent-trustai-agentpolicy-as-codesarifgithub-actionscimachine-readabletrustopsaction-envelopelocal-firstprivacy-first

Alternatives

Comparing tool surfaces…

@ecocitizenz/ecz-id-mcp-verifier

Tools

Tools exposed

No dependency coverage

Topics

Related in git & code hosting