Skip to main content
Glama

Photon

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Photon MCP — OSM geocoder

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
45.4% over 38 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-photon
GitHub Stars
0
Server Listing
mcp-photon

TDQS

A3.7/5.0

Scored across 33 tools

Disambiguation3/5

The descriptions do a lot of work routing between tools, but the meta-tool cluster is genuinely fuzzy: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, compare_entities, entity_profile, and validate_claim all funnel through the same 5,961-tool router with overlapping 'answer a question about X' purposes. Similarly bet_research, polymarket_arbitrage, polymarket_edges, and polymarket_edge_tracker all surface prediction-market opportunities with subtle distinctions only spelled out in long prose. An agent can usually pick right, but misselection between the ask_* family and between the polymarket scanners is a real risk.

Naming Consistency4/5

Nearly everything is lowercase snake_case, which is consistent and readable. Deviations are stylistic rather than structural: some names are verb_noun (generate_llms_txt, scan_dependency, validate_claim, resolve_entity), while others are bare nouns/verbs that don't signal their action (search, reverse, recall, remember, forget). The polymarket_* and ask_pipeworx_* prefixes are used sensibly as groupings.

Tool Count3/5

At 33 tools this is heavy for a single MCP surface and sits above the comfortable 3-15 band. Because the server is a universal data gateway spanning 1552 sources, the breadth partly justifies the count, and most tools map to a distinct capability family (research, identity, memory, subscriptions, prediction markets, discovery, geocoding). Still, the six-tool polymarket cluster and the five ask/research meta-tools push it toward over-provisioned.

Completeness4/5

Coverage is broad and self-consistent: full memory lifecycle (remember/recall/forget), full subscription lifecycle (subscribe/unsubscribe/list_subscriptions/recent_alerts), discovery (discover_tools/suggest_questions/trending), identity resolution, comparison, verification, and a deep prediction-market suite. Gaps are minor — there is no explicit raw schema/lookup primitive beyond discover_tools, and no bulk/export or batch variant, but core workflows have no obvious dead ends.

Tool Schema Changelog

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

  1. 1 tool update
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]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 (\"when-will-bitcoin-hit-150k\"), 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."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."
  2. 2 tool updates
    • Changedbet_research1 field changed
      • 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 (\"when-will-bitcoin-hit-150k\"), 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."
  3. 1 tool update
    • Changedbet_research1 field 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": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]

Related MCP Connectors

Related MCP Servers

  • chuk-mcp-geocoder

    IBM
    A
    license
    A
    quality
    C
    maintenance
    An MCP server providing geocoding and place discovery services via Nominatim and OpenStreetMap. It enables users to perform forward and reverse geocoding, extract bounding boxes, and find nearby places or administrative hierarchies.
    10
    Apache 2.0

  • geocode-mcp

    danishashko
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for geocoding, reverse geocoding, place/POI search, and distance calculation using OpenStreetMap Nominatim, with no API key required.
    47 npm
    1
    MIT
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