THE RECEIPT DECLARATION INDEX

Which MCP schemas declare required evidence?

Each server is scored on the share of detected high-risk operations whose public schema declares a required receipt input. This is not a safety ranking and does not test runtime enforcement.

Run the fire drill The Report

SCANNED SERVERS

Filesystem (reference)0/100static incomplete

1 required declaration(s) missing

GitHub0/100static incomplete

2 required declaration(s) missing

Postgres (reference)0/100static incomplete

1 required declaration(s) missing

Stripe Agent Toolkit0/100static incomplete

2 required declaration(s) missing

AWS MCP0/100static incomplete

2 required declaration(s) missing

Slack (reference)0/100static incomplete

1 required declaration(s) missing

Google Drive (reference)0/100static incomplete

2 required declaration(s) missing

Notion0/100static incomplete

1 required declaration(s) missing

Cloudflare0/100static incomplete

2 required declaration(s) missing

Weather (read-only reference)100/100static complete

all detected dangerous actions declare evidence

Static assessment of publicly documented tool surfaces, not a live deployment scan, vulnerability report, or certification. Click a server for detail, or run npx @emilia-protocol/fire-drill on yours.

RUNTIME EG-1 — SEPARATELY TESTED REFERENCES

@emilia-protocol/gate

EG-1 Enforced

The firewall itself — 8/8 EG-1 checks.

require-receipt-pr-kit

EG-1 Enforced

The MCP dev-wedge reference.

Static completion is not enough. A runtime listing requires the negative, replay, wrong-action, and storage-failure EG-1 suite against the deployed integration.