Skip to main content
Glama

Crs Reports

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Congressional Research Service reports — Congress's own nonpartisan analysis, searchable and…

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.2% over 33 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-crs-reports
GitHub Stars
0
Server Listing
crs-reports

TDQS

A4/5.0

Scored across 40 tools

Disambiguation3/5

Several tools overlap in purpose: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions, while entity_profile, company_facts, recent_changes, compare_entities, and validate_claim all touch company data. Detailed descriptions help clarify boundaries, but an agent can still misselect among the router variants or the dense family of prediction-market tools.

Naming Consistency4/5

All tool names use snake_case with no camelCase mixing, so the convention is consistent. However, the verb_noun pattern is not strictly followed—some are noun phrases (company_facts, entity_profile, pipeworx_feedback) while others are verb_noun (list_subscriptions, validate_claim)—making it mostly consistent but with minor deviations.

Tool Count2/5

Forty tools is far beyond the 15-tool sweet spot and includes many overlapping meta/helper tools. For a server named 'Crs Reports' the breadth is excessive and makes the set feel unfocused rather than well-scoped.

Completeness4/5

The set covers CRS reports thoroughly (search, recent, report, topics) and provides broad cross-domain research, entity resolution, memory, subscriptions, and feedback workflows. Minor gaps exist—e.g., no explicit update for memory beyond forget, or batch CRS operations—but agents can work around them.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedrelease_calendar_markets2 fields changed
      • addedOutput schema / properties / empty_reason
        Added value: +{
+  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
+  "type": "string"
+}
      • addedOutput schema / properties / hint
        Added value: +{
+  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
+  "type": "string"
+}
  2. 40 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcompany_facts
    • First observedcompare_entities
    • First observedcrs_recent
    • First observedcrs_report
    • First observedcrs_search
    • First observedcrs_topics
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

  • @pipeworx/congressional-documents by pipeworx-io

    @pipeworx/congressionalofficial

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    Full-text search and retrieval over official congressional documents (hearings, committee reports, Congressional Record) with citations and govinfo.gov links, designed for grounding AI answers in the official record.
    24 npm
    MIT
  • committee-releases by pipeworx-io

    committee-releasesofficial

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables searching and retrieving documents that congressional committees publish on their own websites, including press releases, oversight letters, staff reports, and interview transcripts, with no authentication required.
    144 npm
    MIT

  • oravan

    cm2489
    A
    license
    A
    quality
    A
    maintenance
    Remote MCP server for nonpartisan U.S. Congress data: plain-language bill decodes (bilingual EN/ES), representative lookup by ZIP with district-office phones, and what's-moving urgency ranking. Read-only, keyless.
    5
    1
    AGPL 3.0
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources