Skip to main content
Glama

Server Details

Water Quality Portal (WQP) MCP — US ambient water-chemistry monitoring

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 17 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-water-quality-portal
GitHub Stars
0
Server Listing
water-quality-portal

TDQS

A3.8/5.0

Scored across 40 tools

Disambiguation2/5

The four wqp_* tools are distinct, but the set contains several overlapping families: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route universal questions; discover_tools and suggest_questions overlap for onboarding; polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, and polymarket_fill_risk overlap on opportunity scanning. Descriptions help, but an agent must parse many boundaries before choosing.

Naming Consistency4/5

All names use snake_case, and domain prefixes such as wqp_, polymarket_, and kalshi_ are applied sensibly, so there is no chaotic style mixing. However, conventions vary between verb_noun forms like ask_pipeworx and validate_claim and noun_phrase forms like company_facts and entity_profile, so it is not a uniform verb_noun pattern.

Tool Count2/5

40 tools is far too many for a server named Water Quality Portal; only four tools actually serve that domain. The other 36 are a broad Pipeworx platform surface, making the count a major scope mismatch.

Completeness4/5

The WQP subset covers the key read-only lifecycle: find stations, resolve controlled vocabulary, fetch sample results, and query results near a point. Some WQP metadata browsing such as organizations and projects is absent, but agents can answer the core water-quality questions without dead ends.

Tool Schema Changelog

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

  1. 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 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 observedwqp_get_results
    • First observedwqp_list_characteristics
    • First observedwqp_results_near_point
    • First observedwqp_search_sites

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.