Skip to main content
Glama
onefreeman1337

OSF - Open Source Filings

by onefreeman1337
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to OSF - Open Source Filings

No user-submitted related servers found.

    Related Servers

    • Verilex Data

      carrierone
      A
      license
      B
      quality
      C
      maintenance
      Query 20 structured datasets from AI agents — healthcare providers (9M NPI records), SEC EDGAR filings, PACER federal courts, USPTO patents and trademarks, OFAC sanctions screening, crypto whale wallets, DeFi liquidation signals, Polymarket smart money, economic indicators (FRED/BLS), federal contracts, NOAA weather, and OTC shell risk scoring. Pay per query, no subscriptions
      75
      1
      MIT

    • compliance-mcp

      FoundryNet
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides regulatory and compliance intelligence from free government sources, including rules, recalls, enforcement actions, and comment deadlines, classified by industry and severity.
      MIT

    • gov-transparency-mcp

      forgemeshlabs
      A
      license
      A
      quality
      A
      maintenance
      MCP server for US government transparency data (congressional trades, federal contracts, campaign finance, lobbying, regulations) with per-call paid access via x402 USDC.
      10
      54 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: each search_* tool targets a different data domain (e.g., patents, aircraft, AI models), and lookup/screening tools are specific. A few pairs like screen_entity vs screen_entity_free and get_record vs sample_record are near-duplicates, but their descriptions clearly explain the differences (paid vs free, full vs sample).

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (search_*, get_*, screen_*, lookup_*, check_*, is_*). The convention is uniform and predictable across all 21 tools, making it easy for an agent to infer the action and domain from the name.

    Tool Count4/5

    At 21 tools, this is on the heavier side but justified by the server's very broad scope—it aggregates data across many distinct verticals (security, sanctions, SEC, economic, legal, healthcare, etc.). Each tool has a specific domain and purpose, so none feels redundant or gratuitous.

    Completeness5/5

    The tool surface is comprehensive: free search tools across diverse domains, lookup and screening tools for entity verification, and paid record retrieval with sampling. There are no obvious dead ends—search results include record_ids that lead cleanly to get_record, and screening tools provide thorough, audit-ready outputs.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources