← Directory
mcp · Global
satellitetracking-mcp-server
MCP server for the N2YO API — satellite positions, passes, and visual/radio tracking.
Claim this listing
Represent satellitetracking-mcp-server? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.
What's in it
- Data offered docs-verified
- real-time satellite position by NORAD ID · TLE (two-line element) data by NORAD ID · visual pass predictions over a location · radio pass predictions over a location · satellites currently above a location · satellite search by name or category
- Coverage llm-inferred
- Any observer location supplied as lat/lng
- Formats llm-inferred
- MCP stdio
- Access docs-verified
- API key required (N2YO API, set via env N2YO_API_KEY); N2YO free tier allows 1,000 requests per hour; local install (clone, npm install, npm run build). Licence: ISC per DOCS, MIT per ENTRY metadata (conflict)
Useful for
- Use cases llm-inferred
- Predicting satellite passes over a project site to plan remote-sensing image acquisition windows · Checking which satellites are above a site for radio or GNSS link feasibility notes · Pulling TLE and orbital metadata to document satellite data sources in a study
- Audience llm-inferred
- GIS analysts · remote sensing specialists · geospatial data engineers
Limitations
- Constraints docs-verified
- Requires an N2YO API key · N2YO free tier limited to 1,000 requests per hour · Rate limiting may require waiting before further requests · Some satellites, especially older or inactive ones, may lack real-time tracking data · Requires Node.js 18+ and a local build · Licence stated differently in DOCS (ISC) and ENTRY metadata (MIT)
- Licence
- MIT
- Authentication
- API key via env: N2YO_API_KEY (auto-extracted from README)
- GitHub stars
- 4
- Last commit
- 18/09/2026
- Last successful page check
- 14/10/2026
- Page health
- healthy
- Package
- Not recorded
- Verification
- Not independently verified
Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.
Provenance & evidence
Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).
Metadata observed 15/10/2026 · research sweep: github-search