Intelligence can recommend.
It cannot grant permission.
Conflux MCP separates discovery from authority, evidence from decision, and decision from execution. This page shows exactly how.
What has actually been checked.
Every published capability carries a verification record. It names the stages that ran, the outcome of each stage, and the verifier. A server without a VERIFIED record cannot be PUBLISHED. Verification is a fact with a provenance, not a marketing claim.
Identity, version, capabilities, sources.
Every field conforms to the Part 5 contract.
Server identity and version are real.
Declared capabilities match the manifest.
Every declared source is reachable.
Published artifacts match their hashes.
MCP transport and version.
No forbidden patterns, no credential exposure.
Repository, license, and publisher.
Where every capability comes from.
Every server carries a source record: repository, license, publisher, publication timestamp, and the exact version that was verified. When a new version appears, it is a new record with a new verification. Old versions remain auditable.
Who owns the server.
Where the code lives.
Under what terms it may be used.
Which external data sources the server declares.
Which exact version was verified and published.
How the boundary is enforced.
Conflux MCP treats every MCP server as untrusted input. Capabilities declare their access level — READ_ONLY, ADVISORY, STATE_CHANGING, or TRANSACTIONAL — and that declaration drives what the authority layer will permit.
No state change. Safe to expose broadly.
Recommendations only. No automatic action.
Requires explicit authority and approval.
Requires explicit authority, approval, and policy.
What happened, and how you can prove it.
Every material decision is recorded. Identity, authority, policy, approval, execution, and outcome are all anchored with hashes that make the record tamper-evident. Audit is not a log. It is evidence.
Every gate decision, with reason codes.
Every MCP operation, with its bound token.
Every grant of permission, with its obligation.
Every state transition of every server.
Each record commits to the previous one.