Skip to main content
Glama

West Virginia Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

West Virginia 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 21 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-west-virginia-code
GitHub Stars
0
Server Listing
west-virginia-code

TDQS

A3.6/5.0

Scored across 37 tools

Disambiguation3/5

Most tools have distinct purposes, but the ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded trio creates real ambiguity (beta is explicitly identical right now), and the polymarket_* family overlaps heavily. The single WV law tool is clearly distinct but is buried among 36 unrelated data tools.

Naming Consistency2/5

All names are snake_case, but there is no consistent verb_noun pattern: bare verbs (remember, forget, recall, subscribe), noun-first names (entity_profile, release_calendar_markets), and prefix families (ask_*, polymarket_*, pipeworx_*) are mixed without a unifying convention. The naming feels like an accreted toolkit rather than a designed API surface.

Tool Count1/5

37 tools for a server named 'West Virginia Code' is an extreme mismatch — only one tool (wv_code_section) relates to West Virginia law, while the other 36 constitute a general-purpose data and prediction-market platform. The count is far beyond what the stated purpose needs and would overwhelm an agent trying to answer a simple legal citation question.

Completeness1/5

For the apparent domain (West Virginia Code), the surface is severely incomplete: there is no search, no table of contents, no title/chapter listing, no amendment history, and no cross-referencing — just one fetch-by-citation tool. The unrelated Pipeworx tools are individually comprehensive, but they do nothing to cover the server's named domain.

Tool Schema Changelog

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

  1. 37 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 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
    • First observedwv_code_section

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