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.

中国 AI 合规与备案（条文级自查）

REMOTE · SAVANTCAT.CN · SCANNED SEP 24

生成式AI备案、AI生成内容标识、深度合成、算法备案：条文级问答 + 应办事项清单（中文）

Available components

remote · savantcat.cn 75
75 Trust /100
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 Security80
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 688 tokens (~114/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the 中国 AI 合规与备案（条文级自查） MCP server?

中国 AI 合规与备案（条文级自查） is a hosted endpoint at https://savantcat.cn/mcp-compliance, 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 · savantcat.cn

# add to Claude Code
claude mcp add --transport http cn-savantcat-ai-compliance 'https://savantcat.cn/mcp-compliance'
// .cursor/mcp.json
{
  "mcpServers": {
    "cn-savantcat-ai-compliance": {
      "url": "https://savantcat.cn/mcp-compliance"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cn-savantcat-ai-compliance": {
      "type": "http",
      "url": "https://savantcat.cn/mcp-compliance"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cn-savantcat-ai-compliance]
url = "https://savantcat.cn/mcp-compliance"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cn-savantcat-ai-compliance": {
      "type": "remote",
      "url": "https://savantcat.cn/mcp-compliance",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cn-savantcat-ai-compliance --url 'https://savantcat.cn/mcp-compliance' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cn-savantcat-ai-compliance:
    url: "https://savantcat.cn/mcp-compliance"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cn-savantcat-ai-compliance": {
      "Transport": "http",
      "Url": "https://savantcat.cn/mcp-compliance"
    }
  }
}
# add to Vellum
assistant mcp add cn-savantcat-ai-compliance -t streamable-http -u 'https://savantcat.cn/mcp-compliance'
// mcp.json
{
  "mcpServers": {
    "cn-savantcat-ai-compliance": {
      "type": "http",
      "url": "https://savantcat.cn/mcp-compliance"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 18 Sept 26 72

    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 24 Sept 2026 · Probed https://savantcat.cn/mcp-compliance

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=savantcat.cn CN=Encryption Everywhere DV TLS CA - G2,OU=www.digicert.com,O=DigiCert Inc,C=US 11 Aug 2026 8 Nov 2026 RSA 2048 SHA256-RSA ce7be013207e24787f0c9c22bc11201
SANs: savantcat.cn, www.savantcat.cn
CN=Encryption Everywhere DV TLS CA - G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 27 Nov 2017 27 Nov 2027 RSA 2048 SHA256-RSA de0ffb5ee62cb61109f608c9ced5ed3

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of savantcat.cn. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
cn. present 33094 8 Verified
savantcat.cn. absent 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=(), usb=(), magnetometer=(), gyroscope=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://savantcat.cn/mcp-compliance Verified 200
http (plaintext) http://savantcat.cn/mcp-compliance HTTPS enforced 301 https://savantcat.cn/mcp-compliance
MCP tools · 6 exposed · ~563 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
filing_route ~160

判断一项 AI 服务要办哪些手续（备案/安全评估/标识），逐条给出法规依据。 Args: public_facing: 是否面向中国境内公众提供服务（仅内部使用请传 false） generates_content: 是否能生成文本/图片/音频/视频等内容 edits_face_or_voice: 是否提供人脸、人声等生物识别信息编辑功能（换脸、AI 配音、数字人） only_internal_use: 是否仅企业内部使用、不对外提供

NameTypeReqDescription
edits_face_or_voiceboolean––
generates_contentboolean––
only_internal_useboolean––
public_facingboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_requirement ~68

按 slug 取一条合规要求的完整内容（正文 + 依据条文 + 落地动作 + 常见追问）。 Args: slug: 条目标识，先用 list_topics 或 search_compliance 取得

NameTypeReqDescription
slugstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_topics ~102

列出全部合规条目的标题清单。 Args: cluster: 可选，按集群过滤。可选值 genai-interim(生成式AI暂行办法) / ai-content-label(AI生成合成内容标识) / deep-synthesis(深度合成) / algo-recommendation(算法推荐与备案) / filing-practice(备案实操)

NameTypeReqDescription
clusterstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

regulation_info ~34

获取收录法规清单（名称、发布/施行日期、条数、官方原文链接、核心要求）。

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

search_compliance ~101

按关键词检索中国 AI 合规条目，返回最相关的若干条（含结论与条文依据）。 Args: query: 检索词，如「AI 客服 备案」「AI 生成内容 标注」「训练数据 合法来源」「大数据杀熟」 top_k: 返回条数，默认 5

NameTypeReqDescription
querystringyes–
top_kinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

self_check ~98

按场景出合规自查清单：把命中条目的「落地动作」汇总成可勾选待办，并列出条文依据。 Args: scope: 场景或关键词，如「AI 客服」「营销文案 标注」「小程序 上架」「全量」； 留空则返回全量自查清单

NameTypeReqDescription
scopestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the 中国 AI 合规与备案（条文级自查） MCP server?

中国 AI 合规与备案（条文级自查） is an MCP server listed in the public MCP registry as cn.savantcat/ai-compliance. 生成式AI备案、AI生成内容标识、深度合成、算法备案：条文级问答 + 应办事项清单（中文）. This page covers its hosted endpoint (https://savantcat.cn/mcp-compliance).

Is the 中国 AI 合规与备案（条文级自查） MCP server safe to use?

中国 AI 合规与备案（条文级自查） scores 75 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 中国 AI 合规与备案（条文级自查） MCP server expose?

中国 AI 合规与备案（条文级自查） exposes 6 tools: list_topics, search_compliance, get_requirement, self_check, filing_route, regulation_info. Their descriptions and schemas cost roughly 563 tokens of context every time the server is loaded.

Does the 中国 AI 合规与备案（条文级自查） MCP server require authentication?

No. We connected to 中国 AI 合规与备案（条文级自查） without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 中国 AI 合规与备案（条文级自查） MCP server still maintained?

中国 AI 合规与备案（条文级自查） is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.