wigolo

MCP@KnockOutEZ
v0.2.1Towhid KhanAGPL-3.0-onlyUpdated 2mo agonpmGitHub

Local-first web intelligence MCP server for AI coding agents

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.

@KnockOutEZ
Identity-verified publisher GitHub@KnockOutEZ
Verified Jul 16, 2026
2kDownloads/wk
2mo agoLast update
Package
AuthorTowhid Khan
LicenseAGPL-3.0-only
Version0.2.1
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
Listed in Forge index+10/10
Publisher identity verified+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
Publisher@KnockOutEZ
SignatureUnsigned
Domain
Provenance✓ Sigstore-verified · 185afb5
Dependencies60 resolved · 2 with advisories
Tool surface
Security scan⚠ Warnings (2)v0.2.1 · 26d agoHow well does this scan work?
EvalsNone
IndexedJul 14, 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 source26d ago

Forge read 300 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

Local-first web intelligence MCP server for AI coding agents

Keywords
mcpmcp-serverweb-searchweb-scrapingai-agentlocal-firstcontent-extractionsearchscrapingcrawlerclaudeagent-tools
Alternatives
Comparing tool surfaces…

Dependency tree

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

60 packages resolved · 28 direct · 2 carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

90 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+78 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in search & retrieval