Data Rennes
Server Details
Rennes Métropole Open Data (data.rennesmetropole.fr) — OpenDataSoft MCP.
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.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-data-rennes
- GitHub Stars
- 0
- Server Listing
- mcp-data-rennes
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Descriptions are unusually explicit about when to prefer one tool over another (company_facts vs entity_profile vs compare_entities; ask_pipeworx vs grounded vs deep_research), which rescues a set that would otherwise be a minefield. However, genuine overlaps remain: ask_pipeworx, ask_pipeworx_beta and ask_pipeworx_grounded are near-identical routers (beta currently byte-equivalent to stable), and polymarket_edges, polymarket_arbitrage and bet_research all scan for opportunities with overlapping output shapes. Agents must read long prose to pick correctly rather than recognizing distinct tool purposes.
Mostly snake_case, but conventions are mixed: verb_noun (search_datasets, validate_claim, resolve_entity), noun-phrase (entity_profile, company_facts, polymarket_edges, updown_venue_compare), and bare verbs (query, recall, remember, forget, subscribe, unsubscribe, unsubscribe). Prefixing is also uneven — ask_pipeworx, pipeworx_feedback and pipeworx_trending disagree on where the namespace goes, and the Rennes-pack tools (query, search_datasets, dataset_info) share no visible family prefix. Still readable, just not predictable.
47 tools is far past the comfortable range for a single connection, and the set is a gateway aggregator rather than a coherent domain surface. Several tools look expendable (ask_pipeworx_beta, scan_competitor_ai_presence as a thin wrapper over ai_visibility_check, generate_llms_txt sitting oddly beside financial/market data tools). The three Rennes Métropole Open Data tools are well-scoped but are a tiny island in a very large catalog.
Core lifecycles are covered: memory (remember/recall/forget), subscriptions (subscribe/list/unsubscribe/recent_alerts), discovery (discover_tools/suggest_questions), and feedback all have full round trips. But descriptions repeatedly point at tools that are not in this surface — get_company_financials, polymarket_market, kalshi_market, polymarket_us_search, fetch_url, fomc_calendar — leaving dead-end instructions an agent cannot follow. No batch variants exist for research_row/classify_row despite being framed as row-over-many workflows.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Nantes Métropole Open Data (data.nantesmetropole.fr) — OpenDataSoft MCP.
Tours Métropole Open Data (data.tours-metropole.fr) — OpenDataSoft MCP.
Toulouse Métropole Open Data (data.toulouse-metropole.fr) — OpenDataSoft MCP.
Angers Loire Métropole Open Data (data.angers.fr) — OpenDataSoft MCP.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for querying and exploring Issy-les-Moulineaux open data datasets (city services, mobility, environment) via OpenDataSoft API.84 npmMIT
- AlicenseNot gradedqualityBmaintenanceDataCambridge MCP — Cambridge open data (data.cambridgema.gov, Socrata SODA API).157 npmMIT
- AlicenseAqualityDmaintenanceMCP server for exploring French public open data via APIs like data.gouv.fr, geo.api.gouv.fr, INSEE Sirene, and Radio France.11MIT
- AlicenseNot gradedqualityCmaintenanceToulouse Métropole Open Data MCP server. Enables searching datasets, retrieving metadata, and querying records using ODSQL.85 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.