This server brings NEUS trust receipts into your AI assistant workflow. It exposes tools for agent identity registration, scoped delegation, and verification checks that produce reusable receipts you can audit later. You can import existing local agent configs from Cursor or Claude Desktop with the CLI, then link them through MCP. The flow is check, verify, save, reuse. Useful when your assistant needs to prove identity before taking actions, gate access based on ownership or risk signals, or generate durable proof pages for what happened. The same receipts work across the SDK, API, and hosted surfaces, so trust context travels between your agent stack and your apps.
The trust layer for people and AI. Portable identity, ownership, and authorization that travels.
Prove once. Reuse everywhere — shared context, clear authority, and an audit trail for every action.
Why NEUS | Start building | Live surfaces | Support
Every new app, agent, and partner usually starts from zero — no shared context about identity, ownership, or authority. NEUS turns those checks into portable trust receipts so people and AI keep context as they move, act under clear limits, and leave an audit trail behind.
A receipt is something you already earned: who someone is, what they own, what they’re allowed to do. Put it on a profile, require it at a gate, or check it from your API — same receipt, every surface.
| Need | What you get with NEUS |
|---|---|
| Stop re-proving the same facts in every product | One portable receipt apps and agents can reuse |
| Carry identity and ownership with the actor | Profiles and ownership proofs that travel across gates |
| Authorize actions with clear limits | Scoped permissions, current status, and enforce-before-act checks |
| Keep shared context for people and AI | Live trust context in the editor, product, and API |
| Audit who did what — and under which authority | Receipt pages, stable references, and reviewable history |
| Ship trust without rebuilding each flow | Hosted Verify, widgets, SDK, and MCP on one model |
Connect once. Your assistant gets portable trust context — identity, authority, and receipts — so it can reuse what’s already proven, authorize actions against real limits, and keep an audit trail without leaving the editor.
npx -y -p @neus/sdk neus setup
npx -y -p @neus/sdk neus check
Then ask your assistant:
Use NEUS so my identity, permissions, and context travel with me. Reuse receipts when you can, verify when you must, authorize actions against those limits, and leave an audit trail.
| Path | Next step |
|---|---|
| AI assistants (Cursor, Claude Code, Codex, VS Code) | Install NEUS |
| MCP setup | MCP setup · Hosted URL: https://mcp.neus.network/mcp |
| First app integration | Quickstart |
| Prove once, reuse everywhere | Integration guide |
| React gate | VerifyGate |
| Server / API | API overview |
| Agent trust | Agents overview |
Optional IDE plugin: install neus-trust@neus from this repo’s marketplace — see Install NEUS.
Drop in Hosted Verify, VerifyGate, or the SDK when your app needs portable trust — shared context at the gate, authority before access, receipts you can audit later.
Give agents identity and scoped authority as receipts — so tools run under real limits, and every action stays auditable.
agent-identity.agent-delegation.| Surface | Use it for |
|---|---|
| Product | Profiles, gates, and hosted product UX |
| Hosted Verify | Browser verification for people and orgs |
| Trust receipts | Portable records of identity, authority, and outcomes |
| SDK · @neus/sdk | Issue, poll, and check receipts from your app |
| Widgets | VerifyGate and ProofBadge for React products |
| API | Server reads, checks, verifier catalog, and verification endpoints |
| Agents | Agent identity, scoped authority, and audit-ready receipts |
| MCP | Portable trust context in the editor — neus setup; registry metadata: @neus/mcp-server |
| Examples | Runnable app and agent samples |
| Verifier catalog | Live check IDs and inputs |
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 |
Public docs, SDK (@neus/sdk), MCP registry package (@neus/mcp-server), widgets, examples, specs, and the neus-trust Claude Code / Cursor plugin (install).
The receipt envelope is specified as CAIP-380 (Portable Proof), an open ChainAgnostic standard submission. Receipts are verifiable against the spec independently of NEUS infrastructure — see the CAIP-380 PR, JSON schemas, and NEUS docs.
| Channel | Use for |
|---|---|
| Docs | Product and integration guidance |
| Changelog | Release notes and upgrade paths |
| Platform status | Maturity, beta scope, and upgrade expectations |
| Discussions | Questions and implementation patterns |
| Issues | Bugs and requests |
| SECURITY.md · dev@neus.network | Vulnerability disclosure |
ray0907/git-mcp-server
cyanheads/git-mcp-server
io.github.b1ff/atlassian-dc-mcp-bitbucket
io.github.b1ff/atlassian-dc-mcp-jira
com.mcparmory/atlassian-jira
sirlordt/vscode-terminal-mcp