EODHD MCP server
Compare daily prices, delayed quotes and financial highlights for a selected ticker using your licensed market data access. Access is gated: request enablement for your organization before connecting.
Agent workflows for EODHD.
Get end-of-day prices
Use when you need daily OHLCV and adjusted closes for one ticker within 366 days. OHLC is unadjusted. Costs 1 API call; retries may spend again. HTTP 402 means daily quota exhausted; resets at midnight GMT. Use and redistribute only as licensed by EODHD.
Get delayed quote
Use when you need a delayed OHLCV quote for one ticker. Indicative data is not for trading execution. Costs 1 API call. HTTP 402 means daily quota exhausted; resets at midnight GMT. Use and redistribute only as licensed by EODHD.
Get equity fundamental highlights
Use when you need equity financial highlights; unavailable sections return null. Requires fundamentals entitlement; costs 10 API calls, including retries. HTTP 402 means daily quota exhausted; resets at midnight GMT. Use and redistribute only as licensed by EODHD.
7 EODHD actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
7Look things up, subject to your permissions.
- eodhd.eodGet end-of-day prices
Use when you need daily OHLCV and adjusted closes for one ticker within 366 days. OHLC is unadjusted. Costs 1 API call; retries may spend again. HTTP 402 means daily quota exhausted; resets at midnight GMT. Use and redistribute only as licensed by EODHD.
- eodhd.quoteGet delayed quote
Use when you need a delayed OHLCV quote for one ticker. Indicative data is not for trading execution. Costs 1 API call. HTTP 402 means daily quota exhausted; resets at midnight GMT. Use and redistribute only as licensed by EODHD.
- eodhd.fundamentalsGet equity fundamental highlights
Use when you need equity financial highlights; unavailable sections return null. Requires fundamentals entitlement; costs 10 API calls, including retries. HTTP 402 means daily quota exhausted; resets at midnight GMT. Use and redistribute only as licensed by EODHD.
- eodhd.searchFind instruments
Use when you need up to 20 active instruments by symbol, name or ISIN. No match may return not found (provider_not_found). Costs 1 API call. HTTP 402 means daily quota exhausted; resets at midnight GMT. Use and redistribute only as licensed by EODHD.
- eodhd.exchangesList exchanges
Use when you need EODHD exchange codes for ticker suffixes or search filters, including virtual exchanges. Costs 1 API call. HTTP 402 means daily quota exhausted; resets at midnight GMT. Use and redistribute only as licensed by EODHD.
- eodhd.dividendsGet dividend history
Use when you need dividend history for one ticker within 366 days. Check dividend currency against quote currency; dates may be absent. Costs 1 API call. HTTP 402 means daily quota exhausted; resets at midnight GMT. Use and redistribute only as licensed by EODHD.
- eodhd.splitsGet split history
Use when you need split history for one ticker within 366 days. Ratios retain new-shares/old-shares notation. Costs 1 API call. HTTP 402 means daily quota exhausted; resets at midnight GMT. Use and redistribute only as licensed by EODHD.
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Control access to EODHD.
After early access is enabled, connect the intended EODHD account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How EODHD connects.
Connect EODHD using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use EODHD with your AI client.
Request access to EODHD first. An Arc0 administrator must enable it for your organization before these actions appear. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
EODHD with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpEODHD with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpEODHD with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpEODHD with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpEODHD with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpEODHD with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
EODHD and Arc0, answered.
Does EODHD work with Claude Desktop and Claude Code?
Yes, after early access is enabled for your organization and you connect the intended account. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.
Can I use EODHD with OpenAI Codex, ChatGPT and Cursor?
Yes, after early access is enabled for your organization and you connect the intended account. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.
Is this the official EODHD MCP server?
This is Arc0’s integration page, not a claim of an official EODHD server. Arc0 adds a shared connection, policy and audit experience across apps. Consult EODHD for its own current MCP offerings.
Which EODHD actions are supported?
7 registry-defined actions: 7 read, 0 write and 0 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.
Which permissions does EODHD need?
Connect EODHD using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
Can I restrict writes in EODHD?
You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.
What does EODHD through Arc0 cost?
See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.
Request EODHD access.
EODHD MCP server: 7 actions including get end-of-day prices, get delayed quote, get equity fundamental highlights. Request early access through Arc0.
Free to build · MCP + REST · Audit log on every plan
EODHD and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by EODHD.