Neus Mcp

Name: Neus Mcp
Author: neus

by neuscommunityv1.1.7

NEUS provides a trust verification platform for apps and agents, including reusable trust receipts, hosted verification flows, SDK/API support, and MCP access to trust context and proof data. The repository includes docs, the @neus/sdk package, widgets, examples, specs, and Claude Code skill metadata.

From the registry: NEUS MCP: identity, authority, trust receipts, and Vault secrets before sensitive AI actions.

GitHub Repository Website

Install & configure

Prerequisites

required
Node.js and npm
Install Node.js and npm so you can run the NEUS CLI via npx for setup and diagnostics.
optional
Optional NEUS Profile access key
Create or obtain a NEUS Profile access key if you want account-aware MCP tools such as `neus_me`.
https://docs.neus.network/mcp/setup

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `neus-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Node.js and npm** — Install Node.js and npm so you can run the NEUS CLI via npx for setup and diagnostics.

Optional prerequisites:
- Optional NEUS Profile access key — Create or obtain a NEUS Profile access key if you want account-aware MCP tools such as `neus_me`. (https://docs.neus.network/mcp/setup)

Canonical MCP server config (HTTP transport):
- url: `https://mcp.neus.network/mcp`
- headers:
  - `Authorization`: `Bearer <your-neus-profile-access-key>`

Note: The README states all MCP hosts connect to the same hosted endpoint and references manual JSON and headers in the MCP setup docs. It explicitly documents the hosted MCP URL and mentions an optional access key that enables account-aware tools. No required headers are shown directly in the README, so the Authorization header is included as optional based on the access-key guidance.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: The README states all MCP hosts connect to the same hosted endpoint and references manual JSON and headers in the MCP setup docs. It explicitly documents the hosted MCP URL and mentions an optional access key that enables account-aware tools. No required headers are shown directly in the README, so the Authorization header is included as optional based on the access-key guidance.