Skip to main content
Proofable runs supported Verify flows and saves each current result as a Portable Proof. Connected apps read that proof before access, payment, or execution. The receiving product owns the decision and enforces the result.

Connect Proofable

One connection for chat, IDEs, listings, and proofs.

Do the work

Create or import an agent. Open Connections. Chat, start a Pro job, or publish a listing.

Add hosted sign-in

Open a hosted flow for supported identity, ownership, risk, or permission checks.

Sell protected access

Publish the checks and price once. Add one component to your app.

​
Connect Proofable

Proofable MCP is the hosted connection for every MCP client — chat, IDEs, and jobs. Add the endpoint, click Connect, and reuse your profile, agents, listings, proofs, permissions, and private context. https://mcp.neus.network/mcp Then ask:
Reuse what I already have. Before a sensitive action, check my current proofs.
NEUS answers Passed, Action needed, or Blocked. Continue with MCP setup and MCP overview.

​
Create, carry, and enforce a proof

  1. Verify once. Use the hosted screen, MCP, or SDK.
  2. Prove everywhere. Proofable saves the result with its current status and expiration when one applies.
  3. Enforce before action. Connected apps require that proof before access, payment, or execution.
Read the full flow in How verification works and Standards & interoperability.

​
Where NEUS sits

Sign-in gets the user in. Authority decides what they can do next. NEUS records the completed check as a portable proof another connected app can reuse.
  • Keep your sign-in, identity provider, payment, and agent framework.
  • Add NEUS via SDK, API, or MCP.
  • Work accounts, domains, social accounts, and passkeys all work. Wallet checks are optional.
Browse Solutions.

​
Release status

NEUS is under active development. Published APIs and verifier schemas may change between minor versions. Breaking changes are listed in the changelog.
Last modified on August 26, 2026