Nexus402 speaks MCP. Point your client's base URL at the gateway, add one header, and tool discovery, argument schemas and streaming all work as they already do.
Configuration#
{
"mcpServers": {
"nexus402": {
"url": "https://api.nexus402.dev/v1/mcp",
"headers": {
"X-Nexus-Api-Key": "nx_dev_..."
}
}
}
}Which methods are billed#
| Method | Billed | Notes |
|---|---|---|
tools/call | Yes | The only billed method. Charged once at the version's fixed price |
tools/list | No | Discovery is free |
initialize | No | Protocol negotiation |
| Anything else | No | Unrecognised methods are refused rather than forwarded |
Your own Authorization header#
If the tool needs its own credential — an API key for the service it wraps — send it in Authorization and the gateway forwards it untouched. The creator sees it; we do not inspect or store it.
Streaming#
Server-sent events work. The gateway relays creator output without buffering the whole response, so you see tokens as they are produced. A tool that goes quiet for five seconds is cut; a tool that keeps producing can run for up to two minutes.