Published standard

Xupra KYA Agent Transaction Standard v0.1

Public trust rules for hosted Know Your Agent certificates used in agent-to-agent verification.

Standard summary

Version: mcp-kya-basic-v0.1
Scope: Hosted agent and MCP certificate verification
Verification: Online status plus optional live nonce challenge
Audience: Agents, MCP clients, and relying transaction systems
Issuer: Xupra KYA Registry
Evidence posture: Public attestation plus private review archive

Control families

What the first KYA standard actually covers.

Identity binding

Every certificate binds one accountable company to one reviewed MCP server, agent, agent card, package, repository, or tool gateway.

Company identity and website domain
Reviewed asset name, type, and endpoint or source binding
Hosted certificate URL and issuer DID
Optional certified operational key for live challenge verification

Transaction trust

Verification is designed for agent-to-agent workflows where the relying agent must confirm status and authority before allowing sensitive work.

Active status, issue date, and expiry checks
KYA level and MCP risk class
Revocation-aware online verification
Evidence hash and signature validation

Review evidence

Xupra reviews technical and operational evidence before a hosted certificate becomes active.

Declared MCP tools, resources, prompts, and permissions
Repository, package, endpoint, and agent card mapping
Maintainer and operator accountability
Recorded scan evidence and operator notes retained privately

Public evidence

What verifiers can see.

certificate identifier
issuer DID and issuer metadata endpoint
company identity and reviewed asset binding
KYA level, MCP risk class, and status
issue date, expiry date, and evidence hash
hosted verification URL and badge URL

Private evidence

What stays with Xupra and the company.

raw scan output and operator notes
survey responses and supporting documents
remediation conversations and internal review history
non-public endpoint details or sensitive architecture evidence

Suspension rules

temporary uncertainty about the reviewed deployment or key binding
new evidence that requires remediation before trust can continue
operator-requested hold while the company updates the asset

Revocation rules

certificate subject no longer maps to the live asset or company control boundary
material hidden behavior, undisclosed capability, or unresolved critical issue
replacement by a newer certificate or explicit withdrawal from the registry

Transaction policy

Different transactions require different trust.

Transaction	Min KYA	Max Risk	Live Challenge	Offline Fallback
directory_lookup	KYA-L1	MCP-R3	offline_ok	allow_offline_lookup
agent_message	KYA-L1	MCP-R2	live_preferred	allow_offline_lookup
tool_invocation	KYA-L2	MCP-R2	live_preferred	deny_when_offline
data_access	KYA-L2	MCP-R1	live_preferred	deny_when_offline
payment_instruction	KYA-L2	MCP-R1	live_required	deny_when_offline
wallet_signing	KYA-L3	MCP-R0	live_required	deny_when_offline

Certification decisions

Pass, remediate, or fail.

Pass

No hidden critical behavior, accountable company identity, stable asset binding, and review evidence sufficient for the assigned KYA level.

Needs remediation

The company can correct declared-tool drift, unresolved high findings, weak delegation controls, or incomplete operational evidence and return for review.

Fail

Hidden shell execution, hidden private-key access, misleading capability disclosure, unresolved critical findings, or ownership mismatch blocks certification.