Skip to main content
mcpFirst-partyLow risk Safety Privacy
Daloopa logo

Daloopa MCP Server for Claude

Access high-quality fundamental financial data from SEC filings and investor presentations

HarnessClaude CodeCodexCursorClaude Desktop

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://docs.daloopa.com/docs/daloopa-mcp, https://github.com/JSONbored/awesome-claude/blob/main/content/mcp/daloopa-mcp-server.mdx
Brand
Daloopa
Brand domain
daloopa.com
Brand asset source
brandfetch
Package URL
/downloads/mcp/daloopa-mcp-server.mcpb
Package SHA256
3862b42d9655eff41883b09966e5f1007b51271479fb8d423b3c2c8f44876d98
Safety notes
Treat financial data as informational research and verify figures before using them for investment, accounting, or reporting decisions.
Privacy notes
Company queries, filing references, financial models, and research topics may be sent through the MCP client and model.
Author
Daloopa
Claim status
unclaimed
Last verified
2025-09-18

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

2 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

10 to clear

Platforms

4 listed

Difficulty

0/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

10 prerequisites to line up before setup. Have accounts and credentials ready first.

0/10 ready
Account & credentials3Network & hosting2General52 minutes

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 1 risk area.

1 area
  • SafetyGeneralTreat financial data as informational research and verify figures before using them for investment, accounting, or reporting decisions.
  • PrivacyGeneralCompany queries, filing references, financial models, and research topics may be sent through the MCP client and model.

Safety notes

  • Treat financial data as informational research and verify figures before using them for investment, accounting, or reporting decisions.

Privacy notes

  • Company queries, filing references, financial models, and research topics may be sent through the MCP client and model.

Prerequisites

  • Daloopa account with active subscription
  • Daloopa API key (obtained from Daloopa sales team - contact sales@daloopa.com)
  • Internet connection for accessing Daloopa MCP server (https://mcp.daloopa.com/server/mcp)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Understanding of SEC filings, financial statements, and financial metrics
  • Knowledge of ticker symbols and company identifiers (e.g., AAPL, MSFT)
  • Understanding of financial data formats (quarterly/annual periods, e.g., Q1 2024)
  • HTTP transport support (remote MCP server, not local stdio)
  • Awareness of subscription tier limitations (coverage universe, data availability dates)
  • Understanding of pagination for large datasets and payload optimization

Schema details

Install type
package
Reading time
1 min
Difficulty score
0
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
3862b42d9655eff41883b09966e5f1007b51271479fb8d423b3c2c8f44876d98
Skill and platform metadata
Retrieval sources
https://docs.daloopa.com/docs/daloopa-mcp
Collection metadata
Estimated setup
2 minutes
Difficulty
beginner
Full copyable content
{
  "daloopa": {
    "url": "https://mcp.daloopa.com/server/mcp",
    "transport": "http"
  }
}

About this resource

Content

Access comprehensive financial data and SEC filing information through Daloopa's curated database.

Features

  • Access SEC filing data and documents
  • Retrieve financial statements and metrics
  • Query investor presentations
  • Analyze historical financial data
  • Compare company metrics across periods
  • Advanced Daloopa data extraction and automation with intelligent document parsing, spreadsheet analysis, and workflow automation
  • Batch operations support for efficient bulk data extraction, processing, and transformation with automatic rate limit handling and retry logic
  • Real-time data synchronization capabilities with webhook integration support for monitoring extraction jobs and triggering automated workflows

Use Cases

  • Analyze quarterly earnings data
  • Compare financial metrics across companies
  • Build financial models with accurate data
  • Track KPI trends over time
  • Research investment opportunities
  • Build automated data extraction workflows that sync external systems with Daloopa for real-time document processing and data transformation

Installation

Claude Code

  1. claude mcp add --transport http daloopa https://mcp.daloopa.com/server/mcp
  2. Verify installation: claude mcp list
  3. Test connection: claude mcp status daloopa

Claude Desktop

  1. Open Claude Desktop configuration file
  2. Add the Daloopa server configuration with HTTP transport
  3. Restart Claude Desktop
  4. Authenticate with your Daloopa account

Requirements

  • Daloopa account with active subscription
  • Daloopa API key (obtained from Daloopa sales team - contact sales@daloopa.com)
  • Internet connection for accessing Daloopa MCP server (https://mcp.daloopa.com/server/mcp)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Understanding of SEC filings, financial statements, and financial metrics
  • Knowledge of ticker symbols and company identifiers (e.g., AAPL, MSFT)
  • Understanding of financial data formats (quarterly/annual periods, e.g., Q1 2024)
  • HTTP transport support (remote MCP server, not local stdio)
  • Awareness of subscription tier limitations (coverage universe, data availability dates)
  • Understanding of pagination for large datasets and payload optimization

Configuration

{
  "daloopa": {
    "url": "https://mcp.daloopa.com/server/mcp",
    "transport": "http"
  }
}

Examples

Get Apple's latest 10-K filing data

Common usage pattern for this MCP server

Ask Claude: "Get Apple's latest 10-K filing data"

Compare revenue growth across tech companies

Common usage pattern for this MCP server

Ask Claude: "Compare revenue growth across tech companies"

Extract key metrics from investor presentation

Common usage pattern for this MCP server

Ask Claude: "Extract key metrics from investor presentation"

Show historical EBITDA margins

Common usage pattern for this MCP server

Ask Claude: "Show historical EBITDA margins"

Extract Data from Document

Extract structured data from a document using Daloopa extraction templates

// Extract data from document using Daloopa
const result = await daloopa.extract({
  document_url: "https://example.com/document.pdf",
  extraction_template: "invoice",
  fields: ["invoice_number", "date", "amount", "vendor"],
});

Security

  • OAuth authentication for access
  • Respect data licensing agreements
  • Monitor API usage limits
  • Cache frequently accessed data
  • Daloopa API keys and access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
  • Daloopa document URLs and extraction templates may expose data sources and extraction patterns - ensure Daloopa resource identifiers are kept private and not shared in public configurations
  • Rate limiting and API quota management are critical for Daloopa MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
  • Daloopa webhook configurations and payloads may contain sensitive document data and extraction results - ensure webhook endpoints are properly secured with authentication and HTTPS encryption
  • Daloopa extraction results may contain sensitive business data - ensure extraction results are properly secured and access-controlled according to data privacy requirements

Troubleshooting

Authentication error: API key invalid or missing

Add Authorization header with your API key to all requests. Contact Daloopa sales team to obtain or regenerate API key. Verify key is copied correctly without extra spaces or line breaks.

Company data not found or unavailable

Verify ticker symbol is correct and company is in Daloopa coverage universe. Check your subscription tier includes access to requested company data. Contact Daloopa support for coverage questions.

Financial metrics missing for specific periods

Confirm company has filed SEC documents for requested period. Check data availability dates for your subscription tier. Verify quarter/year format matches API requirements (e.g., Q1 2024).

API requests timing out or running slowly

Reduce payload size by limiting fields returned in response. Implement pagination for large datasets. Check network connectivity and consider caching frequently accessed data locally.

Daloopa MCP server authentication errors with API keys

Verify API key is valid and not expired. Check API key permissions match required operations. Ensure API key format is correct (Bearer token in Authorization header). Regenerate API key from Daloopa dashboard if needed.

Daloopa extraction job failures or timeouts

Check document format is supported (PDF, Excel, Word, etc.). Verify document is accessible and not password-protected. Ensure network connectivity is stable. For large documents, use chunked processing with resumable extraction support.

Daloopa MCP server rate limiting or throttling errors

Implement exponential backoff retry logic with jitter. Use Daloopa API rate limit headers to monitor usage. Reduce concurrent extraction requests. Cache frequently accessed extraction templates. Request rate limit increases from Daloopa support if needed.

Daloopa MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify Daloopa API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

Source citations

Add this badge to your README

Show that Daloopa MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/daloopa-mcp-server.svg)](https://heyclau.de/entry/mcp/daloopa-mcp-server)

How it compares

Daloopa MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

2 trust signals differ across this comparison (Package trust, Submitter).

Field

Access high-quality fundamental financial data from SEC filings and investor presentations

Open dossier

Python MCP server that lets Claude query Financial Datasets for stock statements, prices, company news, crypto prices, and SEC filings.

Open dossier

Streamable HTTP MCP server for financial research workflows, including standardized financial data, SEC filing search, company discovery, market signals, ticker resolution, and alternative-data table exploration.

Open dossier

Local MCP server for the edgartools Python library, letting Claude search, parse, read, compare, and analyze SEC EDGAR filings, companies, ownership, funds, proxy statements, notes, trends, and live filing feeds.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1oktofeesh1oktofeesh1
Install riskLow riskReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandDaloopa logoDaloopaFinancial Datasets logoFinancial DatasetsDrillr logoDrillr
Categorymcpmcpmcpmcp
Sourcefirst-partysource-backedsource-backedsource-backed
AuthorDaloopaFinancial DatasetsDrillrDwight Gunning
Added2025-09-182026-06-052026-06-052026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesTreat financial data as informational research and verify figures before using them for investment, accounting, or reporting decisions.This server retrieves financial market data; do not treat tool output or model summaries as investment, trading, tax, or legal advice. Current prices, crypto prices, filings, and news can be delayed, incomplete, rate limited, or unavailable depending on API plan and market conditions. Review generated analysis before using it in portfolio decisions, trading workflows, client reports, or compliance-sensitive research. The server sends ticker symbols, date ranges, filing filters, and research queries to the Financial Datasets API.Drillr's MCP endpoint is a remote Streamable HTTP server at `https://gateway.drillr.ai/mcp/data` and requires a bearer API key. Tool calls can consume Drillr credits or billable API usage. Check plan limits and remaining credit balance before high-volume research loops. run_sql is documented as read-only SELECT access, but broad queries across 90-plus tables can still be expensive, slow, or noisy. Treat outputs as research inputs, not investment, legal, accounting, tax, or trading advice. Drillr documents that it does not place trades, manage brokerage positions, expose options chains, or provide its own price forecasts. Review cited SEC filing paragraphs, table schemas, ticker resolution, and source coverage before relying on results in reports or decisions.edgartools MCP can query live SEC filings, parse structured filing data, search filing text, monitor recent filings, compare companies, inspect ownership, and extract proxy or fund information. SEC EDGAR access requires an identity string and can be rate-limited if automated requests are too frequent or unidentified. Filing analysis can produce plausible financial, legal, governance, compensation, or risk conclusions that still require expert review. The local server is stateless, but remote HTTP transport deployments still need normal network access controls if shared with a team. Do not treat model-generated summaries as investment advice, legal advice, accounting advice, or a substitute for reading the filing source.
Privacy notesCompany queries, filing references, financial models, and research topics may be sent through the MCP client and model.API keys must be stored in environment variables or local secret managers and never committed to configuration files. Queried tickers, crypto symbols, time ranges, filings, and news requests can reveal research interests, watchlists, client assignments, or trading hypotheses. Tool outputs may include financial statements, prices, filings, and news that become part of the model context and logs. Avoid sending private portfolio holdings, customer identifiers, or material non-public information through prompts or tool arguments.Prompts, ticker lists, research themes, SQL queries, and retrieved financial context are sent to Drillr's hosted gateway and the connected MCP client. Drillr API keys are sensitive credentials. Keep them out of prompts, shared configs, issue comments, logs, screenshots, and repository files. Research prompts may reveal portfolio interests, watchlists, investment theses, client names, diligence topics, or confidential strategy. SEC filing excerpts, analyst consensus, alt-data, market signals, and generated summaries may be retained by MCP clients, AI providers, logs, or downstream tools. Use synthetic prompts or public tickers for demos, screenshots, and examples when client, portfolio, or internal research strategy is sensitive.Tool inputs can reveal watchlists, portfolio interests, deal research, diligence targets, litigation topics, trading hypotheses, or compliance questions. Tool outputs can expose filing excerpts, insider transactions, institutional holdings, compensation data, financial metrics, and query strategy in the MCP client transcript. EDGAR_IDENTITY includes a name and email address; keep it scoped to approved automation and avoid committing it to source control. If using hosted edgar.tools services instead of the local server, review the hosted service's tier, retention, processing, and data-use terms separately.
Prerequisites
  • Daloopa account with active subscription
  • Daloopa API key (obtained from Daloopa sales team - contact sales@daloopa.com)
  • Internet connection for accessing Daloopa MCP server (https://mcp.daloopa.com/server/mcp)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Python 3.11 or newer, matching the upstream project metadata.
  • uv installed on the machine running the MCP server.
  • A cloned checkout of `financial-datasets/mcp-server`.
  • Financial Datasets API key stored as `FINANCIAL_DATASETS_API_KEY`.
  • Drillr account at `https://drillr.ai`.
  • External-scope Drillr API key from `https://drillr.ai/developer/keys`.
  • MCP client that supports Streamable HTTP servers with bearer headers.
  • Secure secret storage for `DRILLR_API_KEY` outside prompts, repository files, screenshots, and shell history.
  • Python 3.10 or newer and `uvx` available, or the `edgartools[ai]` package installed.
  • EDGAR_IDENTITY set to the name and email required for automated SEC EDGAR access.
  • Network access to SEC EDGAR endpoints and patience for rate limits or transient filing fetch failures.
  • Understanding of the filing forms, companies, sections, and time periods being analyzed.
Install
claude mcp list && claude mcp status daloopa
uv run server.py
claude mcp add drillr https://gateway.drillr.ai/mcp/data --transport http --header "Authorization: Bearer $DRILLR_API_KEY"
claude mcp add edgartools -- uvx --from "edgartools[ai]" edgartools-mcp
Config
{
  "mcpServers": {
    "daloopa": {
      "url": "https://mcp.daloopa.com/server/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "financial-datasets": {
      "command": "uv",
      "args": ["--directory", "PATH_TO_FINANCIAL_DATASETS_MCP", "run", "server.py"],
      "env": {
        "FINANCIAL_DATASETS_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "drillr": {
      "type": "http",
      "url": "https://gateway.drillr.ai/mcp/data",
      "headers": {
        "Authorization": "Bearer ${DRILLR_API_KEY}"
      }
    }
  }
}
{
  "mcpServers": {
    "edgartools": {
      "command": "uvx",
      "args": ["--from", "edgartools[ai]", "edgartools-mcp"],
      "env": {
        "EDGAR_IDENTITY": "Your Name your.email@example.com"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.