Integrations · Market data

Connect Daloopa to Well

Bring Daloopa's structured financial line items, segment data, and operating KPIs into Well, joined to the companies you model.

What Well pulls from Daloopa

Daloopa feeds financial fundamental, company, filing into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Daloopa’s access.

From DaloopaIn Well
Financial fundamental
Research input
Company
Investment
Filing
Audit attachment
Daloopa logo
Sync mode
MCP hybrid
Refresh
live + reconciliation reads
Direction
Daloopa → Well

What Well does with your Daloopa connection

Connect

Connect Daloopa over OAuth (MCP DCR): Well registers a client through Daloopa's OAuth Dynamic Client Registration and you approve on Daloopa's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings financial fundamental, company, and filing in from Daloopa on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Daloopa entity into research input, investment, and audit attachment, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Daloopa lands in the workspace as research input, investment, and audit attachment you can search, chart, and automate.

Questions Daloopa unlocks

Ask in plain language. Well answers from your connected Daloopa connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Daloopa connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your Daloopa connection…

Connect Daloopa in three steps

  1. 01

    Authorise Daloopa via MCP

    From Well's Connections panel, search for Daloopa and click Connect. Well discovers Daloopa's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Daloopa's side. No client credentials to paste.

    • AuthOAuth (MCP DCR)
    • DiscoveryMCP .well-known
    • MCP servermcp.daloopa.com/server/mcp
  2. 02

    Map your entities

    Well's MCP client discovers financial fundamental, company, and filing from Daloopa that Daloopa's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    Ask questions in conversation, build records tables, or let agents act on Daloopa records. Because Daloopa ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.

    • First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Daloopa records happens in the background.

How Daloopa stays secure with Well

Well connects to Daloopa's MCP server (mcp.daloopa.com/server/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Daloopa secret. Tokens are scoped to the financial fundamental, company, and filing Daloopa exposes and refreshed server-side. Reads only, Well cannot modify or delete Daloopa records.

OAuth (MCP DCR)Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requestsmcp.daloopa.com/server/mcp
  • Read Daloopa records

    Resources the Daloopa MCP server exposes, scoped by your OAuth approval.

    granted
  • Resolve financial fundamental, company, and filing across your stack

    Match identifiers in Daloopa against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Modify or delete Daloopa records

    Not granted; Daloopa is read-only in Well. Write-back is opt-in per connector when a write surface exists.

    refused
  • Store Daloopa passwords or session cookies

    Authentication runs through OAuth (MCP DCR) tokens we never see.

    refused
Disconnect any time from Well settings or Daloopa’s admin panel.

Frequently asked questions about Daloopa and Well

From Well, open Connections, find Daloopa, and click Connect. Well discovers the OAuth metadata at mcp.daloopa.com/server/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Daloopa's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in financial fundamental, company, and filing from Daloopa and reshapes each entity into your workspace: financial fundamental becomes research input; company becomes investment. Every record arrives with the source identifier preserved, so Daloopa stays the source of truth while Well lets you query the data alongside the rest of your stack.

Each Daloopa line item, segment record, and KPI is linked to the workspace company it covers. Ask "what's Globex's segment revenue trend per Daloopa" and Well returns the structured view alongside any earnings-call notes and projections in your CRM.

Each Daloopa financial fundamental is scored against the candidate research inputs in your workspace on identifier overlap, amount or quantity match, date proximity, and counterparty resolution. Matches above the auto-link confidence threshold flow through cleanly; below the threshold they queue for a one-click human review, with the most likely research input prefilled and the Daloopa source attached.

Well combines live Daloopa events with periodic reconciliation reads of financial fundamental, company, and filing. New rows appear within seconds when Daloopa pushes them; periodic reads catch anything a push missed. The first connect backfills history from Daloopa in the background.

Open Connections > Daloopa in Well and click Disconnect. Well calls Daloopa's token revocation endpoint and stops calling Daloopa immediately on its side; provider-side propagation to Daloopa's admin panel varies by provider. The financial fundamental, company, and filing Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Daloopa records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.

Daloopa logo

Ready to connect Daloopa?

Connect once. Every financial fundamental, company, filing from Daloopa becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.