network

mcp
Security Audit
Warn
Health Pass
  • License — License: NOASSERTION
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 10 GitHub stars
Code Warn
  • process.env — Environment variable access in .github/workflows/release.yml
Permissions Pass
  • Permissions — No dangerous permissions requested
Purpose
This is an open trust infrastructure platform that generates portable proof receipts for apps, APIs, and AI agents. It allows developers to verify user identity, content, or wallet ownership once and reuse that verified status across their entire software stack.

Security Assessment
The overall risk is rated as Low. The repository does not request dangerous permissions, nor does it appear to execute shell commands or contain hardcoded secrets. The tool's core functionality inherently requires making network requests to fetch and validate receipts via the NEUS API. There is a noted warning regarding `process.env` access, but this is safely confined to a GitHub Actions release workflow for CI/CD pipelines rather than the application's runtime code.

Quality Assessment
The project is in a very early stage, reflected by a low community trust metric of only 10 GitHub stars. However, it is under active development, with the most recent code push occurring today. The project states it uses the permissive Apache-2.0 license, though the automated scanner flagged it as unasserted, likely due to a minor repository configuration issue. Overall, it is well-documented and actively maintained.

Verdict
Safe to use, but keep in mind it is an early-stage project with a small community footprint.
SUMMARY

Open trust infrastructure for apps, APIs, and agents. Verify once, then reuse proof receipts for identity, access, content, and payments.

README.md

NEUS

NEUS

Verify once. Prove everywhere.
Portable proof receipts for apps, APIs, and agents.

npm License Discussions

Quickstart · Docs · API Reference · MCP · Examples


Every app makes you re-verify. That's why bots win and users lose.

NEUS fixes it: verify once, get a portable proof receipt, reuse it everywhere. Gate access, attach proof to content, register agents with scoped permissions — private by default, public when you choose.

Auth got standardized (OAuth). Payments got standardized (Stripe). Verification is still bespoke. NEUS standardizes it into one receipt.

Why NEUS

  • Stop re-verifying. One check produces a receipt your whole stack can trust
  • Gate access with proof, not auth spaghetti. One line of code replaces custom verification logic
  • Proof travels, data stays private. Share the result without exposing underlying data
  • Ship trust in minutes. Drop-in SDK, widgets, and API — not months of infra
  • Works for people and agents. Same receipt format for human users and AI agents

How it works

 ┌──────────┐     ┌──────────────┐     ┌──────────────────┐
 │  Verify  │ ──▶ │ Get receipt  │ ──▶ │  Reuse anywhere  │
 │          │     │   (proofId)  │     │                  │
 │ wallet,  │     │  portable,   │     │ gate, share,     │
 │ social,  │     │  private by  │     │ post, automate,  │
 │ identity │     │  default     │     │ delegate         │
 └──────────┘     └──────────────┘     └──────────────────┘

Quick start

npm install @neus/sdk
import { NeusClient } from '@neus/sdk';

const client = new NeusClient();

// 1. Verify
const proof = await client.verify({
  verifier: 'ownership-basic',
  content: 'My content',
  wallet: window.ethereum,
});

// 2. Save the receipt
const proofId = proof.proofId;

// 3. Reuse — check eligibility from anywhere
const check = await client.gateCheck({
  address: '0x...',
  verifierIds: ['ownership-basic'],
});
// check.data.eligible → true/false

No wallet in your app? Use Hosted Verify — redirect or popup, zero wallet code.

What you can build

Use case How Verifier
🛡️ Human-only access Block bots at signup proof-of-human
🎨 NFT / token gated products Gate by on-chain holdings nft-ownership · token-holding
✅ Verified creator badges Prove authorship, bind to wallet ownership-basic
🏢 Org-verified teams Prove domain or org membership ownership-dns-txt · ownership-org-oauth
🤖 Agent identity + delegation Register agents, scope permissions agent-identity · agent-delegation
📝 Proof-backed content Attach proof to posts and listings ownership-basic + proofId

Start here

I want to… Go to
Try it in 5 minutes Quickstart
Add verification with no code Hosted Verify
Gate content in React Widgets
Check proofs from my server API Reference
Add trust to AI agents MCP
Set up platform + billing Get Started

Integration paths

Path Best for Effort
Hosted Verify Login, guided verification Redirect / popup — no UI to build
Widgets React gating + badges <VerifyGate> — one component
SDK Custom flows Full programmatic control
API Server-side checks HTTP from any language
MCP AI agents (Cursor, Claude) One URL — https://mcp.neus.network/mcp

Gate content in React

import { VerifyGate } from '@neus/sdk/widgets';

<VerifyGate requiredVerifiers={['nft-ownership']}
  verifierData={{ 'nft-ownership': { contractAddress: '0x...', tokenId: '1', chainId: 1 } }}>
  <PremiumContent />
</VerifyGate>

AI agents (MCP)

Add NEUS to any MCP-compatible agent with one URL:

{
  "mcpServers": {
    "neus": { "url": "https://mcp.neus.network/mcp" }
  }
}

Agents verify users via hosted links that tools return. Setup guide →

Documentation

Resource Description
Quickstart First proof in 5 minutes
Verifier catalog All verification types
API reference HTTP endpoints
SDK reference JavaScript SDK
Examples React, Node.js, curl

Community

Channel
GitHub Discussions Questions and ideas
GitHub Issues Bug reports
[email protected] Security disclosures

License

  • SDK & tools: Apache-2.0
  • Smart contracts: BUSL-1.1 → Apache-2.0 (Aug 2028)

Reviews (0)

No results found