Skip to content

mcp-audit — MCP static scan (SARIF + CI)

top.web3project/mcp-auditweb3project.topstreamable-httpv0.4.0Scanned

Static MCP server scan: injection, secrets, tool poisoning. SARIF + rules catalog.

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the mcp-audit — MCP static scan (SARIF + CI) can do

The mcp-audit — MCP static scan (SARIF + CI) is published by web3project.top, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: scan_mcp_server and scan_public_repo), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 0.4.0.

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.

2 tools

Changes things 2Claude Code: ask
  • scan_mcp_server审计一个 MCP server 项目(本地路径)的安全风险,返回结构化风险清单No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    审计一个 MCP server 项目(本地路径)的安全风险,返回结构化风险清单
  • scan_public_repo扫描任意公开仓库(github.com / gitlab.com / gitee.com)里的 MCP server 安全风险。直接传仓库 URL,无需下载、无需本地路径。返回按严重度汇总的摘要 + 最多 3 条明细;完整报告(含修复建议/SARIF/CI 模板)见 https://web3project.top/mcp-auditNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    扫描任意公开仓库(github.com / gitlab.com / gitee.com)里的 MCP server 安全风险。直接传仓库 URL,无需下载、无需本地路径。返回按严重度汇总的摘要 + 最多 3 条明细;完整报告(含修复建议/SARIF/CI 模板)见 https://web3project.top/mcp-audit

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.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:20 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://web3project.top/mcp: tools/list returned 1 tool to an anonymous client, including scan_mcp_server (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. Tools1 added.+1 addedView diff

Install

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

claude mcp add --transport http audit https://web3project.top/mcp
claude mcp add --transport http audit https://web3project.top/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__audit__scan_mcp_server",
      "mcp__audit__scan_public_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 audit. 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://radar.anlyon.com/api/v1/servers/top.web3project/mcp-audit/verify?hash=380e20cd23aa85a8201e9a248867679bb7855188eec48807a48c8956b5b347f9" | jq -e '.changed == false'

Pinned hash 380e20cd23aa, from Nov 20, 2026, 03:18 UTC.

Watch

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

https://radar.anlyon.com/servers/top.web3project/mcp-audit/changes.xml

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

Badge

Anlyon Radar badge for top.web3project/mcp-audit
[![Anlyon Radar](https://radar.anlyon.com/badge/top.web3project/mcp-audit.svg)](https://radar.anlyon.com/servers/top.web3project/mcp-audit)

Source: MCP Registry. Synced Nov 20, 2026, 03:17 UTC.

mcp-audit — MCP static scan (SARIF + CI): questions and answers

Answered from the scan above, not from the publisher's description.

Is the mcp-audit — MCP static scan (SARIF + CI) safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the mcp-audit — MCP static scan (SARIF + CI) delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the mcp-audit — MCP static scan (SARIF + CI) do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the mcp-audit — MCP static scan (SARIF + CI) have?

2 tools: 2 write. scan_mcp_server and scan_public_repo.

Does the mcp-audit — MCP static scan (SARIF + CI) need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the mcp-audit — MCP static scan (SARIF + CI) send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the mcp-audit — MCP static scan (SARIF + CI) changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.