Skip to main content
Use this path when you need your own auth, policy, or UI controls around DZap tools.

​
Endpoint

https://nlp-ai-439689868940.europe-north1.run.app/mcp 
Your app/agent -> client policy layer -> DZap MCP (/mcp) -> tools -> response

​
Practical rollout

  1. Start with read-only tools (PriceTool, TokenAddressTool, BalanceTool).
  2. Add retrieval/search tools (RagOverDocsTool, WebSearchTool).
  3. Add execution-sensitive tools only with explicit confirmation UX.
  4. Persist tool call logs and sessionId for auditability.

​
Minimal remote config pattern

{
  "mcpServers": {
    "dzap": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://nlp-ai-439689868940.europe-north1.run.app/mcp"]
    }
  }
}
If the server is protected with DZAP_MCP_HTTP_TOKEN, pass the bearer token as a header: 
{
  "mcpServers": {
    "dzap": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://nlp-ai-439689868940.europe-north1.run.app/mcp",
        "--header", "Authorization: Bearer ${DZAP_MCP_HTTP_TOKEN}"
      ]
    }
  }
}
A raw HTTP client sends the same header directly: 
curl -X POST "https://nlp-ai-439689868940.europe-north1.run.app/mcp" \
  -H "Authorization: Bearer $DZAP_MCP_HTTP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"my-client","version":"1.0"}}}'

​
Session notes

  • Initialize creates an MCP session.
  • Reuse mcp-session-id on follow-up requests.
  • Send DELETE /mcp to close session state cleanly.
Last modified on June 18, 2026