GeoNames MCP — GeoNames geographical database API
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.
Scored across 35 tools
Descriptions are extraordinarily detailed and do heavy lifting, but several clusters genuinely overlap: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research are four routers (beta explicitly 'currently matches ask_pipeworx exactly'), six polymarket_* tools plus bet_research share arbitrage/edge purposes, and scan_competitor_ai_presence wraps ai_visibility_check. An agent can usually pick correctly by reading carefully, but the boundaries require long descriptions rather than clean separation.
Nearly everything is snake_case with a verb_noun shape (search_geonames, find_postal_codes, resolve_entity, validate_claim, get_timezone). Topical prefixes (ask_pipeworx_, polymarket_, scan_) are applied consistently and aid grouping. Minor deviations are noun-only names (remember, recall, forget, subscribe) that omit a verb, which is acceptable for lifecycle tools.
35 tools is heavy for any single server and includes redundancy: three near-identical ask_pipeworx routers, six polymarket tools with overlapping scan/edge/fill purposes, and both ai_visibility_check and scan_competitor_ai_presence. The gateway scope justifies breadth, but consolidation would clearly improve it.
The surface is unusually broad and mostly closes loops: full memory CRUD (remember/recall/forget), full subscription lifecycle (subscribe/list_subscriptions/unsubscribe/recent_alerts), discovery, feedback, grounded verification, and a deep polymarket trading suite. Minor gaps exist (no explicit resource-read tool, no update for stored memories), but agents can work around them.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput schema / examplesPrevious 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"
+ }
+]Input schema / properties / market / descriptionPrevious 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."polymarket_kalshi_spread1 field changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]bet_research2 fields changedInput schema / examplesPrevious 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"
+ }
+]Input schema / properties / market / descriptionPrevious 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."polymarket_kalshi_spread1 field changedInput schema / properties / topic / descriptionPrevious 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."Geo MCP — geographic utilities from free public APIs
Free GeoNames MCP: countries, cities, POIs, distance & nearby. Remote HTTP + agent token signup.
OpenStreetMap Overpass MCP — programmatic queries against the OSM database
Add one secure layer between your agents and this server.