Skip to main content
Glama

Virginia Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Code of Virginia — state statutes by citation.

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.3% over 35 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-virginia-code
GitHub Stars
0
Server Listing
virginia-code

TDQS

A3.9/5.0

Scored across 37 tools

Disambiguation3/5

The prediction-market tools overlap heavily: polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, and polymarket_kalshi_spread all deal with edge/arbitrage/spread detection and could be confused despite distinct nuances. Similarly ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research form a cluster where selection depends on subtle quality/latency tradeoffs. Other tools are clearly distinct.

Naming Consistency3/5

Most names follow snake_case, but the set mixes clear verb_noun patterns (generate_llms_txt, validate_claim, resolve_entity) with domain-noun names (entity_profile, company_facts, recent_changes) and vendor-prefixed cluster names (ai_visibility_check, kalshi_weather_edge, scan_dependency). Readable but no single predictable convention.

Tool Count2/5

37 tools is heavy for a single connector, and several are near-duplicates (ask_pipeworx vs ask_pipeworx_beta vs ask_pipeworx_grounded; the five polymarket_* analysis tools). The breadth spans GDP-scale unrelated domains (statutes, AI marketing, npm deps, prediction markets), making the surface feel like several servers bundled together.

Completeness4/5

The surface is unusually complete across its domain — entity resolution, profiles, comparisons, memory, subscriptions, feedback, and meta-tools all have coverage. Minor gaps: no direct tool-listing introspection beyond discover_tools/suggest_questions, and the memory tools lack a bulk list-update, but nothing critical is missing.

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. 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 observedva_code_section
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

  • west-virginia-code

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables retrieval of West Virginia Code statutes by citation from the official state legislature data, supporting both direct tool calls and natural-language queries.
    19 npm
    MIT

  • west-virginia-rules

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables searching and reading West Virginia's Code of State Rules — finding agency rules by agency, rule family, authorizing statute or full text, and retrieving current and historical versions with their filing history and full rule text. Covers only the administrative regulations (with licensing data for individuals out of scope).
    MIT
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