N2YO MCP — wraps the N2YO Satellite Tracking REST API (n2yo.com)
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 34 tools
The tool set is unusually large and several meta-tools overlap: ask_pipeworx, ask_pipeworx_beta (explicitly identical to ask_pipeworx right now), ask_pipeworx_grounded, and deep_research all route the same way and differ mainly by cost/depth, while the six prediction-market tools (bet_research, polymarket_arbitrage/edges/edge_tracker/fill_risk/kalshi_spread) require careful reading to separate. Lengthy descriptions do disambiguate most of these, but the boundaries are close enough that an agent could easily misselect.
The vast majority of tools use snake_case, most following a verb_noun pattern (get_positions, list_subscriptions, resolve_entity, compare_entities, validate_claim, discover_tools). A handful deviate with noun-phrase or interrogative names (deep_research, entity_profile, recent_alerts, recent_changes, pipeworx_trending, whats_above), and the ask_pipeworx* family lacks a verb, but the style stays readable and predictable overall.
34 tools is heavy for a single MCP connection and overloads the agent's context; the meta-routers (ask_pipeworx/deep_research) already collapse thousands of underlying sources into a few entry points, so many of the extra gateway, memory, subscription, and branding tools add surface area rather than distinct capability. The count is well above the 15-tool sweet spot.
The gateway side covers a broad range of data via meta-tools, and memory/subscription lifecycle (remember/recall/forget, subscribe/unsubscribe/list_subscriptions/recent_alerts) is complete. However the satellite domain implied by the name 'N2yo' is thin — only get_positions, get_visual_passes, and whats_above exist, with no TLE/orbital-element lookup, satellite catalog browse, or radio-pass operations, leaving obvious gaps.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
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": "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 (\"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."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]Input 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."entity_profile3 fields changedInput schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."Input schema / properties / type / enumPrevious value: -[
- "company"
-]New value: +[
+ "company",
+ "ticker"
+]Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."resolve_entity1 field changedInput schema / properties / value / descriptionPrevious value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."NASA MCP — wraps NASA Open APIs (api.nasa.gov)
Spacenews MCP — wraps the Spaceflight News API v4 (free, no auth)
TLE MCP — satellite tracking via Two-Line Element sets (tle.ivanstanojevic.me, free, no auth)
FlightAware MCP — wraps FlightAware AeroAPI v4 (aeroapi.flightaware.com)
Add one secure layer between your agents and this server.