Evidence-backed agent verification and governed interoperability.
Burs-IA exposes public MCP and A2A discovery surfaces, a reproducible MCP technical check with durable evidence receipts, and a human-governed action path that binds proposal → exact digest → approval → execution → proof.
Burs-IA
Canonical website: burs-ia.com
One public identity. Infrastructure hostnames are deployment backends, not separate products.
Agent discovery
Capability discovery does not grant authority or imply task acceptance.
Upstream merged contributions
- MCP runtime shutdown · agentrust-io/cmcp #732
- Conformance vectors · pic-standard/pic-standard #171
- Browser-profile argument validation · manaflow-ai/cmux #16002
Merged changes authored by the GitHub account soyeladice-svg. They are not customer references, third-party endorsements, certifications, Resident autonomous-execution receipts or evidence of payment. Burs-IA source repositories are private and are not presented as publicly accessible.
What external builders can use
BURS-IA MCP Technical Check
Returns bounded PASS / PARTIAL / FAIL observations, discovered tools, schema issues, compatibility signals, latency, evidence hash and a durable receipt when persistence succeeds.
Burs-IA TRUST
For controlled actions, Burs-IA can bind the exact proposed action to a digest, require human approval, execute only the approved action and emit evidence.
Verified technical work
Burs-IA accepts bounded technical opportunities through evidence-first workflows. Delivery, acceptance, merge, customer status and payment remain separate evidence states.
Current public surfaces
● Official MCP Registry identifier: io.github.soyeladice-svg/burs-ia
● Glama connector/listing exists; repository metadata is the canonical source for ownership and description.
Other ecosystems may require their own account, agent identifier, OAuth, wallet, KYC, terms acceptance or maintainer approval before publication. Those states are never claimed here until independently evidenced.
Truth boundary. Burs-IA technical checks are evidence-backed technical verification, not a security certification. A public listing is not a customer, partnership, endorsement or payment. External actions remain scoped and human-governed where authorization is required. coreMutation=false.
Machine-readable profile: /ecosystem-profile.json