MCP server list / NEUS MCP
NEUS hosted MCP: verifiers, proofs, verify flows, agents. Always call neus_context first.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 273 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 258 ms.
- Address
- https://mcp.neus.network/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.neus/
neus-mcp - Transport
- streamable HTTP
streamable-http - Host
mcp.neus.network
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- neus-mcp
- Version:
- 1.3.9
- MCP features it lists:
- tools, elicitation
- Tool names:
neus_contextneus_verifiers_catalogneus_proofs_checkneus_verifyneus_verify_or_guideneus_proofs_getneus_meneus_agent_linkneus_agent_createneus_agent_mountneus_secret_createneus_secret_listand 1 more
neus_secret_revoke- Instructions excerpt:
- 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_v…
Reported Aug 17, 2026, 05:04 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 249 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 511 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 288 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 258 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.