Docs  /  MCP Server

MCP Server

Divergence exposes a Model Context Protocol server for AI agents, IDE extensions, and any MCP-compatible client. It gives you structured, tool-based access to the same data the REST API serves — without writing HTTP requests or parsing JSON by hand.

Supported clients include Claude Desktop, Cursor, Windsurf, and any framework that speaks the MCP Streamable HTTP transport.

Endpoint

https://divergence.duckdns.org/mcp/mcp

Protocol: MCP Streamable HTTP transport. Not a REST endpoint — connect through an MCP client, not curl.

What you get

  • 9 tools covering market news, ticker lookup, portfolio scanning, editorial divergence, keyword search, and full event detail
  • 1 resource (divergence://agent-guide) with score interpretation tables, tool selection guide, and example workflows
  • The same data as the REST API, shaped for tool calls rather than HTTP responses

What this is not

  • Not a real-time stream. The pipeline runs every 30 minutes. Tool results reflect the latest completed ingest.
  • Not unauthenticated. Every connection requires a Bearer token. See Authentication.
  • Not a substitute for the REST API when you need bulk data. For large result sets or historical queries, use /api/v2/events.

Getting started

  1. Get a Bearer token — Authentication
  2. Connect your MCP client to https://divergence.duckdns.org/mcp/mcp with the token in the Authorization header
  3. Call get_digest() to verify the connection and see today's market summary