_ registry / mcp + a2a http-sse · checked 2h ago

savantcat-ai-compliance

https://savantcat.cn

Registry code: 2f325143d05b74d0

api record

合尘猫 · 中国 AI 合规与备案知识库。收录《生成式人工智能服务管理暂行办法》《人工智能生成合成内容标识办法》《互联网信息服务深度合成管理规定》《互联网信息服务算法推荐管理规定》的逐条要求,回答「要不要备案」「要不要标注 AI 生成」「AI 客服上线前要做什么」「用第三方大模型 API 义务在谁身上」这类问题。所有结论均标注法规条文依据,并用 filing_route 给出应办事项清单。

endpoint
https://savantcat.cn/mcp-compliance
door code
9fbc1edb2940cb6f
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is savantcat-ai-compliance live?
Yes — it answered the hub's last check (checked 2h ago). It answered 85% of checks over the last 30 days.
Is savantcat-ai-compliance free to use?
Yes — the hub reached it with no key and no payment.
What tools does savantcat-ai-compliance have?
8 tools: search_compliance, get_article, get_requirement, search_articles, list_topics, self_check, regulation_info, filing_route.
Is savantcat-ai-compliance safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
84.5%

90 days 85%· all time 86.1%

latency
1,359ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1069 checks · signed record
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • answer questions on the chinese ai customer service standard
  • get a compliance self-check list
  • search compliance q&a
takes → gives
text → text
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
4 open 4 never probed 4 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_topics open 6h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "list_topicsArguments",
      "properties": {
        "cluster": {
          "type": "string",
          "title": "Cluster",
          "default": ""
        }
      }
    }
    arguments 11 lines
  • self_check open 2h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "self_checkArguments",
      "properties": {
        "scope": {
          "type": "string",
          "title": "Scope",
          "default": ""
        }
      }
    }
    arguments 11 lines
  • regulation_info open 6h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "regulation_infoArguments",
      "properties": {}
    }
    arguments 5 lines
  • filing_route open 6h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "filing_routeArguments",
      "properties": {
        "public_facing": {
          "type": "boolean",
          "title": "Public Facing",
          "default": true
        },
        "generates_content": {
          "type": "boolean",
          "title": "Generates Content",
          "default": true
        },
        "only_internal_use": {
          "type": "boolean",
          "title": "Only Internal Use",
          "default": false
        },
        "edits_face_or_voice": {
          "type": "boolean",
          "title": "Edits Face Or Voice",
          "default": false
        }
      }
    }
    arguments 26 lines
  • search_compliance unknown 24h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "search_complianceArguments",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "title": "Query"
        },
        "top_k": {
          "type": "integer",
          "title": "Top K",
          "default": 5
        }
      }
    }
    arguments 18 lines
  • get_article unknown 2h ago

    按条号取某部法规的条文**逐字原文**,并附内容指纹与官方原文链接。 与 get_requirement 的分工:get_requirement 按「问题」取整条合规要求(含结论与落地动作); get_article 按「条号」取条文原文,用于逐字核对、引用与溯源。 Args: law: 法规名或集群标识。可写全称(《生成式人工智能服务管理暂行办法》)、 简称(标识办法 / 算法推荐规定)或 cluster (genai-interim / ai-content-label / deep-synthesis / algo-recommendation) article: 条号,支持「第十条」「10」「第10条」三种写法

    mcp-tool

    {
      "type": "object",
      "title": "get_articleArguments",
      "required": [
        "law",
        "article"
      ],
      "properties": {
        "law": {
          "type": "string",
          "title": "Law"
        },
        "article": {
          "type": "string",
          "title": "Article"
        }
      }
    }
    arguments 18 lines
  • get_requirement unknown 2h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "get_requirementArguments",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "title": "Slug"
        }
      }
    }
    arguments 13 lines
  • search_articles unknown 24h ago

    在**某一部法规内部**按关键词检索条文,返回命中条号 + 条文摘录。 用途:已经知道是哪部法规,要定位「哪一条讲了这件事」。 Args: law: 法规名或集群标识(同 get_article 的 law 参数) keywords: 检索词,如「训练数据 合法来源」「标识 元数据」「备案 十日」 top_k: 返回条数,默认 5

    mcp-tool

    {
      "type": "object",
      "title": "search_articlesArguments",
      "required": [
        "law",
        "keywords"
      ],
      "properties": {
        "law": {
          "type": "string",
          "title": "Law"
        },
        "top_k": {
          "type": "integer",
          "title": "Top K",
          "default": 5
        },
        "keywords": {
          "type": "string",
          "title": "Keywords"
        }
      }
    }
    arguments 23 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2f325143d05b74d0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2f325143d05b74d0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2f325143d05b74d0/badge.svg)](https://brick.blue/agent/2f325143d05b74d0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.