The MCP URL and the HTTP API use different transports and base paths. Discovery and the agent card list what your integration needs.
MCP endpoint
| URL | Role |
|---|
https://mcp.neus.network/mcp | MCP — Setup |
OAuth discovery
| URL | Role |
|---|
https://mcp.neus.network/.well-known/oauth-protected-resource | Protected resource metadata (RFC 9728) |
https://neus.network/.well-known/oauth-authorization-server | Authorization server metadata (RFC 8414) |
OAuth endpoints
| URL | Role |
|---|
https://neus.network/oauth/authorize | Authorization endpoint (browser login) |
https://neus.network/api/v1/auth/mcp/token | Token endpoint (code exchange + refresh) |
https://neus.network/api/v1/auth/mcp/revoke | Token revocation |
Other discovery
| URL | Role |
|---|
https://mcp.neus.network/.well-known/mcp.json | MCP discovery |
https://mcp.neus.network/.well-known/mcp/server-card.json | MCP server card |
https://neus.network/.well-known/a2a/agent-card.json | Platform A2A agent card — Docs |
https://neus.network/.well-known/agent-card.json | EIP-8004 agent registration |
MCP OAuth
OAuth flow reference.
Setup
Install and configure.
Last modified on May 29, 2026
