Skip to main content
Glama

Maryland Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Maryland Code — state statutes by citation.

Glama couldn't complete the latest health check. 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.1% over 22 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-maryland-code
GitHub Stars
0
Server Listing
mcp-maryland-code

TDQS

A3.9/5.0

Scored across 38 tools

Disambiguation3/5

Many tools are clearly distinct (md_code_section, company_facts, validate_claim), but there is overlap among ask_pipeworx, ask_pipeworx_beta (currently identical), ask_pipeworx_grounded, and deep_research, plus several closely related prediction-market tools (polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread). Long descriptions help, but some pairs could be confused.

Naming Consistency2/5

Naming is a mix of verb-noun (ask_pipeworx, resolve_entity), noun-only (company_facts, entity_profile), prefixed (polymarket_edges, md_code_section), and generic single words (remember, forget, subscribe). All are snake_case, but the pattern is inconsistent and some names are vague.

Tool Count2/5

38 tools is heavy for the apparent scope, and the server name 'Maryland Code' suggests a narrow domain while the tools span data lookups, prediction markets, memory, subscriptions, and feedback. Many tools could be consolidated (e.g., the multiple ask_pipeworx variants).

Completeness4/5

The broad domain of structured data research and prediction-market analysis is well covered with multiple entry points, entity resolution, comparisons, arbitrage checks, and subscription management. Gaps exist but are minor (e.g., no direct open-web search; some soft-failing sources).

Tool Schema Changelog

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

  1. 38 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 observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedmd_articles
    • First observedmd_code_section
    • 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

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