Market data · https://eodhd.com/api
set up treg — https://treg.to/llms.txt
claude mcp add --transport http treg https://treg.to/mcp
Settings → Connectors → add https://treg.to/mcp as a custom connector.
Add https://treg.to/mcp as a remote MCP connector in its tool settings.
Settings → Connectors → Add custom connector → https://treg.to/mcp.
Point it at https://treg.to/mcp (HTTP transport).
curl -fsSL https://treg.to/install.sh | sh
LangChain, CrewAI or any code: /call/<tool-id> with a Bearer token. No SDK.
Using treg, end-of-day price history for a ticker. Show me the price first.
curl -H "Authorization: Bearer $TREG_TOKEN" \ "https://treg.to/call/eodhd.eod"
Connect once; treg.to keeps the credential server-side and injects it per call. No key on any machine.
The provider's own rate, $0.000 markup. How billing works.
Charged per call. $1.00 free per new team, no card to start.
Register it and those calls are never metered. Your key always wins.
Another provider is a different word in the prompt, not a new integration.
The same token calls Finnhub, Marketstack, Polygon.io and ~2,600 other tools.
eodhd.eodeodhd.real-timeeodhd.exchangesReliability badges come from live traffic through treg.to, not a controlled benchmark.
Yes. This is an own-account connection: you sign in to EODHD once and your agent uses that connection through your treg.to token. Calls on it are never metered.
Run: claude mcp add --transport http treg https://treg.to/mcp — one MCP server carries EODHD and the rest of the catalog.
Anything that speaks MCP (Claude Code, Claude Desktop, ChatGPT, Codex, Cursor, Grok) and anything that can make an HTTP request (LangChain, CrewAI, LlamaIndex, plain code).
No. treg.to serves EODHD's real API through its own metered proxy: the request is the provider's own, the credential is injected server-side, and the answer is relayed verbatim. The official EODHD channels are linked above.