Bosco Labs Data
OfficialRelated Servers
Alternatives to Bosco Labs Data
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceStandalone Python 3.11 MCP stdio server exposing 31 read-only B2B regulatory compliance, KYB/AML sanctions, GLEIF LEI, US SEC EDGAR, openFDA, NHTSA, CISA KEV, ICANN RDAP, and Brazil fiscal audit tools.1MIT
- AlicenseAqualityBmaintenanceRead-only MCP server for official U.S. House stock disclosures, saved synthetic portfolio snapshots, and period changes with source and timing metadata. Requires an approved Capitol Ledger pilot API key; runs locally over stdio with no trade execution.3MIT
- AlicenseAqualityDmaintenanceMCP server for querying US federal contracts and public company financial data from USAspending and SEC EDGAR. Enables searching expiring contracts, screening companies by metrics, and retrieving financial histories.4MIT
- AlicenseAqualityDmaintenanceMCP server for EU company and business data. 9 tools: company search (GLEIF, 2M+ entities), LEI lookup, corporate structures (parent/subsidiaries), trade register search, EU VAT validation (VIES), GDP, unemployment, inflation, and business demography (Eurostat). All APIs free, no keys required.96MIT
- AlicenseNot gradedqualityBmaintenanceBridges MCP clients to a hosted service exposing 64 read-only tools over US public records, covering SEC filings and insider trades, congressional trades and campaign finance, lobbying, federal contracts and grants, FDA and other regulatory enforcement, company fundamentals, prices, and cross-collection search. Every call is forwarded upstream so published disclosures can be queried by ticker, CIK, name, or date range without storing anything locally.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients such as Claude Code and Claude Desktop to research US public company SEC filings by looking up companies and filings, searching and reading filing pages, querying SEC XBRL concepts and facts, and running an exact calculator with named inputs. Runs over stdio or streamable HTTP, sharing the agent's exact tool definitions and code path.7MIT
TDQS
Scored across 9 tools
Each tool targets a distinct source/geography/entity type: GLEIF identification, SEC company lookup, EU ESEF reports, UK/DK/NO registry accounts, SEC filings, SEC insider trades, House trades, EU tenders, DoD awards. The only realistic confusion is between the two financial-statement tools (get_eu_annual_reports vs get_company_accounts), and the descriptions resolve it via geography and listed-vs-private coverage. Identification tools (get_lei_record name search vs find_sec_company name search) overlap slightly but clearly map to different registries.
Names consistently follow verb_noun with a source qualifier (get_/find_/search_ + sec/eu/us/dod + resource), making the pattern predictable. The get vs find vs search distinction is mostly meaningful (direct record vs identification vs filtered query), though get_lei_record also does fuzzy name search, which blurs the verb semantics a little.
Nine tools is well within the sweet spot, and each covers a distinct data source with no filler or near-duplicates. Nothing appears to be a thin wrapper that could be merged into another tool.
The surface covers company identification, EU/UK/DK/NO financials, SEC filings, insider trades, congressional trades, EU tenders and DoD awards, but conspicuously lacks US company financial statements (10-K/10-Q XBRL fundamentals), which is the natural next step after find_sec_company and is instead pushed to paid calls. Senate disclosures are also absent by design, leaving agent workflows that need US fundamentals or Senate trades at a dead end.