Daloopa MCP server icon

Daloopa

by Daloopa

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Finance9 tools

Pull SEC-sourced fundamentals, filing text and stock prices into an AI agent, with a source link on every number. Daloopa's own docs list 9 tools; Anthropic's directory lists 3. OAuth or API key, no scopes, read-only.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Daloopa via MCP

https://mcp.daloopa.com/server/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect Daloopa once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Daloopa Tools & Capabilities (9)

discover_companies
discover_company_series
get_company_fundamentals

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The licensing position is unresolved and you should resolve it yourself. Daloopa's public Terms of Use forbid exposing Content to open or public AI technology, forbid storing significant portions of it, and require that third-party providers not retain Content on their systems. The document never mentions MCP. Daloopa nonetheless ships this connector, so a separate agreement almost certainly governs — one we have not read, and which may modify those terms in either direction. Ask your account team which document controls.
  • No scopes exist, so consent cannot be narrowed. The authorization server metadata declares no scopes_supported, the RFC 9728 descriptor declares none, and the authorize endpoint's published schema accepts no scope parameter. Since the surface is read-only this costs less than it would elsewhere, but there is no way to grant fundamentals without also granting filing text.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or annotation is published here. The read-only claim rests on Daloopa's written statement and its tool descriptions.
  • Anthropic's directory entry is stale by six tools. It lists three; Daloopa documents nine. A reader who sized this connector from the directory would not know it can read filing text or return stock prices at all.
  • Coverage is bounded by your subscription, and consumption is metered. Daloopa publishes endpoints for datapoint consumption, per-company series consumption and a monthly datapoint limit, so agent queries draw down a quota. Broad exploratory prompts are the expensive case.
  • Rate limits are 120 requests per minute across the account, with HTTP 429 on exceedance. Daloopa's own guidance is to batch and cache rather than retry.
  • The plugin skills reach outside Daloopa for market data. Beta, analyst targets and consensus estimates come from web search or another connected MCP server when Daloopa lacks them. Reports can mix sourced and searched figures, so read the attribution rather than assuming everything traces to a filing.
  • Two Daloopa MCP servers exist and are easily confused. The financial-data server is mcp.daloopa.com/server/mcp, the subject of this page. A separate documentation-search server runs at docs.daloopa.com/mcp and is advertised in Daloopa's own .well-known/mcp/server-card.json. Daloopa's plugin configures both. We did not handshake the docs server.
  • The vendor's own pages disagree with each other on counts. The MCP page says "Three tools" in prose above a list of nine; the integrations page says 11 skills where the skills page tabulates 21. Prefer the enumerated lists over the prose totals.
  • Skill file-writing behaviour is inconsistently documented. Daloopa's setup skill states reports are saved to a reports/ directory, while its research-note skill instructs the agent not to save to a file. In a filesystem-capable client such as Claude Code, expect that a skill may write into your working directory.

Frequently asked questions

Nine, according to Daloopa's own documentation. Anthropic's directory listed three when we snapshotted it, and a second Daloopa page lists seven. The nine-name list is the newest and the largest, so we publish it and label its source. Because the endpoint requires authentication we could not run a handshake to settle the disagreement ourselves.

No, and Daloopa states this in writing. Its MCP privacy disclosure says MCP access is strictly read-only and that third parties cannot write to, upload to or modify Daloopa data through the protocol. Every one of the nine documented tools is a search or a fetch. The write endpoints Daloopa does operate live on its REST API, not on this server.

Daloopa's public Terms of Use say no, while Daloopa itself ships and promotes this connector. The Terms forbid exposing any Content to open or public AI technology and forbid storing significant portions of it. Those Terms never mention MCP. Subscribers are almost certainly covered by an Order Form instead, so check yours before assuming either answer.

Yes, and the server instructs the model to include them. Every fundamental datapoint carries a fundamental_id, and Daloopa's published server instructions require the model to render figures as links to daloopa.com/src/ plus that ID. Those instructions also tell the model never to fabricate an ID and to omit the link when none exists.

None whatsoever. Daloopa's authorization server metadata omits scopes_supported entirely, its RFC 9728 resource descriptor omits it too, and the published OpenAPI schema for the authorize endpoint does not accept a scope parameter at all. Consent is all-or-nothing access to whatever companies your Daloopa subscription already covers.

Yes, with a header. Daloopa documents three authentication methods: an OAuth login, a 24-hour bearer token generated from an API key, and direct API-key authentication using an X-API-KEY header sent with every request. The header approach needs no token refresh, and Daloopa publishes the exact claude mcp add command for each.

Daloopa documents 120 requests per minute counted across your whole account, with HTTP 429 returned once you exceed it. Its guidance is to batch identifiers into single calls, cache company and series structure, and pace requests at roughly two per second. Separately, your plan carries a monthly datapoint limit that the connector consumes against.

Yes, by design, in the plugin distributions. Daloopa's published skill files tell the agent to source market data from Daloopa first, then from any other MCP server you have connected, then from web search for figures like beta and analyst targets. So a Daloopa-branded report can contain numbers Daloopa never supplied.

Sources

Server Info

Category
Finance
Developer
Daloopa
Tools
9
Domain
mcp.daloopa.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.

Ready to connect Daloopa?

Connect Daloopa once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.