Install command
Provided
Access high-quality fundamental financial data from SEC filings and investor presentations
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Install command
Provided
Config snippet
Provided
Copy snippet
Provided
Prerequisites
10 to clear
Platforms
4 listed
Difficulty
0/100
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
10 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
1 safety and 1 privacy notes across 1 risk area.
{
"daloopa": {
"url": "https://mcp.daloopa.com/server/mcp",
"transport": "http"
}
}Access comprehensive financial data and SEC filing information through Daloopa's curated database.
{
"daloopa": {
"url": "https://mcp.daloopa.com/server/mcp",
"transport": "http"
}
}
Common usage pattern for this MCP server
Ask Claude: "Get Apple's latest 10-K filing data"
Common usage pattern for this MCP server
Ask Claude: "Compare revenue growth across tech companies"
Common usage pattern for this MCP server
Ask Claude: "Extract key metrics from investor presentation"
Common usage pattern for this MCP server
Ask Claude: "Show historical EBITDA margins"
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"],
});
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.
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.
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).
Reduce payload size by limiting fields returned in response. Implement pagination for large datasets. Check network connectivity and consider caching frequently accessed data locally.
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.
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.
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.
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.
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 status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | — | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Low risk | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | |||
| Category | mcp | mcp | mcp | mcp |
| Source | first-party | source-backed | source-backed | source-backed |
| Author | Daloopa | Financial Datasets | Drillr | Dwight Gunning |
| Added | 2025-09-18 | 2026-06-05 | 2026-06-05 | 2026-06-06 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓Treat 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 notes | ✓Company 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 |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.