Skip to main content
Glama

Server Details

State attorney-general multistate enforcement, from the National Association

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

TDQS

A3.8/5.0

Scored across 40 tools

Disambiguation3/5

Several clusters have hazy boundaries: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical routers, and polymarket_arbitrage, polymarket_edges, and polymarket_edge_tracker all find/analyze market edges. The extremely detailed descriptions help differentiate them, but an agent could easily misselect without reading carefully.

Naming Consistency4/5

All tool names are lowercase snake_case, and many follow verb_noun (compare_entities, resolve_entity, validate_claim) or domain-prefix patterns (naag_*, pipeworx_*, polymarket_*, ask_pipeworx). The mix of noun-phrase names like company_facts and single-word verbs like remember/forget is a minor deviation but still predictable and readable.

Tool Count2/5

40 tools is well over the reasonable threshold for a cohesive server. While the surface is broad (legal data, prediction markets, company research, memory, subscriptions, AI visibility, dev tools), 40 tools imposes a heavy discovery and selection burden, especially multiple near-duplicate routers and market scanners.

Completeness3/5

Core workflows are largely covered: memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list/recent_alerts, and prediction markets have a research-to-fill-risk pipeline. However, several tool descriptions reference tools not present in this server (e.g. polymarket_market, kalshi_market), and the stated NAAG domain (evident from the server name) only has 4 of 40 tools, leaving obvious gaps.

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 observednaag_case_detail
    • First observednaag_multistate_cases
    • First observednaag_policy_letters
    • First observednaag_press_releases
    • 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

Glama MCP Gateway

Add one secure layer between your agents and this server.