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.

SynomosAI Governance MCP

PYPI · SYNOMOSAI-GOVERNANCE-MCP

AI governance assessment: A³ scorecard, ISO 42001 evidence chain, compliance checklist, PII scan.

68 Trust /100

Last scanned (16 hours ago)

Scores higher than 61% of PyPI servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 582 tokens (~97/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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • 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 package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 53

    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 · Analysed pypi/synomosai-governance-mcp@1.2.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~582 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
a3_assess ~150

A³ 法则四维评分卡(意图/影响/可逆性/监督,各 1-5 分),返回总分(满分 20)与放行建议——AI 造/改 AI 或高影响动作发布前评估

NameTypeReqDescription
impactinteger–影响可控度:越高越安全/可回退
intentinteger–意图纯净度:越高越受控/目的越正当
oversightinteger–人类监督强度:越高越多人审介入
reversibilityinteger–可逆性:越高越容易撤销/纠偏

No output schema declared.

No examples provided.

audit_evidence_chain ~93

生成 ISO/IEC 42001 + NIST AI RMF 可审计证据工件模板(六类:决策日志/风险登记册/模型卡/变更记录/人类监督证明/事件处置台账)——为 AI 系统准备可追溯审计证据链

NameTypeReqDescription
system_namestring–AI 系统/智能体名称

No output schema declared.

No examples provided.

compliance_checklist ~70

生成 AI 治理合规清单(EU AI Act 2024/1689 相关条款 / GB/Z 185 / ISO/IEC 42001 / PIPL·GDPR)——面向自主 agent 注册就绪的自评起点,非法律意见

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gov_scan ~97

通用治理/PII 扫描:手机号、邮箱、本地路径、疑似凭据、密钥特征串 + 版权指纹缺失提示;可用 names 传指名清单(逗号分隔)

NameTypeReqDescription
namesstring–可选:指名清单(逗号分隔),命中即告警
textstring–待扫描文本

No output schema declared.

No examples provided.

lgd_knowledge ~113

LGD 全程治理论知识端点:返回三律/三查/规范出处(DOI·仓库·官网),可按主题路由到对应域论文(金融/证据/政务/链上/驾驶/数据/低空/机器人/工业/基因/教育/医械)

NameTypeReqDescription
domainstring–可选:直接指定域关键词
querystring–主题/问题,如 '金融AI' 或 '什么是三查'

No output schema declared.

No examples provided.

passport_lookup ~59

查询技能/智能体身份码与溯源(本地台账示例)——展示 AI 身份码登记格式与溯源字段

NameTypeReqDescription
skillstring–技能/智能体标识,如 example-ai-brand

No output schema declared.

No examples provided.

Install

How do I install the SynomosAI Governance MCP server?

SynomosAI Governance MCP runs locally as a PyPI package, launched with uvx synomosai-governance-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · synomosai-governance-mcp

# add to Claude Code
claude mcp add zhaoxinghua09-cell-synomosai-governance-mcp -- uvx synomosai-governance-mcp
Common questions

What is the SynomosAI Governance MCP server?

SynomosAI Governance MCP is listed in the public MCP registry as io.github.zhaoxinghua09-cell/synomosai-governance-mcp. AI governance assessment: A³ scorecard, ISO 42001 evidence chain, compliance checklist, PII scan. This page covers its PyPI package (synomosai-governance-mcp).

Is the SynomosAI Governance MCP server safe to use?

SynomosAI Governance MCP scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 SynomosAI Governance MCP server expose?

SynomosAI Governance MCP exposes 6 tools: audit_evidence_chain, a3_assess, passport_lookup, compliance_checklist, gov_scan, lgd_knowledge. Their descriptions and schemas cost roughly 582 tokens of context every time the server is loaded.

Is the SynomosAI Governance MCP server still maintained?

SynomosAI Governance MCP 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 licence is the SynomosAI Governance MCP server under?

SynomosAI Governance MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the SynomosAI Governance MCP server?

VerifyMCP ran 15 checks on SynomosAI Governance MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about SynomosAI Governance MCP: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.