Use Burs-IA from an external pipeline.
An external team can call the public Verify API directly and receive a bounded machine-readable result, evidence hash and durable receipt reference when persistence succeeds. No Burs-IA account or private repository access is required for this MCP technical check. The canonical public MCP identity is https://burs-ia.com/mcp; infrastructure hostnames are deployment backends, not separate Burs-IA products.
Public Verify contract
POST https://burs-ia.com/api/verify
Content-Type: application/json
{
"endpoint": "https://your-public-mcp.example.com/mcp",
"protocolVersion": "2026-07-28"
}
Use 2026-07-28 for new integrations. Burs-IA keeps bounded compatibility with legacy MCP revisions where the runtime explicitly supports them. Suitable for CI, deployment gates or developer tooling that can make an HTTPS POST and parse JSON.
Machine-readable output
{
"verification": {
"status": "PASS | PARTIAL | FAIL",
"evidenceHash": "..."
},
"durableReceipt": {
"receiptId": "...",
"url": "https://burs-ia.com/verify/..."
}
}
PASS only covers the checks explicitly executed by Burs-IA Verify. It is not a security certification.
Terminal artifact
The Verify UI now downloads a versioned BURSIA_MCP_CHECK_DELIVERABLE_V1 JSON bundle containing the verification result, evidence hash and durable receipt reference when available.
TRUST receipt digest check
A third party can recompute the embedded SHA-256 content digest locally. Paste a BURSIA_TRUST_ACTION_RECEIPT_V1 below; this page checks the digest in the browser.
No receipt checked yet.