Odel
NEUS MCP

NEUS MCP

@neus23JavaScriptApache-2.0Updated 1w ago

The trust harness for AI agents. Set what an agent can do before it acts.

View on GitHub
Server endpointStreamable HTTPOAuthProbed

This is the third-party server itself — Odel doesn't run it. Hitting this URL directly talks straight to the upstream server with no auth or proxying. Connect through Odel to front it with managed auth.

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.

@neus/sdk on npm @neus/mcp-server on npm License Discussions NEUS verified portable proof

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.

NeedWhat you get with NEUS
Reuse a completed checkA proof with source, status, scope, and expiry
Keep proofs in one profilePrivate-by-default proof management and selective sharing
Add verification to an appHosted sign-in, API, SDK, and React widgets
Sell protected accessPublished checks, price, hosted checkout, and a server confirmation
Set limits on an AI agentOwner, 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.

PathNext step
MCP clientConnect NEUS
AppHosted sign-in
Sell accessRecipe
Agent limitsAgents

Live surfaces

SurfaceUse it for
ProductProfiles, gates, and hosted product UX
Hosted sign-inBrowser verification for people and orgs
ProofsPortable records of identity, authority, and outcomes
SDK (@neus/sdk)Issue, poll, and check proofs from your app
WidgetsVerifyGate and ProofBadge for React products
APIServer reads, checks, verifier catalog, and verification endpoints
AgentsAgent identity, permissions, and proof history
MCPProfile, checks, proofs, and permissions in any MCP client. Registry metadata: @neus/mcp-server
ExamplesRunnable app and agent samples
Verifier catalogLive 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.

CapabilityVerifiers
Ownership and identityownership-basic, ownership-social, ownership-dns-txt, ownership-org-oauth, ownership-pseudonym
Human and wallet trustproof-of-human, wallet-risk, wallet-link
Assets and contractstoken-holding, nft-ownership, contract-ownership
Content and safetyai-content-moderation
Agent trustagent-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

ChannelUse for
DocsProduct and integration guidance
ChangelogRelease notes and upgrade paths
PlatformHosted product, API, and upgrade path
DiscussionsQuestions and implementation patterns
IssuesBugs and requests
SECURITY.md, dev@neus.networkVulnerability 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.