MCP servers · baneado98

import-guardian: MCP server that checks npm imports in generated code

MCP server that checks npm imports in AI-generated code for packages that do not exist or look like newly registered squats, before npm install runs.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

The server reads generated JavaScript or TypeScript, extracts every npm package the code imports, and checks each name against the npm registry. Imports of names that do not exist on npm return BLOCK, with a suggested closest real package. Packages that exist but were published recently, have no source repository, have very low downloads, or differ by one or two edits from a popular library return REVIEW. Other imports return CLEAN. Node built-ins and local paths are skipped, and subpath imports are resolved to their package name.

The publisher's concern is slopsquatting, where attackers register package names that language models invent. The publisher reports code generators referencing more than 205,000 unique non-existent package names. The check is meant to run on code an agent has just generated, before its install command is executed. The publisher also describes sibling tools for auditing an already chosen package, dependency licences and lockfiles.

The free tools are scan_code_imports, which checks a block of code, check_packages, which checks a list of names, and verify_package, which checks one name in depth. audit_lockfile is a premium tool that resolves the full dependency tree from npm, yarn, pnpm, PyPI or Go lockfiles and checks for dependency confusion, typosquats, maintainer takeover signs and risky install scripts.

Limitations and requirements

audit_lockfile is a premium tool; the other tools are listed as free. The only runtime dependency beyond the code itself is the MCP SDK. Dependency-confusion detection requires a live cross-check against the public registry, as the publisher states.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.Baneado98/import-guardian

    Catch AI-hallucinated (slopsquatted) npm imports in generated code before npm install.

    v0.3.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026