How do AI agents use EODHD through Open Connector?

Your user connects EODHD once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes EODHD tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a EODHD MCP server?

Yes. Open Connector can serve EODHD as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call EODHD actions with credentials injected server-side.

Where do EODHD credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

EODHD integration

EODHD integration for AI agents.

EODHD integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves EODHD tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real EODHD actions, managed and audited.

Your user connects EODHD once; your agent can then access real-time, historical, and end-of-day market data for stocks, ETFs, funds, and forex. Developer-friendly APIs, SDKs, OpenAPI docs, and AI-ready integrations. 60+ exchanges, 150K+ tickers — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants EODHD access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported EODHD tools.

0 tools are generated from the published EODHD catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 0 tools. All published catalog entries are included in this page's server-rendered HTML.

No tools match “”.

FAQ

EODHD integration, answered

How do AI agents use EODHD through Open Connector?: Your user connects EODHD once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes EODHD tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a EODHD MCP server?: Yes. Open Connector can serve EODHD as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call EODHD actions with credentials injected server-side.
Where do EODHD credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents EODHD — keep the keys.

Open source, self-hostable, with EODHD credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →