← Back to search
github-ronload/bazi-flex-mcp

ronload/bazi-flex-mcp

A Bazi (八字 / Four Pillars) MCP server that works even when the birth hour is unknown. Built on shunshi-bazi-core, with true-solar-time correction.

DECISION SUMMARY

Allow With Approval

Score
67.9
Top 0.3% of 73,547 scored public servers
Confidence
Medium
Based on evidence completeness, recency, and validation density.
Evidence age
11.2h old
Freshness: fresh. Snapshot trustsnap_3d956862c0679ec9.
Top risk drivers
  • Transport Compliance
  • Recovery Semantics
  • Dependency Supply Chain Signal
Recommended actions
  • Inspect the latest validation evidence and resolve the client-visible regression.
  • Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
  • Inspect the latest validation evidence and resolve the client-visible regression.
Production decision
Allow with approval
write/admin actions need confirmation safeguards
Current score
67.9
Snapshot trustsnap_3d956862c0679ec9
Next action
export policy, require approval for writes, add authenticated validation
Claim the profile to add evidence, trigger validation, and configure monitoring.
Compare alternatives Export policy Open report JSON
Observed Attention
No observed attention
No observed attention in the current 30-day window.
  • No segmented attention signals observed in the current window.
Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.
Status
Healthy
Score
67.9
Transport
streamable-http
Tools
2

Current trust snapshot

Snapshot ID
trustsnap_3d956862c0679ec9
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Aug 04, 2026 02:18:43 PM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Aug 04, 2026 03:07:40 AM UTC
Age: 11.18h • freshness band: Verified in last 24h • display score: 67.87
Production trust decision
Allow with approval
write/admin actions need confirmation safeguards
Readiness class
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.

Canonical machine links

SERVER OWNER FUNNEL

Own this MCP?

Claim ownership, prove control with a GitHub, DNS, HTTP, MCP metadata, or email-domain challenge, revalidate now, publish a badge, configure monitoring, and unlock a verified server profile.

1. Claim
unclaimed
with GitHub, DNS, or HTTP challenge instructions.
2. Revalidate
POST /v1/servers/github-ronload/bazi-flex-mcp/revalidate
Verified owners get priority queueing after proof succeeds.
3. Badge
Verified by MCP Verify badge
Verified by MCP Verify - score 67.9 - last checked Aug 4, 2026
4. Monitor
Continuous Verify plan is self-serve: choose a tier, configure watches, add authenticated validation, trigger revalidation, and use the badge.
Paid profile
Add verified publisher identity, security metadata, evidence packs, badge customization, and owner analytics without buying a better score.
Badge embed
[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/github-ronload/bazi-flex-mcp.svg)](https://verify.sentinelsignal.io/servers/github-ronload/bazi-flex-mcp)
PUBLISHER READINESS

Publisher readiness checklist

4/7 readiness checks currently pass. Paid status never changes the objective score; it can add evidence, monitoring, badge analytics, and authenticated validation.

Publisher readiness checks for this MCP server
CheckStatusHow to improve
Ownership verified Needs work Prove GitHub, DNS, HTTP, MCP metadata, or domain-email control.
Fresh validation Ready Keep public evidence inside the 48h publisher launch window.
Healthy endpoint Ready Remote endpoint should initialize and list tools reliably.
Score threshold Needs work Aim for score >= 70 before using production-readiness language.
Metadata complete Ready Publish description, homepage/docs, remote URL, and support metadata.
Risk posture reviewed Needs work Address OAuth, write-action, destructive-tool, and protocol findings.
Badge ready Ready Publish score and freshness badges only when current evidence exists.

Scan or claim this server Open badge kit

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Freshness band
Verified in last 24h
Policy SLA: 168.0h • confidence-weighted score: 51.8 • stale score suppressed:
Policy exports
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/decide
Returns allowed tools, blocked tools, approval requirement, and reason.
Hosted runtime
Deploy trusted servers from GitHub with secrets, egress controls, releases, rollback, and audit events.
Authenticated validation
Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.
Active trust badges
Freshly Validated Claude Remote MCP Compatible No Critical Risk
Semantic benchmarks
available
Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.
Supply chain
metadata signal
Deep scan checks are marked separately from public metadata signals.
Compliance metadata
Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.
Alert subscription types
Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes

MCP Runtime hosting

Verify Hosted MCP turns a trusted server report into a managed remote MCP endpoint with GitHub deployment provenance, sandbox policy, encrypted secrets, release history, rollback, and audit/usage events.

Activation readiness
Trusted hosted runtimes require fresh validation, a passing server state, a remote endpoint, and a minimum score.
Minimum tier
TrustOps
Publisher claim plus paid TrustOps tier are required before secrets or releases can be created.
Hosted endpoint
/hosted/{namespace}/{name}/mcp
The endpoint enforces egress allowlists and records audit/usage events.
Blockers
score_below_hosting_threshold
DeploymentStatusEndpointRelease
No hosted runtime deployments yet.

Production readiness class

Production readiness class
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
Critical alerts
0
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
76.2
Based on 1 recent validations, 26 captured checks, and validation age of 11.2 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
11.2h
Lower age means fresher evidence.

Recommended for

Claude Desktop
Claude Desktop is marked compatible with score 83.
Smithery
Smithery is marked compatible with score 100.
Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 100.

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Client compatibility: ChatGPT
Partially client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeError
  • step_up_auth_probeMissing
  • connector_replay_probeMissing — Frozen tool snapshots must survive refresh.
  • request_association_probeMissing — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Client-compatible
Transport behavior should match Claude-compatible HTTP expectations.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeError
Write-action publishing
Publishing blocked
Blocked until safeguards and confirmation semantics are verified for write, exec, or destructive tools.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeError
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: high (76.25)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probeMissing
  • connector_replay_probeMissing

Why compatibility is limited by client

ChatGPT custom connector
Partially client-compatible
Remediation checklist
  • OpenAI connectors expect OAuth for remote server auth.
  • Dynamic client registration materially improves connector setup.
  • Transport compliance should be in good shape.
  • search fetch only is not yet satisfied
  • oauth configured is not yet satisfied
  • admin refresh required is not yet satisfied
Claude remote MCP
Client-compatible
Remediation checklist
  • Transport behavior should match Claude-compatible HTTP expectations.
  • search fetch only is not yet satisfied
  • oauth configured is not yet satisfied
  • admin refresh required is not yet satisfied
  • safe for company knowledge is not yet satisfied
  • safe for messages api remote mcp is not yet satisfied
Write-safe publishing
Blocked
Remediation checklist
  • Add a clearer auth boundary around risky write actions.
  • Add confirmation or dry-run semantics for risky actions.

Verdict traces

Production verdict
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
Confidence: high (76.25)
Winning source: live_validation
Triggering alerts
  • No active alert triggers.
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Partially client-compatible initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Client-compatible initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Publishing blocked action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none

Publishability policy profiles

ChatGPT custom connector compatibility
Compatible with review
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Connector-compatible
Transport behavior should match Claude-compatible HTTP expectations. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
Transport behavior should match Claude-compatible HTTP expectations.
  • remote_transport: Passes
  • tool_discovery: Passes
  • auth_connect: Passes
  • safe_write_review: Degraded

Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Latest profile
remote_mcp
Authenticated session used
Public score isolation
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview

Public server reputation

Validation success 7d
1.0
Validation success 30d
1.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0

Incident & change feed

TimestampEventDetails
Aug 04, 2026 03:07:40 AM UTC Latest validation: healthy Score 67.9 with status healthy.

Capabilities

Use-case taxonomy
development search communication productivity

Security posture

Tools analyzed
2
High-risk tools
0
Destructive tools
1
Exec tools
0
Egress tools
0
Secret tools
0
Bulk-access tools
0
Risk distribution
medium:2

Agent Commerce & Payment Readiness - Beta

Beta assessment. Verify separates commerce-adjacent context from observed payment execution. Usage, billing, pricing, card, wallet, or meter terms alone do not make a server payment-capable. This is not a certification of safety, compliance, or fraud prevention.

Overall
None
Auth posture
10
Payment readiness
10
Delegation safety
50
Tool risk
70
Commerce signal: weak Payment capable: none Payment execution: no Billing/usage context: no Quote/pricing context: no Numeric price context: yes Commercial quote context: no Checkout/charge signal: no Checkout term observed: no Human confirmation: unknown Spending policy: yes Receipt support: unknown Auth required: no Operator identity: declared Tool risk: administrative Delegation level: none
Detected payment rails
none detected
Purchase stages
none detected
Evidence level
inferred
Confidence
low

Warnings

No commerce-specific warnings generated.

Evidence

FieldValueSourceMatched termsConfidence
commerce_signalweakserver_metadatalimit, ratelow

Recommended operator fixes

Tool capability & risk inventory

ToolCapabilitiesRiskFindingsNotes
getBaziChart read write delete Medium destructive operation No explicit safeguard hints detected.
getBaziChartPartial read write network admin Medium admin mutation No explicit safeguard hints detected.

Write-action governance

Governance status
Error
Safe to publish
Auth boundary
public_or_unclear
Blast radius
Medium
High-risk tools
0
Confirmation signals
none
Safeguard count
0

Status detail: 1 destructive tool(s) are exposed without a clear auth boundary; no safeguards or confirmation signals detected.

ToolRiskFlagsSafeguards
No high-risk tools were detected on the latest run.

Action-controls diff

Snapshot changed
no
Disabled-by-default candidates
none
Manual review candidates
none
New actions
ActionRiskFlags
No newly added actions.
Changed actions
ActionChange typesRisk
No materially changed actions.

Why this score?

Access & Protocol
30/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
32.83/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
27/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
18.75/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
19.45/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
5/8
Adoption clues and public evidence that the server is intended for external use.

Algorithmic score breakdown

Auth Operability
2/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
2.8/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
2/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
2/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
4/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
4/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
4/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
1.8/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
4/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
2/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
2/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
4/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
4/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
4/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
3/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
2/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
3/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
4/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
3/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
4/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
2/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
3/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
3/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
0/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
2/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
2/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
3/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
3/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
3/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
3/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
2/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
3/4
Whether the server appears directly or indirectly in the official MCP registry.
Provenance Divergence
4/4
How closely official registry metadata, the live server card, and public repo/package signals agree with each other.
Safety Transparency
2/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
4/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
2/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
4/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
2/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
3/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
0.5/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
3/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
3/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

Compatibility profiles

OpenAI Connectors
66.7
partial
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
Connector URL: https://bazi-flex.ronaldluo.com/mcp
# No OAuth metadata detected.
# Server: github-ronload/bazi-flex-mcp
Claude Desktop
83.3
compatible
Transport behavior should match Claude-compatible HTTP expectations.
{
  "mcpServers": {
    "bazi-flex-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://bazi-flex.ronaldluo.com/mcp"]
    }
  }
}
Smithery
100.0
compatible
No major blockers detected.
smithery mcp add "https://bazi-flex.ronaldluo.com/mcp"
Generic Streamable HTTP
100.0
compatible
No major blockers detected.
curl -sS https://bazi-flex.ronaldluo.com/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Actionable remediation

SeverityRemediationWhy it mattersRecommended action
High Add confirmation and dry-run semantics for risky actions High-risk write, delete, exec, or egress tools should communicate safeguards clearly. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Associate roots, sampling, and elicitation with active client requests Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Expose /.well-known/oauth-protected-resource Without a protected-resource document, OAuth clients cannot discover auth requirements reliably. Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Playbook
  • Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint.
  • Point it at the authorization server metadata URL.
  • Confirm clients receive consistent auth hints before tool execution.
High Keep connector refreshes backward compatible Managed connector clients freeze tool snapshots, so removed tools, new required args, and breaking output changes can break published integrations after refresh. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Publish a complete server card Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.
Playbook
  • Publish `/.well-known/mcp/server-card.json`.
  • Include homepage, repository, support, tools, prompts/resources, and auth metadata.
  • Revalidate the server after publishing the card.
High Stop asking users to paste secrets directly Public MCP servers should prefer OAuth or browser-based auth guidance over in-band secret collection. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Reduce tool-surface churn Frequent add/remove or output-shape drift makes published connectors and cached tool snapshots brittle. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Repair prompts/list or stop advertising prompts Prompt metadata should either work live or be removed from the advertised capability set. Only advertise prompts if prompts/list works and prompt arguments are documented.
Playbook
  • Only advertise prompts that are actually accessible.
  • Add prompt descriptions and argument docs.
  • Run a live `prompts/list` check after any prompt changes.
Medium Repair resources/list or stop advertising resources Resource metadata should either work live or be removed from the advertised capability set. Only advertise resources if resources/list works and resources expose stable URIs/types.
Playbook
  • Only advertise resources with stable URIs and read semantics.
  • Add MIME/type hints where possible.
  • Run a live `resources/list` and `resources/read` check after updates.
Medium Support resumable HTTP sessions cleanly Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Publish or reconcile the server in the official MCP registry Official registry presence improves discovery confidence and cross-source consistency. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.

Point loss breakdown

ComponentCurrentPoints missing
Transport Compliance 0/4 -4.0
Recovery Semantics 0/4 -4.0
Dependency Supply Chain Signal 0.5/4 -3.5
Trust Confidence 1.8/4 -2.2
Utility Coverage 2/4 -2.0
Spec Recency 2/4 -2.0
Schema Completeness 2/4 -2.0
Safety Transparency 2/4 -2.0
Result Shape Stability 2/4 -2.0
Resource Contract 2/4 -2.0
Registry Consistency 2/4 -2.0
Rate Limit Semantics 2/4 -2.0

Validation diff

Need at least two validation runs before diffing changes.

Tool snapshot diff & changelog

Need at least two validation runs before building a tool changelog.

Connector replay

Status
Missing
Backward compatible
Would break after refresh
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.

Transport compliance drilldown

Probe status
Error
Transport
streamable-http
Session header
no
Protocol header
no
Bad protocol response
404
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: missing_session_id, missing_protocol_header, bad_protocol_not_rejected

Request association

Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none

Utility coverage

Probe status
Missing
Completions
not detected
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no

Benchmark tasks

Benchmark taskStatusEvidence
Discover tools Passes
  • initializeOK
  • tools_listOK
Read-only fetch flow Likely to fail
  • resource_readMissing
  • read_only_tool_surfaceMissing
OAuth-required connect Degraded
  • oauth_protected_resourceError
  • step_up_auth_probeMissing
Safe write flow with confirmation Likely to fail
  • action_safety_probeError

Registry & provenance divergence

Probe status
OK
Direct official match
no
Drift fields
none
FieldRegistryLive server card
Titlen/an/a
Versionn/an/a
Homepagen/an/a

Active alerts

No active alerts for the current server state.

Aliases & registry graph

IdentifierSourceCanonicalScore
github-ronload/bazi-flex-mcp github_topic_registry yes 67.87

Alias consolidation

Canonical identifier
github-ronload/bazi-flex-mcp
Duplicate aliases
0
Registry sources
github_topic_registry
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Install snippets

Openai Connectors
Connector URL: https://bazi-flex.ronaldluo.com/mcp
# No OAuth metadata detected.
# Server: github-ronload/bazi-flex-mcp
Claude Desktop
{
  "mcpServers": {
    "bazi-flex-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://bazi-flex.ronaldluo.com/mcp"]
    }
  }
}
Smithery
smithery mcp add "https://bazi-flex.ronaldluo.com/mcp"
Generic Http
curl -sS https://bazi-flex.ronaldluo.com/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Agent access & tool surface

Live server tools
getBaziChart getBaziChartPartial
Observed from the latest live validation against https://bazi-flex.ronaldluo.com/mcp. This is the target server surface, not Verify's own inspection tools.
Live capability counts
2 tools • 0 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search fetch search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for github-ronload/bazi-flex-mcp.
Direct machine links

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions
0
Teams: none

Alert routing

Active watches
0
Generic webhooks
0
Slack routes
0
Teams routes
0
Email routes
0
WatchTeamChannelsMinimum severity
No active watch destinations.

Maintainer analytics

Validation Run Count
1
Average Latency Ms
2026.24
Healthy Run Ratio Recent
1.0
Registry Presence Count
1
Active Alert Count
0
Watcher Count
0
Verified Claim
False
Taxonomy Tags
development, search, communication, productivity
Score Trend
67.87
Remediation Count
19
High Risk Tool Count
0
Destructive Tool Count
1
Exec Tool Count
0

Maintainer response quality

Score
33.33
Verified claim
Support contact
Changelog present
Incident notes present
Tool changes documented
Annotation history
Annotation count
0

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Latest validation evidence

Latest summary
Healthy
Validation profile
remote_mcp
Started
Aug 04, 2026 03:07:38 AM UTC
Latency
2026.2 ms

Failures

Checks

CheckStatusLatencyEvidence
action_safety_probe Error n/a 1 destructive tool(s); no clear auth boundary; safeguards=0; confirmation=none.
advanced_capabilities_probe Missing n/a No advanced MCP capability signals detected.
connector_publishability_probe Warning n/a Publishability blockers: transport compliance, action safety, server card.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe OK 40.8 ms Check completed
initialize OK 199.8 ms Protocol 2025-03-26
interactive_flow_probe Missing n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 263.4 ms Client error '404 Not Found' for url 'https://bazi-flex.ronaldluo.com/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
official_registry_probe Warning n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 154.9 ms Fetched https://bazi-flex.ronaldluo.com/robots.txt
prompt_get Missing n/a not advertised
prompts_list Missing 174.3 ms not supported
protocol_version_probe Warning n/a Claims 2025-03-26; 2 release(s) behind 2025-11-25.
provenance_divergence_probe OK n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read Missing n/a not advertised
resources_list Missing 175.8 ms not supported
server_card Error 358.5 ms Client error '404 Not Found' for url 'https://bazi-flex.ronaldluo.com/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
session_resume_probe Warning n/a no session id
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe Missing n/a no historical snapshot
tools_list OK 347.6 ms 2 tool(s) exposed
transport_compliance_probe Error 217.7 ms Issues: missing session id, missing protocol header, bad protocol not rejected (bad protocol=404).
utility_coverage_probe Missing 38.9 ms No completions evidence; no pagination evidence; tasks missing.

Raw evidence view

Show raw JSON evidence
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [],
        "safeguard_count": 0,
        "summary": {
          "bulk_access_tools": 0,
          "capability_distribution": {
            "admin": 1,
            "delete": 1,
            "network": 1,
            "read": 2,
            "write": 2
          },
          "destructive_tools": 1,
          "egress_tools": 0,
          "exec_tools": 0,
          "high_risk_tools": 0,
          "risk_distribution": {
            "critical": 0,
            "high": 0,
            "low": 0,
            "medium": 2
          },
          "secret_tools": 0,
          "tool_count": 2
        }
      },
      "latency_ms": null,
      "status": "error"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": false,
          "resources": false,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [],
        "enabled_count": 0,
        "initialize_capability_keys": [
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "missing"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "transport_compliance",
          "action_safety",
          "server_card"
        ],
        "criteria": {
          "action_safety": false,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": false,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": true,
          "tools_list": true,
          "transport_compliance": false
        },
        "high_risk_tools": 0,
        "tool_count": 2,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_replay_probe": {
      "details": {
        "reason": "no_historical_snapshot"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "determinism_probe": {
      "details": {
        "attempts": 2,
        "baseline_signature": "cfbf95920cbea1203ca0109644bd487fc4385d7e10ed25759d384be3f6fc8862",
        "errors": [],
        "matches": 2,
        "stable_ratio": 1.0,
        "successful": 2
      },
      "latency_ms": 40.81,
      "status": "ok"
    },
    "initialize": {
      "details": {
        "headers": {
          "content-type": "text/event-stream"
        },
        "http_status": 200,
        "payload": {
          "id": 1,
          "jsonrpc": "2.0",
          "result": {
            "capabilities": {
              "tools": {
                "listChanged": true
              }
            },
            "protocolVersion": "2025-03-26",
            "serverInfo": {
              "name": "bazi-flex-mcp",
              "version": "0.0.1"
            }
          }
        },
        "url": "https://bazi-flex.ronaldluo.com/mcp"
      },
      "latency_ms": 199.76,
      "status": "ok"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://bazi-flex.ronaldluo.com/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://bazi-flex.ronaldluo.com/.well-known/oauth-protected-resource"
      },
      "latency_ms": 263.44,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": false,
        "official_identifiers": [
          "ai.ai-akari/one-minute-akari",
          "ai.artidrop/artidrop",
          "ai.justpublish/just-publish",
          "ai.ankimcp/anki-mcp-server",
          "ai.pimea/pimea",
          "ai.afmr/discovery",
          "ai.boolsai/directory",
          "ai.agenticfabricationnetwork/ufp",
          "ai.agenticshelf/graffeo",
          "ac.tandem/docs-mcp"
        ],
        "official_peer_count": 10,
        "registry_source": "github_topic_registry"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain; charset=utf-8"
        },
        "http_status": 200,
        "url": "https://bazi-flex.ronaldluo.com/robots.txt"
      },
      "latency_ms": 154.89,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream"
        },
        "http_status": 200,
        "payload": {
          "error": {
            "code": -32601,
            "message": "Method not found"
          },
          "id": 3,
          "jsonrpc": "2.0"
        },
        "reason": "not_supported",
        "url": "https://bazi-flex.ronaldluo.com/mcp"
      },
      "latency_ms": 174.28,
      "status": "missing"
    },
    "protocol_version_probe": {
      "details": {
        "claimed_version": "2025-03-26",
        "lag_days": 244,
        "latest_known_version": "2025-11-25",
        "releases_behind": 2,
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "provenance_divergence_probe": {
      "details": {
        "direct_official_match": false,
        "drift_fields": [],
        "metadata_document_count": 1,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": null,
        "server_card_version": null
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream"
        },
        "http_status": 200,
        "payload": {
          "error": {
            "code": -32601,
            "message": "Method not found"
          },
          "id": 5,
          "jsonrpc": "2.0"
        },
        "reason": "not_supported",
        "url": "https://bazi-flex.ronaldluo.com/mcp"
      },
      "latency_ms": 175.78,
      "status": "missing"
    },
    "server_card": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://bazi-flex.ronaldluo.com/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://bazi-flex.ronaldluo.com/.well-known/mcp/server-card.json"
      },
      "latency_ms": 358.49,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "protocol_version": "2025-03-26",
        "reason": "no_session_id",
        "resume_expected": true,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "current_tool_count": 2,
        "reason": "no_historical_snapshot"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tools_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream"
        },
        "http_status": 200,
        "payload": {
          "id": 2,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "description": "Compute a full Bazi chart from complete birth time. Requires year/month/day/hour. Use this when the birth hour is known.\n\nOutput notes:\n- `\u516b\u5b57.\u67f1\u4f4d\u8be6\u7ec6.\u65e5\u67f1.\u4e3b\u661f` is `null` (\u65e5\u4e3b carries no ten-god against itself). Identify the day-pillar via `\u65e5\u67f1.isDayMaster === true`; `\u65e5\u67f1.label` is `\"\u65e5\u4e3b\"` for display. Only year/month/hour pillars carry real ten-god strings in `\u4e3b\u661f`.\n- `\u516b\u5b57.\u67f1\u4f4d\u8be6\u7ec6.\u65e5\u67f1.\u526f\u661f` intentionally still contains ten-god strings (the day-pillar's earth-branch hidden stems carry real ten-god relations to the day-master \u2014 e.g. \u8f9b in \u9149 is \u4e03\u6740 to \u4e59 day-master). Only `\u4e3b\u661f` is nulled because \u65e5\u4e3b has no ten-god against itself; \u526f\u661f is unaffected.\n- `\u516b\u5b57.\u5341\u795e\u7edf\u8ba1[\u5341\u795e]` aggregates ten-god counts as `{ \u900f, \u85cf, \u5171 }`. `\u900f` counts from year/month/hour pillars' `\u4e3b\u661f`; `\u85cf` counts from all four pillars' `\u526f\u661f` (earth-branch hidden stems). \u65e5\u4e3b itself is excluded.\n- `\u516b\u5b57.\u67f1\u95f4\u5173\u7cfb` lists pair-wise (or triple-wise, for \u4e09\u5211) relations between the four pillars, derived from upstream `\u5211\u51b2\u5408\u4f1a`. Each entry is `{ kind: \"\u5929\u5e72\"|\"\u5730\u652f\", type: \"\u76f8\u5408\"|\"\u76f8\u51b2\"|\"\u76f8\u5bb3\"|\"\u76f8\u7834\"|\"\u6697\u5408\"|\"\u81ea\u5211\"|\"\u4e09\u5211\"|\"\u514b\", pillars: [\u5e74|\u6708|\u65e5|\u65f6, ...], \u5e72\u652f: [...], raw }`. When two pillars share the same stem/branch (e.g. two \u4e59 in month and day), a single upstream relation expands to multiple entries covering each possible pillar pair \u2014 the ambiguity is surfaced rather than hidden.\n- `\u516b\u5b57.\u51b3\u7b56\u8f85\u52a9` surfaces three derived metrics so consumers do not recompute them: `\u65e5\u4e3b\u5f97\u4ee4` (day-master element relation to month-command element + `\u5f97\u4ee4` boolean), `\u65e5\u4e3b\u6839\u6c14` (day-master-element presence across all four earth-branch hidden-stems using canonical \u672c/\u4e2d/\u4f59 weights 1.0/0.5/0.3), and `\u900f\u85cf\u5e73\u8861` (\u6bd4\u52ab vs \u5f02\u7c7b transparent/hidden counts). These are raw inputs \u2014 no \u65fa\u8870/\u683c\u5c40/\u7528\u795e judgement is baked in. Feed them into your own reasoning rules.\n- `\u516b\u5b57.\u6d41\u5e74` is an array of year-by-year \u6d41\u5e74 entries covering `\u516b\u5b57.\u6d41\u5e74\u8303\u56f4` (default: the \u5e72\u652f\u5e74 of `referenceDate` plus/minus 3 = 7 years, configurable via `liunianStart`/`liunianEnd` for a wider window). Each entry is `{ \u5e74\u4efd, \u5e72\u652f, \u5929\u5e72, \u5730\u652f, \u4e3b\u661f, \u85cf\u5e72, \u85cf\u5e72\u5341\u795e, \u5f53\u524d }`; `\u4e3b\u661f` is the ten-god of the year stem against the day-master. \u6d41\u5e74 vs \u56db\u67f1/\u5927\u8fd0 relations are NOT pre-computed \u2014 derive them yourself by combining `\u6d41\u5e74[].\u5e72\u652f` with `\u67f1\u95f4\u5173\u7cfb` logic or `\u5927\u8fd0[].\u5e72\u652f`. `\u5e74\u4efd: N` denotes the \u7acb\u6625-bounded \u5e72\u652f\u5e74, i.e. \u7acb\u6625 of year N through the day before \u7acb\u6625 of N+1. `\u5f53\u524d` resolves `referenceDate` under that same convention, so between Jan 1 and \u7acb\u6625 it correctly points at the previous \u5e72\u652f\u5e74. Resolved at day granularity: on \u7acb\u6625 day itself the exact instant is not considered.\n- `\u516b\u5b57.\u5927\u8fd0[].\u65e5\u4e3b\u5173\u7cfb` is `null` when there is no relation (previously `\"\"`).\n- `\u516b\u5b57.\u5927\u8fd0[].\u5f53\u524d` is computed from `meta.referenceDateUsed` (defaults to today). Override via the `referenceDate` input for historical or hypothetical scenarios.\n- `meta.scoringMethod` documents how `\u516b\u5b57.\u4e94\u884c\u5206\u503c` is computed, so consumers do not need to guess the weighting scheme.\n- Time strings (`\u8f93\u5165.\u516c\u5386`, `\u771f\u592a\u9633\u65f6.\u949f\u8868\u65f6\u95f4`, `\u771f\u592a\u9633\u65f6.\u771f\u592a\u9633\u65f6`, `\u516b\u5b57.\u516c\u5386`) are all ISO 8601 with second precision (`YYYY-MM-DDTHH:MM:SS`). `\u771f\u592a\u9633\u65f6.\u4fee\u6b63\u5206\u949f` is the original decimal-minute correction; `\u771f\u592a\u9633\u65f6.\u4fee\u6b63\u79d2\u6570` is the same value as a rounded integer number of seconds.\n- \u7a7a\u4ea1 is surfaced as three complementary fields (this server restructures upstream's ambiguous single-string surface). `\u516b\u5b57.\u65ec\u7a7a = { \u65e5\u67f1\u65ec\u7a7a: [...], \u5e74\u67f1\u65ec\u7a7a: [...] }` is the top-level index of void branches for the two traditional reference \u65ecs. Each pillar (and each `\u5927\u8fd0` entry) exposes `\u6240\u5728\u65ec\u7a7a\u4ea1: string[]` (the two branches void in *that pillar's own* \u65ec \u2014 pure reference, does NOT imply this pillar is void) and `\u843d\u7a7a\u4ea1: { \u65e5\u67f1\u65ec: boolean, \u5e74\u67f1\u65ec: boolean }` (does this pillar's earth branch actually fall into day-xun / year-xun void). The original upstream `\u7a7a\u4ea1: string` field is removed on both \u67f1\u4f4d\u8be6\u7ec6 and \u5927\u8fd0 entries \u2014 use the structured fields instead. Prefer `\u843d\u7a7a\u4ea1` as the authoritative \"is this pillar in \u7a7a\u4ea1\" signal; upstream's `\u795e\u715e` array still contains a `\"\u7a7a\u4ea1\"` string for compatibility but it's the boolean-OR of `\u843d\u7a7a\u4ea1.\u65e5\u67f1\u65ec` and `\u843d\u7a7a\u4ea1.\u5e74\u67f1\u65ec`. For strict modern \u4ee5\u65e5\u8d77\u7a7a\u4ea1 convention, use `\u843d\u7a7a\u4ea1.\u65e5\u67f1\u65ec` alone.\n- `\u516b\u5b57.\u8d77\u8fd0` is the precise duration from birth to the first decade cycle (e.g., `\"6\u5e747\u670822\u65e5\u8d77\u8fd0\"`), derived from the solar-term distance. `\u516b\u5b57.\u8d77\u8fd0\u65e5\u671f` is the corresponding Gregorian date.\n- Each `\u516b\u5b57.\u5927\u8fd0` entry exposes `\u8d77\u59cb\u865a\u5c81` (East-Asian nominal age; equals the original `\u8d77\u59cb\u5e74\u9f84`) and `\u8d77\u59cb\u5b9e\u5c81` (completed years at that decade-cycle start, derived from `\u8d77\u8fd0\u65e5\u671f` aligned to the birth month/day). They typically differ by 1-2.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "properties": {
                    "city": {
                      "description": "Birth city (Chinese name preferred); enables true-solar-time correction",
                      "type": "string"
                    },
                    "day": {
                      "description": "Gregorian day of month",
                      "maximum": 31,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "gender": {
                      "anyOf": [
                        {
                          "const": 0,
                          "type": "number"
                        },
                        {
                          "const": 1,
                          "type": "number"
                        }
                      ],
                      "description": "0 = female, 1 = male"
                    },
                    "hour": {
                      "description": "Hour of birth (0-23)",
                      "maximum": 23,
                      "minimum": 0,
                      "type": "integer"
                    },
                    "latitude": {
                      "description": "Birth latitude in degrees north",
                      "type": "number"
                    },
                    "liunianEnd": {
                      "description": "End year for the \u6d41\u5e74 table. Years are \u7acb\u6625-bounded \u5e72\u652f\u5e74, not Gregorian years. Defaults to the \u5e72\u652f\u5e74 of referenceDate plus 3.",
                      "maximum": 9007199254740991,
                      "minimum": -9007199254740991,
                      "type": "integer"
                    },
                    "liunianStart": {
                      "description": "Start year for the \u6d41\u5e74 table. Years are \u7acb\u6625-bounded \u5e72\u652f\u5e74, not Gregorian years. Defaults to the \u5e72\u652f\u5e74 of referenceDate minus 3.",
                      "maximum": 9007199254740991,
                      "minimum": -9007199254740991,
                      "type": "integer"
                    },
                    "longitude": {
                      "description": "Birth longitude in degrees east",
                      "type": "number"
                    },
                    "minute": {
                      "default": 0,
                      "description": "Minute of birth (0-59)",
                      "maximum": 59,
                      "minimum": 0,
                      "type": "integer"
                    },
                    "month": {
                      "description": "Gregorian month (1-12)",
                      "maximum": 12,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "referenceDate": {
                      "description": "Optional ISO date (YYYY-MM-DD). Accept this as an INPUT from the caller \u2014 pass it explicitly for historical reconstructions or hypothetical 'what if I looked at this chart at time T' queries. Defaults to system today when omitted. Controls which `\u516b\u5b57.\u5927\u8fd0[].\u5f53\u524d` is true and which `\u516b\u5b57.\u6d41\u5e74[].\u5f53\u524d` is true. Echoed back as `meta.referenceDateUsed`.",
                      "pattern": "^\\d{4}-\\d{1,2}-\\d{1,2}$",
                      "type": "string"
                    },
                    "year": {
                      "description": "Gregorian year of birth",
                      "maximum": 9007199254740991,
                      "minimum": -9007199254740991,
                      "type": "integer"
                    }
                  },
                  "required": [
                    "year",
                    "month",
                    "day",
                    "hour",
                    "gender"
                  ],
                  "type": "object"
                },
                "name": "getBaziChart",
                "title": "Get Bazi Chart (full time)"
              },
              {
                "description": "Compute a three-pillar Bazi chart when the birth hour is unknown. Requires year/month/day/gender. Use this when the caller knows only the birth date.\n\nHow it works:\n- The chart is built natively from \u5e74/\u6708/\u65e5 alone. No placeholder hour is invented, so nothing in the output is derived from a time that was never supplied.\n- \u5e74\u67f1 and \u6708\u67f1 use day-granular attribution: the whole calendar day on which a \u7bc0 falls belongs to the new month (and \u7acb\u6625 day to the new \u5e72\u652f\u5e74).\n- When the birth date is itself a \u7bc0 day the answer is genuinely undetermined, and `\u516b\u5b57.\u8282\u6c14\u6b67\u4e49` reports both candidates instead of hiding the choice. See below.\n\n`\u516b\u5b57.\u8282\u6c14\u6b67\u4e49` (only field with no counterpart in `getBaziChart`):\n- `null` on ordinary days. Non-null on the ~1.6% of dates that carry a \u7bc0.\n- `\u8282\u6c14` is the term name, `\u65f6\u523b` its exact local moment (`YYYY-MM-DDTHH:MM:SS`), `\u5f71\u54cd` lists which pillars actually differ across it.\n- `\u6b64\u523b\u4e4b\u524d` holds the \u5e74\u67f1/\u6708\u67f1 for a birth earlier that day; `\u6b64\u523b\u4e4b\u540e` holds them for a birth at or after the moment. `\u6b64\u523b\u4e4b\u540e` is what the rest of the response uses.\n- If the caller can narrow the birth time to one side of `\u65f6\u523b`, prefer the matching branch and say so; otherwise present both.\n\nOutput differences vs `getBaziChart`:\n- `\u516b\u5b57.\u4e09\u67f1` replaces `\u516b\u5b57.\u56db\u67f1` and holds exactly three \u5e72\u652f.\n- `\u516b\u5b57.\u67f1\u4f4d\u8be6\u7ec6` contains only `\u5e74\u67f1`, `\u6708\u67f1`, `\u65e5\u67f1` \u2014 the `\u65f6\u67f1` key is **omitted entirely** (not just nulled). Identify the day-pillar via `\u65e5\u67f1.isDayMaster === true`.\n- `\u516b\u5b57.\u547d\u5bab`, `\u516b\u5b57.\u8eab\u5bab`, `\u516b\u5b57.\u80ce\u5143`, `\u516b\u5b57.\u80ce\u606f` are all `null` \u2014 these formulas require the birth hour and cannot be approximated.\n- `\u771f\u592a\u9633\u65f6` is **omitted** from the response, and `\u57ce\u5e02` / `\u7ecf\u5ea6` / `\u7eac\u5ea6` are not accepted as inputs: the correction only ever moves the hour pillar.\n- `\u8f93\u5165.\u516c\u5386` and `\u516b\u5b57.\u516c\u5386` are date-only (`YYYY-MM-DD`); `\u8f93\u5165.\u65f6\u8fb0` is `null`; `\u516b\u5b57.\u519c\u5386` carries no \u65f6\u8fb0 suffix.\n- `\u516b\u5b57.\u5341\u795e\u7edf\u8ba1`, `\u516b\u5b57.\u4e94\u884c\u5206\u503c`, `\u516b\u5b57.\u5211\u51b2\u5408\u4f1a`, `\u516b\u5b57.\u67f1\u95f4\u5173\u7cfb` and `\u516b\u5b57.\u51b3\u7b56\u8f85\u52a9.\u65e5\u4e3b\u6839\u6c14` all cover \u5e74/\u6708/\u65e5 only. `\u5360\u6bd4` in `\u516b\u5b57.\u4e94\u884c\u5206\u503c` is normalised over the 3-pillar total.\n- `\u516b\u5b57.\u5927\u8fd0` is **kept**: the decade-cycle direction (\u987a/\u9006) depends only on year-pillar polarity + gender, neither of which needs the hour. **However**, \u8d77\u8fd0 and \u8d77\u8fd0\u65e5\u671f are measured from the birth moment to the neighbouring solar term, and the reference moment used here is the midpoint of the day's month-command window, so they may carry **\u00b11 day to \u00b11-2 month error** \u2014 and the resulting `\u8d77\u59cb\u5e74\u4efd` / `\u7ed3\u675f\u5e74\u4efd` may shift by \u00b11 year. Treat decade boundaries as approximate windows, not precise dates. See `meta.disclaimer.\u5927\u8fd0\u8d77\u8fd0\u7cbe\u5ea6`.\n- `\u516b\u5b57.\u6d41\u5e74` is unchanged \u2014 \u6d41\u5e74 derivation depends only on the day-master stem and the \u5e72\u652f\u5e74, neither of which needs the hour.\n- `\u516b\u5b57.\u65ec\u7a7a` (`\u65e5\u67f1\u65ec\u7a7a`, `\u5e74\u67f1\u65ec\u7a7a`) and per-pillar `\u6240\u5728\u65ec\u7a7a\u4ea1` / `\u843d\u7a7a\u4ea1` are unchanged in semantics; the day pillar does not depend on the hour except across the 23:00 \u5b50\u65f6 switch, which no date-only input can reach.\n\nInherited from `getBaziChart` (unchanged behaviour):\n- `\u516b\u5b57.\u67f1\u4f4d\u8be6\u7ec6.\u65e5\u67f1.\u4e3b\u661f` is `null` (\u65e5\u4e3b carries no ten-god against itself); use `\u65e5\u67f1.isDayMaster === true` to identify the day pillar; `\u65e5\u67f1.label` is `\"\u65e5\u4e3b\"`.\n- `\u516b\u5b57.\u5927\u8fd0[].\u65e5\u4e3b\u5173\u7cfb` is `null` when there is no relation (instead of `\"\"`).\n- `\u516b\u5b57.\u5927\u8fd0[].\u5f53\u524d` is computed from `meta.referenceDateUsed` (defaults to today). Override via the `referenceDate` input.\n- `meta.scoringMethod` documents how `\u516b\u5b57.\u4e94\u884c\u5206\u503c` is computed (3-pillar variant).\n- `meta.disclaimer` enumerates exactly which fields are absent, null, or 3-pillar-only and why \u2014 surface this to the user when explaining the chart's confidence level.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "properties": {
                    "day": {
                      "description": "Gregorian day of month",
                      "maximum": 31,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "gender": {
                      "anyOf": [
                        {
                          "const": 0,
                          "type": "number"
                        },
                        {
                          "const": 1,
                          "type": "number"
                        }
                      ],
                      "description": "0 = female, 1 = male"
                    },
                    "liunianEnd": {
                      "description": "End year for the \u6d41\u5e74 table. Years are \u7acb\u6625-bounded \u5e72\u652f\u5e74, not Gregorian years. Defaults to the \u5e72\u652f\u5e74 of referenceDate plus 3.",
                      "maximum": 9007199254740991,
                      "minimum": -9007199254740991,
                      "type": "integer"
                    },
                    "liunianStart": {
                      "description": "Start year for the \u6d41\u5e74 table. Years are \u7acb\u6625-bounded \u5e72\u652f\u5e74, not Gregorian years. Defaults to the \u5e72\u652f\u5e74 of referenceDate minus 3.",
                      "maximum": 9007199254740991,
                      "minimum": -9007199254740991,
                      "type": "integer"
                    },
                    "month": {
                      "description": "Gregorian month (1-12)",
                      "maximum": 12,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "referenceDate": {
                      "description": "Optional ISO date (YYYY-MM-DD). Accept this as an INPUT from the caller \u2014 pass it explicitly for historical reconstructions or hypothetical 'what if I looked at this chart at time T' queries. Defaults to system today when omitted. Controls which `\u516b\u5b57.\u5927\u8fd0[].\u5f53\u524d` is true and which `\u516b\u5b57.\u6d41\u5e74[].\u5f53\u524d` is true. Echoed back as `meta.referenceDateUsed`.",
                      "pattern": "^\\d{4}-\\d{1,2}-\\d{1,2}$",
                      "type": "string"
                    },
                    "year": {
                      "description": "Gregorian year of birth",
                      "maximum": 9007199254740991,
                      "minimum": -9007199254740991,
                      "type": "integer"
                    }
                  },
                  "required": [
                    "year",
                    "month",
                    "day",
                    "gender"
                  ],
                  "type": "object"
                },
                "name": "getBaziChartPartial",
                "title": "Get Bazi Chart (no hour)"
              }
            ]
          }
        },
        "url": "https://bazi-flex.ronaldluo.com/mcp"
      },
      "latency_ms": 347.65,
      "status": "ok"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json"
        },
        "bad_protocol_payload": {
          "error": {
            "code": -32000,
            "message": "Bad Request: Unsupported protocol version (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"
          },
          "id": null,
          "jsonrpc": "2.0"
        },
        "bad_protocol_status_code": 404,
        "delete_error": null,
        "delete_status_code": null,
        "expired_session_error": null,
        "expired_session_status_code": null,
        "issues": [
          "missing_session_id",
          "missing_protocol_header",
          "bad_protocol_not_rejected"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": false,
        "transport": "streamable-http"
      },
      "latency_ms": 217.69,
      "status": "error"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [
          "tools"
        ],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 200,
          "probe_status": "missing"
        }
      },
      "latency_ms": 38.91,
      "status": "missing"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://bazi-flex.ronaldluo.com/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://bazi-flex.ronaldluo.com/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "server_card": {
      "error": "Client error '404 Not Found' for url 'https://bazi-flex.ronaldluo.com/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://bazi-flex.ronaldluo.com/.well-known/mcp/server-card.json"
    },
    "transport_compliance_probe": {
      "bad_protocol_error": null,
      "bad_protocol_headers": {
        "content-type": "application/json"
      },
      "bad_protocol_payload": {
        "error": {
          "code": -32000,
          "message": "Bad Request: Unsupported protocol version (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"
        },
        "id": null,
        "jsonrpc": "2.0"
      },
      "bad_protocol_status_code": 404,
      "delete_error": null,
      "delete_status_code": null,
      "expired_session_error": null,
      "expired_session_status_code": null,
      "issues": [
        "missing_session_id",
        "missing_protocol_header",
        "bad_protocol_not_rejected"
      ],
      "last_event_id_visible": false,
      "protocol_header_present": false,
      "requested_protocol_version": "2025-03-26",
      "session_id_present": false,
      "transport": "streamable-http"
    }
  },
  "remote_url": "https://bazi-flex.ronaldluo.com/mcp",
  "server_card_payload": null,
  "server_identifier": "github-ronload/bazi-flex-mcp"
}

Known versions

Validation history

Trend history appears after at least two validation runs. This avoids presenting a one-point validation as a trend.

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Aug 04, 2026 03:07:40 AM UTC Healthy 67.9 2025-03-26 public 2 0 none

Recent validation runs

Recent validation runs for this MCP server
StartedStatusSummaryLatencyChecks
Aug 04, 2026 03:07:38 AM UTC Completed Healthy 2026.2 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe