Skip to content

net.bigfloppy.vibescan/vibescan

net.bigfloppy.vibescan/vibescanvibescan.bigfloppy.netstreamable-httpv1.0.0Scanned

Free security scan for AI-written GitHub repos: leaked keys, .env, eval, SQLi, CORS.

1 tool: 1 change things.

Tools: 0 delete, 0 irreversible, 1 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding, 1 high

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

1 tool

Changes things 1Claude Code: ask
  • scan_repoScan a public GitHub repo (owner/repo or URL) for leaked secrets, .env files, eval, SQLi, CORS and other risky patterns common in AI-written code.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • High

      The description refers to ".env".

      Matched text

      description: "...(owner/repo or URL) for leaked secrets, .env files, eval, SQLi, CORS and other risky..."

      What this check looks for
    Description, as the server wrote it
    Scan a public GitHub repo (owner/repo or URL) for leaked secrets, .env files, eval, SQLi, CORS and other risky patterns common in AI-written code.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

1 high
  • The description refers to ".env".

    Matched text

    description: "...(owner/repo or URL) for leaked secrets, .env files, eval, SQLi, CORS and other risky..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http vibescan https://vibescan.bigfloppy.net/mcp
claude mcp add --transport http vibescan https://vibescan.bigfloppy.net/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__vibescan__scan_repo"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vibescan. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/net.bigfloppy.vibescan/vibescan/verify?hash=54ec23a6158b7ae5bf8bfc002d2521db3ff0f2b9302a97f79da62a2d0694ebf6" | jq -e '.changed == false'

Pinned hash 54ec23a6158b, from Oct 29, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/net.bigfloppy.vibescan/vibescan/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for net.bigfloppy.vibescan/vibescan
[![anlyon.dev](https://anlyon.dev/badge/net.bigfloppy.vibescan/vibescan.svg)](https://anlyon.dev/servers/net.bigfloppy.vibescan/vibescan)

Source: MCP Registry · repository. Synced Oct 29, 2026, 03:18 UTC.