Skip to main content
Glama

Opentripmap

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

OpenTripMap MCP — wraps the OpenTripMap Places API (dev.opentripmap.org)

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

TDQS

A3.6/5.0

Scored across 40 tools

Disambiguation2/5

The tool set mixes a small coherent OpenTripMap POI group (5 tools) with a large, heavily overlapping Pipeworx data-access family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions) and a sprawling prediction-market cluster (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, release_calendar_markets). Several tools have near-identical purposes (ask_pipeworx vs ask_pipeworx_beta; entity_profile vs company_facts vs compare_entities; remember/recall/forget are fine but unrelated to the server's apparent domain). An agent would frequently struggle to pick the right one.

Naming Consistency2/5

The OpenTripMap tools follow a clean opentripmap_* prefix pattern, but the rest of the set mixes styles: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded (verb_phrase), entity_profile, company_facts, compare_entities (noun_phrase), polymarket_arbitrage, polymarket_edges, polymarket_fill_risk (noun_phrase with inconsistent suffixes), and generic verbs like remember, forget, recall, subscribe, unsubscribe. There is no single predictable convention across the server.

Tool Count2/5

40 tools is far too many for a server ostensibly named 'Opentripmap' — only 5 of them are actually OpenTripMap tools. The remaining 35 are a grab-bag of Pipeworx data lookup, prediction-market analysis, memory, subscription, and feedback utilities. The count is not just high; it is misaligned with the server's apparent purpose.

Completeness3/5

The OpenTripMap subset is reasonably complete for POI discovery (geoname, places_radius, autosuggest, place_detail), though it lacks obvious operations like searching by text/name globally or filtering by more attributes. The Pipeworx side is broad but has no clear boundary — it includes memory, subscriptions, feedback, and trending tools that are unrelated to the data-access domain, while still missing obvious operations like a direct 'get_company_financials' tool (replaced by entity_profile/company_facts). Overall the surface is sprawling and uneven rather than complete for any single stated purpose.

Tool Schema Changelog

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

  1. 3 tool updates
    • Changedask_pipeworx3 fields changed
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
    • Changedask_pipeworx_beta3 fields changed
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
    • Changedask_pipeworx_grounded3 fields changed
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"Your question in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
  2. 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 observedopentripmap_autosuggest
    • First observedopentripmap_geoname
    • First observedopentripmap_place_detail
    • First observedopentripmap_places_radius
    • 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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources