io.github.zhaoxinghua09-cell/uibc-core
PYPI · UIBC-CORE
UIBC Core: three-valued verdicts and Ed25519 seals for agent lifecycle evidence.
Available components
Last scanned (12 hours ago)
Scores higher than 58% of PyPI servers
Category Security
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: at least one of this release's files carries no attestation we credit (SLSA provenance or PyPI's publish attestation), so the release as a whole is not verified. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 401 tokens (~57/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 27% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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 +15
- Malware scan: unverified → pass ▲ security
- 20 Nov 26 +1
- Provenance: Provenance check failed: at least one of this release's files carries no attestation we credit (SLSA provenance or PyPI's publish attestation), so the release as a whole is not verified. security
- Package version: 0.4.1 → 0.5.0 functional
- 19 Nov 26 0
- Package version: 0.4.0 → 0.4.1 functional
- 18 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Provenance: Provenance check failed: no build-provenance attestation is published. security
- Package version: 0.3.3 → 0.4.0 functional
- 16 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Provenance: Provenance check failed: at least one of this release's files carries no attestation we credit (SLSA provenance or PyPI's publish attestation), so the release as a whole is not verified. security
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.3.0 → 0.3.3 functional
- Package version: 0.3.0 → 0.3.2 functional
- 13 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Nov 26 47
First indexed and scored.
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/uibc-core@0.5.0
Provenance Unverified
The package claims build provenance, but we could not verify that claim, so it earns no credit.
| Result | Unverified |
|---|---|
| Ecosystem | pypi |
| Reason | A file is unattested |
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 →
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 →
cert_verify ~48
Verify an UIBC certificate (C1-C7); optional package binding check.
| Name | Type | Req | Description |
|---|---|---|---|
| cert_path | string | yes | – |
| key_hex | string | yes | – |
| package_dir | string | – | – |
No output schema declared.
No examples provided.
gate_check ~100
Governed decision: ALLOW/DENY/HOLD (mirrors CLI gate, exit 0/2/3). Honors signed revocation; disputes annotate only.
| Name | Type | Req | Description |
|---|---|---|---|
| dispute_path | string | – | – |
| key_hex | string | – | – |
| path | string | yes | – |
| pubkey_hex | string | – | Ed25519 public key, 64-char hex (optional, pins the expected signer) |
| revocation_path | string | – | – |
No output schema declared.
No examples provided.
get_identity ~29
Read a package identity.json (API category IDENTITY, read-only).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
inspect_package ~30
Human-readable package summary (agent, status, events, evidence, root).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
list_events ~32
Read a package lifecycle event chain (API category LIFECYCLE, read-only).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
list_evidence ~34
Read a package evidence index with content hashes (API category EVIDENCE, read-only).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
verify_package ~128
Verify a sealed .uibc package: S1-S6. Pass key_hex for strict mode (unsigned/forged/substituted seals FAIL at S6); omit for open mode. Read-only. Result is three-valued: PASS/FAIL/INCONCLUSIVE.
| Name | Type | Req | Description |
|---|---|---|---|
| key_hex | string | – | owner seal key, 64-char hex (optional, enables strict mode) |
| path | string | yes | package directory |
| pubkey_hex | string | – | Ed25519 public key, 64-char hex (optional, pins the expected signer; a substituted key FAILS S6) |
No output schema declared.
No examples provided.
How do I install the io.github.zhaoxinghua09-cell/uibc-core MCP server?
io.github.zhaoxinghua09-cell/uibc-core runs locally as a PyPI package, launched with uvx uibc-core. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · uibc-core
claude mcp add zhaoxinghua09-cell-uibc-core -- uvx uibc-core
What is the io.github.zhaoxinghua09-cell/uibc-core MCP server?
io.github.zhaoxinghua09-cell/uibc-core is an MCP server listed in the public MCP registry as io.github.zhaoxinghua09-cell/uibc-core. UIBC Core: three-valued verdicts and Ed25519 seals for agent lifecycle evidence. This page covers its PyPI package (uibc-core).
Is the io.github.zhaoxinghua09-cell/uibc-core MCP server safe to use?
io.github.zhaoxinghua09-cell/uibc-core scores 66 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 io.github.zhaoxinghua09-cell/uibc-core MCP server expose?
io.github.zhaoxinghua09-cell/uibc-core exposes 7 tools: verify_package, gate_check, inspect_package, cert_verify, get_identity, and 2 more. Their descriptions and schemas cost roughly 401 tokens of context every time the server is loaded.
Is the io.github.zhaoxinghua09-cell/uibc-core MCP server still maintained?
io.github.zhaoxinghua09-cell/uibc-core 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 io.github.zhaoxinghua09-cell/uibc-core MCP server under?
io.github.zhaoxinghua09-cell/uibc-core declares the Apache-2.0 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 io.github.zhaoxinghua09-cell/uibc-core MCP server?
VerifyMCP ran 16 checks on io.github.zhaoxinghua09-cell/uibc-core, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.