Skip to main content
NEUS runs supported checks and saves each current result as a Portable Proof. Connected apps read that proof before access, payment, or execution. The receiving product decides what it accepts and enforces the result. Choose the integration path that matches the decision your product needs to make.

Set up MCP

Load your NEUS profile and proofs inside a supported assistant.

Add Hosted Verify

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 an AI assistant

The portable trust harness for AI. Add the hosted MCP endpoint, click Connect, and the same profile, checks, Portable Proofs, permissions, and private context are available in that client. https://mcp.neus.network/mcp Then ask:
Before you take a sensitive action, use NEUS. Reuse what I already have.
NEUS answers Passed, Action needed, or Blocked. You now have a clear decision before the action runs. Continue with MCP setup and the NEUS trust stack for MCP.

​
Create, carry, and enforce a proof

  1. Verify once. Run a check through the hosted screen, MCP, or SDK.
  2. Carry the proof. NEUS 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

Login gets them 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. No replacement required.
  • No wallet required. Work accounts, domains, social accounts, and passkeys all work. Wallet checks are optional.
See how teams put this to work in Solutions.

​
Release status

NEUS is under active development. Published APIs and verifier schemas may change between minor versions before the long-term stability freeze. We version everything we ship and document every breaking change in the changelog.
Last modified on August 20, 2026