Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

REMOTE · WEB3PROJECT.TOP

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

Available components

64 Trust /100

Last scanned (16 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 313 tokens (~62/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Schema quality: 95 → 62 ▲ functional
    • Server version: 0.3.0 → 0.4.0 functional
    • New tool “explain_rule” functional
    • New tool “list_rules” functional
    • New tool “scan_to_sarif” functional
  • 20 Nov 26 +3
    • Schema quality: 88 → 190 ▼ functional
    • Server version: 0.2.0 → 0.3.0 functional
    • New tool “scan_public_repo” functional
  • 18 Nov 26 +3
    • HSTS header: fail → pass ▲ security
  • 17 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 58

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://web3project.top/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=web3project.top CN=YE2,O=Let's Encrypt,C=US 20 Nov 2026 18 Feb 2027 ECDSA 256 ECDSA-SHA384 6d17e62001f513dfc0504b7dbc27a0b347e
SANs: web3project.top
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of web3project.top. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
top. DS published 41508 13 Verified
web3project.top. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://web3project.top/mcp Verified 200
http (plaintext) http://web3project.top/mcp HTTPS enforced 308 https://web3project.top/mcp
MCP tools · 5 exposed · ~273 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explain_rule ~30

查询单条规则的严重度、含义与修复建议

NameTypeReqDescription
rulestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_rules ~29

列出扫描器的全部规则(规则 id、严重度、说明、修复建议)

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

scan_mcp_server ~48

审计一个 MCP server 项目(本地路径)的安全风险,返回结构化风险清单

NameTypeReqDescription
include_testsboolean––
pathstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

scan_public_repo ~102

扫描任意公开仓库(github.com / gitlab.com / gitee.com)里的 MCP server 安全风险。直接传仓库 URL,无需下载、无需本地路径。返回按严重度汇总的摘要 + 最多 3 条明细;完整报告(含修复建议/SARIF/CI 模板)见 https://web3project.top/mcp-audit

NameTypeReqDescription
repo_urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

scan_to_sarif ~64

扫描本地路径或公开仓库并直接返回 SARIF 2.1.0 文档,可上传 GitHub code scanning

NameTypeReqDescription
include_testsboolean––
pathstring––
repo_urlstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the mcp-audit — MCP static scan (SARIF + CI) server?

mcp-audit — MCP static scan (SARIF + CI) is a hosted endpoint at https://web3project.top/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · web3project.top

# add to Claude Code
claude mcp add --transport http top-web3project-mcp-audit 'https://web3project.top/mcp'
Common questions

What is the mcp-audit — MCP static scan (SARIF + CI) server?

mcp-audit — MCP static scan (SARIF + CI) is listed in the public MCP registry as top.web3project/mcp-audit. Static MCP server scan: injection, secrets, tool poisoning. SARIF + rules catalog. This page covers its hosted endpoint (https://web3project.top/mcp).

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

mcp-audit — MCP static scan (SARIF + CI) scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

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

mcp-audit — MCP static scan (SARIF + CI) exposes 5 tools: scan_mcp_server, scan_public_repo, list_rules, scan_to_sarif, explain_rule. Their descriptions and schemas cost roughly 273 tokens of context every time the server is loaded.

Does the mcp-audit — MCP static scan (SARIF + CI) server require authentication?

No. We connected to mcp-audit — MCP static scan (SARIF + CI) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the mcp-audit — MCP static scan (SARIF + CI) server still maintained?

mcp-audit — MCP static scan (SARIF + CI) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the mcp-audit — MCP static scan (SARIF + CI) server?

VerifyMCP ran 12 checks on mcp-audit — MCP static scan (SARIF + CI), covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about mcp-audit — MCP static scan (SARIF + CI): Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.