io.github.Aakashbhardwaj27/ai-scanner

Name: io.github.Aakashbhardwaj27/ai-scanner
Author: io.github.Aakashbhardwaj27

MCPcommunity

v1.0.6io.github.Aakashbhardwaj27UnknownUpdated 6mo agonpm GitHub

Scan codebases for LLM/AI SDK usage, exposed API tokens, and hardcoded secrets.

MCP server for ai-scanner - let AI agents scan codebases for LLM usage, AI frameworks, and exposed secrets. An MCP server that exposes ai-scanner as tools for AI agents. Works with Claude Code, Claude Desktop, Cursor, Windsurf, and any MCP-compatible client. | Full scan — LLM SDKs, AI frameworks, exposed tokens, and hardcoded secrets with severity levels | | Security check — pass/fail scan for…

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 →

1GitHub stars

1Forks

6mo agoLast update

Package

Authorio.github.Aakashbhardwaj27

LicenseUnknown

Version1.0.6

Sourcemcp-registry

npmai-scanner-mcp

GitHubAakashbhardwaj27/ai-scanner-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

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—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface3 tools · none privileged

Security scan✓ Cleanv1.0.3 · 3mo agoHow well does this scan work?

EvalsNone

IndexedJun 13, 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 packagev1.0.3 · 3mo 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.

scan_directoryNo description published

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

check_secretsNo description published

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

ai_inventoryNo 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

mcp

Alternatives

Comparing tool surfaces…

io.github.Aakashbhardwaj27/ai-scanner

Tools

Tools exposed

No dependency coverage