Bazi MCP
Claim ownership, trigger a revalidation, update metadata, and inspect exactly where points are being lost.
shuangzixing1976/bazi-mcp
v1.0.313.Where points are being lost
| Component | Current | Points missing |
|---|---|---|
| Transport Compliance | 0/4 | -4.0 |
| Tool Surface Design | 0/4 | -4.0 |
| Tool Snapshot Churn | 0/4 | -4.0 |
| Tool Namespace Clarity | 0/4 | -4.0 |
| Tool Capability Clarity | 0/4 | -4.0 |
| Session Semantics | 0/4 | -4.0 |
| Schema Completeness | 0/4 | -4.0 |
| Result Shape Stability | 0/4 | -4.0 |
| Recovery Semantics | 0/4 | -4.0 |
| OAUTH Interop | 0/4 | -4.0 |
| Input Sanitization Safety | 0/4 | -4.0 |
| Error Contract | 0/4 | -4.0 |
Is this your server?
Start with a GitHub repo or email. This records owner intent before the full GitHub, DNS, HTTP, or MCP metadata challenge.
Claim server
Revalidate now
Update metadata
Maintainer annotations
Attach changelog links, incident notes, support links, or explicit tool-change notes so Verify can show maintainer context next to live probes.
Continuous Verify plan
Self-serve publisher setup: claim server, verify ownership, pick a plan, get a badge, configure alerts, trigger revalidation, and track usage through the API response.
Badge
Verified publishers can embed the live score and trust badges after claim verification.
[](https://verify.sentinelsignal.io/servers/shuangzixing1976/bazi-mcp)
Premium authenticated validation
Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.
API responses
No request submitted yet.