Bosco Labs data: MCP server
One MCP server that gives AI agents official-source data: SEC insider trades and filings, US House members' stock trades, Pentagon contract awards, EU public tenders and the financials of European companies. Each tool runs one of the Bosco Labs Apify Actors with your own Apify token and returns a short JSON list with a source link on every row.
Tools
| Tool | Data (source) | Price per row | Example question |
|---|---|---|---|
eu_annual_report_financials |
Audited financials of EU/UK listed companies (ESEF reports, filings.xbrl.org) | $0.05 + $0.01 per call | "Compare ASML's and Heineken's latest revenue and operating margin." |
european_company_accounts |
Accounts of UK, Danish and Norwegian companies, incl. private (Companies House, Erhvervsstyrelsen, Brønnøysund) | $0.04 | "What were the revenue and equity of Danish company CVR 24256790 in recent years?" |
sec_insider_trades |
Form 4 insider purchases and sales since 2006, cluster buys and sells (SEC EDGAR) | $0.0018 | "Have NVIDIA insiders bought or sold shares in the last month?" |
sec_filings |
Any EDGAR filing since 1994: 8-K items, 10-K, 10-Q, earnings release times (SEC EDGAR) | $0.001 | "When did Apple last release earnings, and was it after the close?" |
us_house_stock_trades |
STOCK Act trades of House members since 2014 (Clerk of the House) | $0.0018 | "What stocks did Nancy Pelosi trade this year?" |
eu_public_tenders |
EU/EEA public tenders and contract awards (TED) | $0.002 | "Find open IT-services tenders in Germany and the Netherlands from this week." |
dod_contract_awards |
DoD (or any federal agency) contract awards since FY2008, with winner tickers (USAspending.gov) | $0.005 | "Which Pentagon contracts did Kratos win this year?" |
Every tool has a max_results parameter with a small default (3 to 25 rows) and a hard
maximum, so one call costs cents. dod_contract_awards can take a minute or more.
Two other Bosco Labs Actors are not tools here because they work on your own Apify datasets or Google credentials: Dedup & Merge Datasets and Google Sheets Export. Use them on Apify directly.
Pricing
You pay Apify per row returned, with your own token, at the prices above (the free Apify plan includes monthly credit). The server itself is free and sends nothing anywhere else.
Install
- Get an Apify API token: https://console.apify.com/settings/integrations
- Install uv.
- Add the server to your client (below). Once the package is on PyPI the command is
uvx bosco-labs-data-mcp. Until then, run it from this folder:uvx --from /path/to/bosco-labs-data/mcp bosco-labs-data-mcp.
Claude Desktop
claude_desktop_config.json (Settings -> Developer -> Edit Config):
{
"mcpServers": {
"bosco-labs-data": {
"command": "uvx",
"args": ["bosco-labs-data-mcp"],
"env": { "APIFY_TOKEN": "apify_api_..." }
}
}
}
Cursor
~/.cursor/mcp.json (or .cursor/mcp.json in a project): the same mcpServers block as
above.
Claude Code
claude mcp add bosco-labs-data -e APIFY_TOKEN=apify_api_... -- uvx bosco-labs-data-mcp
Alternative: Apify's hosted MCP server
Without installing anything, you can use the same Actors through Apify's own MCP server (OAuth or your token; each Actor becomes a tool with its full input):
https://mcp.apify.com?tools=Bosco_labs/esef-annual-reports,Bosco_labs/company-accounts,Bosco_labs/sec-insider-trades,Bosco_labs/sec-filings-feed,Bosco_labs/us-house-trades,Bosco_labs/eu-tenders,Bosco_labs/dod-contract-awards
This server is the lighter option: typed parameters, small defaults and compact results.
Development
uv run --with pytest pytest -q # from this folder; Apify is mocked, plus a stdio smoke test
Source and releases: https://github.com/PB7-debug/bosco-labs-data (folder mcp/). Releases are
published to PyPI and the official MCP Registry by the publish-mcp.yml GitHub Actions
workflow; see
PUBLISHING.md.
Metadata
Release files for bosco-labs-data-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bosco_labs_data_mcp-0.1.0.tar.gz | 12.5 kB | With provenance | Details for bosco_labs_data_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bosco_labs_data_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for bosco_labs_data_mcp-0.1.0-py3-none-any.whl |
Total release size: 25.5 kB
Release files / bosco_labs_data_mcp-0.1.0.tar.gz
| Download URL | bosco_labs_data_mcp-0.1.0.tar.gz |
|---|---|
| Size | 12.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ac376d3d7a8b7b6df937a082f29273aa32322889a8c444687cd80c225b35069
|
|
BLAKE2b-256 checksum How to use checksums |
1087728d4d566018cf3b7190710ce5df66701f7ee7fdbb333e40f038af791067
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / bosco_labs_data_mcp-0.1.0-py3-none-any.whl
| Download URL | bosco_labs_data_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab2f2d2437882222627de34524a48ffda634123b26c7c732d362c5ff3a43f6f4
|
|
BLAKE2b-256 checksum How to use checksums |
e8ad9b14de5475be7bec8e43392c6041da9537369fa1d935f8b06deb0cd5f3f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logSecurity for bosco-labs-data-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for bosco_labs_data_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.