NEUS MCP
NEUS hosted MCP: verifiers, proofs, verify flows, agents. Always call neus_context first.
https://mcp.neus.network/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- neus-mcp
- Version
- 1.3.9
- Capability keys
- tools, elicitation
- Tool names
- neus_context, neus_verifiers_catalog, neus_proofs_check, neus_verify, neus_verify_or_guide, neus_proofs_get, neus_me, neus_agent_link, neus_agent_create, neus_agent_mount, neus_secret_create, neus_secret_list, neus_secret_revoke
NEUS MCP connects assistants to reusable identity, ownership, and permission proofs. Start with neus_context once per session. When a tool allows the wallet to be omitted, use the signed-in profile. For a trust request, check existing proofs with neus_proofs_check before using neus_verify_or_guide. Use neus_proofs_get for current proof records and neus_verifiers_catalog for check IDs and required inputs. Share a NEUS browser link only when a tool returns one. Summarize the result as Passed, Action needed, or Blocked. Run neus setup for OAuth sign-in. Profile access keys are intended for servers and automation; never ask a user to paste credentials into chat. Proofs remain offchain by default. Set options.publishToHub only when the user explicitly asks for a blockchain record. Never invent proof IDs, check IDs, statuses, accounts, or URLs. Public MCP tools include neus_context, neus_verifiers_catalog, neus_proofs_check, neus_verify, neus_verify_or_guide, neus_proofs_get, neus_me, n
Reported Aug 17, 2026, 05:04 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 249ms
- respondsMCP initialize · 8s limit · HTTP 200 · 511ms
- respondsMCP initialize · 8s limit · HTTP 200 · 288ms
- respondsMCP initialize · 8s limit · HTTP 200 · 258ms