Skip to main content
Glama

Server Details

Île-de-France (Greater Paris) Events MCP.

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
49.4% over 38 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-idf-events
GitHub Stars
0

TDQS

A3.8/5.0

Scored across 37 tools

Disambiguation3/5

Most tools target distinct resources and actions, but there are several overlapping families: the three ask_pipeworx variants serve nearly identical purposes, and the five polymarket_* tools plus bet_research all concern prediction-market opportunities. Company-facing tools (entity_profile, compare_entities, company_facts, recent_changes) also share boundaries that could cause misselection, though their detailed descriptions help.

Naming Consistency3/5

The set mixes conventions: many tools use verb-first names (ask_pipeworx, compare_entities, generate_llms_txt, validate_claim), while others use noun/domain-first names (company_facts, entity_profile, polymarket_arbitrage, resolution_audit) or bare nouns (events). Within the Pipeworx/Polymarket families the prefixes are consistent, but across the full set the pattern is inconsistent, though names remain descriptive and readable.

Tool Count2/5

At 37 tools, the set is heavy, and the vast majority are unrelated to the server's stated 'Idf Events' purpose—only one tool addresses Île-de-France events. Even as a general data-access server, 37 tools is at the high end and could be consolidated; for an events-focused server it is a severe scope mismatch.

Completeness2/5

For the events domain implied by the server name, the surface is severely incomplete: a single search tool with no event details, categories, venue information, or lifecycle operations. For the actual Pipeworx data domain, coverage is strong, but the mismatch between the server label and the tool set leaves obvious gaps relative to the stated purpose.

Tool Schema Changelog

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

  1. 5 tool updates
    • Addedcompany_facts
    • Addedkalshi_weather_edge
    • Addedrelease_calendar_markets
    • Addedresolution_audit
    • Addedresolution_diff
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "market": "will-bitcoin-reach-100k-in-july-2026"
        -  },
        -  {
        -    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
        -  }
        -]New value: +[
        +  {
        +    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.