Skip to main content
Glama

Server Details

WHO Regional Office for Europe — Data Warehouse API v5.

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-who-euro
GitHub Stars
0
Server Listing
@pipeworx/who-euro

TDQS

A3.6/5.0

Scored across 42 tools

Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical, and the six polymarket_* tools plus bet_research blur together. entity_profile, recent_changes, and company_facts also cover overlapping company-data territory, making misselection likely.

Naming Consistency3/5

Most tools use snake_case with a verb_noun structure (validate_claim, resolve_entity, search_within), but conventions vary: some are bare verbs (forget, recall, remember), some are brand-prefixed (ask_pipeworx, who_euro_*), and some are noun-first (bet_research, entity_profile, company_facts). Readable but not a consistent pattern.

Tool Count2/5

42 tools is a heavy surface for any single server, and the count is inflated by a large prediction-market cluster (6+ tools), a memory/subscription subsystem, and a WHO Europe module that could each be their own server. The count creates cognitive load and increases the chance of picking the wrong tool.

Completeness3/5

The data-lookup surface is genuinely rich (universal router, grounded answers, deep research, entity resolution, claim validation), but the server is named 'Who Euro' while most tools have nothing to do with the WHO European Region. The WHO Europe toolset itself (list datasets, search measures, fetch data, metadata) is complete, yet the overall set lacks a coherent stated purpose, leaving the completeness question ill-defined.

Tool Schema Changelog

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

  1. 42 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 observedwho_euro_countries
    • First observedwho_euro_dataset_measures
    • First observedwho_euro_list_datasets
    • First observedwho_euro_measure_data
    • First observedwho_euro_measure_metadata
    • First observedwho_euro_search_measures

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.