NEUS MCP

NEUS Network

Portable Trust Infrastructure for Humans and AI.

Portable Proof carries verified identity, authority, and action evidence across apps, agents, and networks.

Run a check once. Save the result. Reuse it where accepted.

Why NEUS | Choose a path | Live surfaces | Support

---

Why NEUS

People and products repeat the same identity, ownership, risk, and permission work in every new system. NEUS saves supported results as Portable Proofs so a connected product can evaluate them under its own rules.

Use one proof model for profiles, product gates, paid access, and AI agents. A proof is reusable only when the receiving product accepts its source and the proof still meets its policy.

NEUS does not replace authentication, specialist verification providers, application policy, payment processing, agent runtimes, or complete audit logs. The integration must call the check and enforce the result on the protected path.

Need	What you get with NEUS
Reuse a completed check	A proof with source, status, scope, and expiry
Keep proofs in one profile	Private-by-default proof management and selective sharing
Add verification to an app	Hosted sign-in, API, SDK, and React widgets
Sell protected access	Published checks, price, hosted checkout, and a server confirmation
Set limits on an AI agent	Owner, optional spend account, allowed and denied actions, expiry, and revocation

Choose a path

Add the hosted MCP remote, then click Connect.

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. Full steps: MCP setup.

Path	Next step
MCP client	Connect NEUS
App	Hosted sign-in
Sell access	Recipe
Agent limits	Agents

---

Live surfaces

Surface	Use it for
Product	Profiles, gates, and hosted product UX
Hosted sign-in	Browser verification for people and orgs
Proofs	Portable records of identity, authority, and outcomes
SDK (@neus/sdk)	Issue, poll, and check proofs from your app
Widgets	VerifyGate and ProofBadge for React products
API	Server reads, checks, verifier catalog, and verification endpoints
Agents	Agent identity, permissions, and proof history
MCP	Profile, checks, proofs, and permissions in any MCP client. Registry metadata: @neus/mcp-server
Examples	Runnable app and agent samples
Verifier catalog	Live check IDs and inputs

Capability snapshot

The live verifier catalog is documented at docs.neus.network/verification/verifiers. JSON Schemas live in docs/verifiers/schemas/; the machine index is spec/VERIFIERS.json.

Capability	Verifiers
Ownership and identity	ownership-basic, ownership-social, ownership-dns-txt, ownership-org-oauth, ownership-pseudonym
Human and wallet trust	proof-of-human, wallet-risk, wallet-link
Assets and contracts	token-holding, nft-ownership, contract-ownership
Content and safety	ai-content-moderation
Agent trust	agent-identity, agent-delegation

This repository

Public docs, SDK (@neus/sdk), MCP registry package (@neus/mcp-server), widgets, examples, specs, and the neus-mcp plugin (setup).

Open standard

NEUS is a reference implementation of CAIP-380 (Portable Proof) (PR), a ChainAgnostic standard at Draft status. Wallet-signed request envelopes use a deterministic SHAKE-256 hash (qHash), CAIP-2 chain context, and CAIP-10 / did:pkh identities. The hash, DID binding, and signature can be checked without NEUS. Verifier outcomes remain part of the NEUS portable proof. The envelope works with any CAIP-2 namespace and that chain’s native signing scheme. See Standards & interoperability, the offline examples, the CAIP-380 docs, and the Technical Whitepaper.

Support

Channel	Use for
Docs	Product and integration guidance
Changelog	Release notes and upgrade paths
Platform	Hosted product, API, and upgrade path
Discussions	Questions and implementation patterns
Issues	Bugs and requests
SECURITY.md, dev@neus.network	Vulnerability disclosure

Status

NEUS is under active development. Published APIs and verifier schemas may change between minor versions. Breaking changes are listed in the changelog.

Audit

Smart contracts were audited by SafeStack AI in March 2026. The audit completed with no critical, high, medium, or low severity findings. See the Trust Center for details.

Partners and programs

• Webacy, ZKPassport, Phala Network: integration partnerships for verification, zero-knowledge identity, and confidential compute
• NVIDIA Inception: early-stage AI startup program
• Google for Startups: cloud and AI startup program
• Optimism Retro Funding Season 8: grant recipient

License

All code in this repository is Apache-2.0, including the reference smart contracts. The CAIP-380 specification is released under CC0 1.0. NEUS names and logos are protected trademarks; see TRADEMARKS.md.