# SeekSat (remote · seeksat.com)

Satellite passes, live positions, visibility, cloud forecasts and radio Doppler. Free, no key.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `seeksat.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-seeksat-seeksat/api-mcp.md), [page](https://verifymcp.io/servers/com-seeksat-seeksat/api-mcp)

## Channel facts

- Endpoint: `https://seeksat.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 8205 tokens (~745/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 6 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SeekSat MCP server?

SeekSat is a hosted endpoint at https://seeksat.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-seeksat-seeksat 'https://seeksat.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-seeksat-seeksat": {
      "url": "https://seeksat.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-seeksat-seeksat": {
      "type": "http",
      "url": "https://seeksat.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-seeksat-seeksat]
url = "https://seeksat.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-seeksat-seeksat": {
      "type": "remote",
      "url": "https://seeksat.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-seeksat-seeksat --url 'https://seeksat.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-seeksat-seeksat:
    url: "https://seeksat.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-seeksat-seeksat": {
      "Transport": "http",
      "Url": "https://seeksat.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-seeksat-seeksat -t streamable-http -u 'https://seeksat.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-seeksat-seeksat": {
      "type": "http",
      "url": "https://seeksat.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 72, 0)

- [functional] Server version: 3.1.0 → 3.1.1

### 2026-11-20 (score 72, 0)

- [security regression] Tool “find_next_visible_pass” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “find_satellites_up_now” rewrote its description, which is the text the model reads
- [security] Tool “get_pass_chart” rewrote its description, which is the text the model reads
- [security] Tool “get_pass_weather” rewrote its description, which is the text the model reads
- [security] Tool “get_radio_pass” rewrote its description, which is the text the model reads
- [security] Tool “get_satellite” rewrote its description, which is the text the model reads
- [security] Tool “identify_satellite” rewrote its description, which is the text the model reads
- [security] Tool “list_satellites” rewrote its description, which is the text the model reads
- [security] Tool “search_satellites” rewrote its description, which is the text the model reads
- [security] Tool “find_best_pass” rewrote its description, which is the text the model reads
- [security] Tool “find_next_visible_pass” rewrote its description, which is the text the model reads
- [security] Tool “find_passes” rewrote its description, which is the text the model reads
- [security] Tool “get_position” rewrote its description, which is the text the model reads
- [functional improvement] Tool “find_best_pass” now declares an output schema
- [functional improvement] Tool “find_next_visible_pass” now declares an output schema
- [functional improvement] Tool “find_passes” now declares an output schema
- [functional improvement] Tool “get_satellite” now declares an output schema
- [functional improvement] Tool “find_satellites_up_now” now declares an output schema
- [functional improvement] Tool “get_pass_chart” now declares an output schema
- [functional improvement] Tool “get_pass_weather” now declares an output schema
- [functional improvement] Tool “get_position” now declares an output schema
- [functional improvement] Tool “get_radio_pass” now declares an output schema
- [functional improvement] Tool “identify_satellite” now declares an output schema
- [functional improvement] Tool “list_satellites” now declares an output schema
- [functional improvement] Tool “search_satellites” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Server version: 2.3.0 → 3.1.0
- [functional] Server version: 2.2.0 → 2.3.0
- [functional] Server version: 2.1.0 → 2.2.0
- [functional] Server version: 2.0.1 → 2.1.0
- [cosmetic] “find_passes” added an optional parameter “chart”
- [cosmetic] “find_passes” added an optional parameter “limit”
- [cosmetic] “get_position” added an optional parameter “durationMinutes”
- [cosmetic] “get_position” added an optional parameter “stepSeconds”
- [cosmetic] “find_passes” reworded the description of “windowHours”
- [cosmetic] “get_position” reworded the description of “satellite”
- [cosmetic] “find_best_pass” reworded the description of “chart”
- [cosmetic] “find_best_pass” reworded the description of “location”
- [cosmetic] “find_next_visible_pass” reworded the description of “chart”
- [cosmetic] “find_next_visible_pass” reworded the description of “location”
- [cosmetic] “find_passes” reworded the description of “location”
- [cosmetic] “find_satellites_up_now” reworded the description of “location”
- [cosmetic] “find_satellites_up_now” reworded the description of “mode”
- [cosmetic] “get_pass_chart” reworded the description of “location”
- [cosmetic] “get_pass_weather” reworded the description of “location”
- [cosmetic] “get_radio_pass” reworded the description of “location”
- [cosmetic] “identify_satellite” reworded the description of “location”
- [cosmetic] “find_passes” reworded the description of “satellite”
- [cosmetic] “get_position” reworded the description of “location”
- [cosmetic] “get_position” reworded the description of “time”
- [cosmetic] “find_best_pass” dropped the optional parameter “minElev”
- [cosmetic] “find_best_pass” dropped the optional parameter “minElevationDeg”
- [cosmetic] “find_next_visible_pass” dropped the optional parameter “minElev”
- [cosmetic] “find_next_visible_pass” dropped the optional parameter “minElevationDeg”
- [cosmetic] “find_passes” dropped the optional parameter “minElev”
- [cosmetic] “find_passes” dropped the optional parameter “minElevationDeg”
- [cosmetic] “find_satellites_up_now” dropped the optional parameter “minElev”
- [cosmetic] “find_satellites_up_now” dropped the optional parameter “minElevationDeg”
- [cosmetic] “get_pass_chart” dropped the optional parameter “minElev”
- [cosmetic] “get_pass_chart” dropped the optional parameter “minElevationDeg”
- [cosmetic] “get_pass_chart” dropped the optional parameter “passTime”
- [cosmetic] “get_position” dropped the optional parameter “passTime”
- [cosmetic] “get_radio_pass” dropped the optional parameter “minElev”
- [cosmetic] “get_radio_pass” dropped the optional parameter “minElevationDeg”
- [cosmetic] “get_radio_pass” dropped the optional parameter “passTime”
- [cosmetic] “identify_satellite” dropped the optional parameter “passTime”

### 2026-11-19 (score 72, −1)

- [security regression] Stability: 0.10 → fail
- [security regression] Tool “best_pass” was removed
- [security regression] Tool “next_visible_pass” was removed
- [security regression] Tool “whats_up_now” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “find_passes” rewrote its description, which is the text the model reads
- [security] Tool “get_pass_chart” rewrote its description, which is the text the model reads
- [security] Tool “get_pass_weather” rewrote its description, which is the text the model reads
- [security] Tool “get_position” rewrote its description, which is the text the model reads
- [security] Tool “get_radio_pass” rewrote its description, which is the text the model reads
- [security] Tool “identify_satellite” rewrote its description, which is the text the model reads
- [security] Tool “list_satellites” rewrote its description, which is the text the model reads
- [security] Tool “search_satellites” rewrote its description, which is the text the model reads
- [security] Tool “best_pass” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 7505 → 8732
- [functional] Server version: 1.0.0 → 2.0.1
- [functional] New tool “find_best_pass”
- [functional] New tool “find_next_visible_pass”
- [functional] New tool “find_satellites_up_now”
- [functional] New tool “get_satellite”
- [cosmetic] “get_pass_chart” reworded the description of “time”

### 2026-11-18 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 71)

First indexed and scored.

## MCP tools (11)

### `list_satellites` (~130 tokens)

Popular satellites

SeekSat's ten popular satellites (ISS, Tiangong, Hubble, weather satellites and a few others): always all ten, in a fixed order, with aliases, page url and orbit data freshness. Not the full list: every other tool accepts any NORAD catalog number. To find another satellite by name use search_satellites; for one satellite's facts and TLE use get_satellite. Takes no input, reads only SeekSat's own catalog and does not fail. Read-only, free, no key needed; up to 120 requests per 60 seconds per IP address.

Output parameters:

- `satellites` (array): the ten popular satellites, in a fixed order

### `find_passes` (~1280 tokens)

Find passes

Upcoming passes of one satellite or several over a location within windowHours (default 48, or 72 with limit; up to 240), in time order and not ranked: limit 1 for "when is the next pass?", no limit for the full schedule ("when does it pass this week?"). Which pass tool: find_passes lists passes in time order, from the next one (limit 1) to every pass in the window; find_best_pass ranks them by rating, for one satellite or, with none named, from a scan of many ("what can I see tonight?"); get_radio_pass gives one pass's Doppler and tuning, the next one by default. chart:true also draws the first pass listed as a sky chart (the image get_pass_chart gives) in this same result, so one call answers when and where to look. For another pass's chart give its peak time to get_pass_chart; to check clouds give it to get_pass_weather.

With a list of up to 10 satellites the result is one combined schedule: each pass also names its satellite, and satellites has one entry per satellite (one that can't be found gets an error there; the others still answer). Duplicates are listed once, and limit counts passes across the whole list. One satellite, not in a list, puts satellite, noradId and url at the top.

mode "visual" (default) keeps only the part of each pass that can be seen by eye, so rise and set can fall mid-sky and the peak is the highest point of that part; mode "radio" keeps the whole pass above minElevation. Rise and set are where it crosses minElevation, not the horizon, so a higher minElevation gives shorter, fewer passes. In visual mode the cloud forecast for the place is folded into the ratings.

rating is the one seeksat.com shows. Visual mode: how much brighter than the faintest visible star for skyType the pass gets (headroomMag), a level lower for some forecast cloud and one bar for a cloudy forecast, up to 4 days ahead; at most Fair when the brightness is estimated or the peak is below 15 degrees, at most Good below 25 degrees or when seen for under 90 seconds,…

Input parameters:

- `chart` (boolean): true to also render the first pass's polar sky chart (PNG, 800 by 897 pixels, about 120 KB) and return it in this same result. Default false.
- `lat` (number): observer latitude in decimal degrees, north positive (-90 to 90). Give it with lon, or give location instead.
- `limit` (integer): return only the first limit passes in time order, 1 to 100: 1 for the next pass. Default: every pass in the window.
- `location` (string): where the observer is, when lat and lon are not given (they win when both are): a Maidenhead grid square (EN52, EN52ve, EN52ve12), coordinates in any common form ("41.88, -87.63", "41.88N 87.63W", "4…
- `lon` (number): observer longitude in decimal degrees, east positive and west negative (-180 to 180).
- `minElevation` (number): lowest elevation that counts: a pass must climb above it, and rise and set are when it crosses it, in degrees above the horizon (0 to 90). Default 10.
- `mode` (string): "visual" (default): naked-eye passes, sunlit while the sky is dark; "radio": every line-of-sight pass, day or night.
- `satellite` (required): NORAD catalog number (as a number or a string) or a name, e.g. 25544, "25544" or "iss"; or a list of up to 10, e.g. [25544, 48274], for one schedule of all their passes.
- `skyType` (string): how dark the observer's sky is, for the visual rating as on seeksat.com: "city" (stars to magnitude 3.5), "suburban" (stars to magnitude 4.5), "rural" (stars to magnitude 5.5), "dark" (stars to magni…
- `windowHours` (number): how far ahead to look, in hours, up to 240 (10 days). Default 48, or 72 with limit.

Output parameters:

- `elementAge`: how trustworthy the prediction is, from the age of the orbital elements
- `noradId`
- `note`
- `passes` (array): the passes in time order, every one in the window or the first limit; with a list of satellites each row also has satellite and noradId
- `receptionSource`
- `resolvedLocation` (object): the place the answer is for
- `satellite`
- `satellites` (array): a list of satellites: one entry each
- `source`
- `stationary`: a geosynchronous satellite has no passes: where to point instead; null otherwise
- `summary`
- `tleAgeHours`
- `tleEpoch`
- `url`
- `weather` (object): visual mode: whether a cloud forecast was used

### `get_position` (~911 tokens)

Satellite position

Where a satellite is now, or at a given time: the point on Earth straight below it, its altitude, whether it is sunlit, and its page url. For every satellite in the sky right now use find_satellites_up_now; for when it passes over use find_passes; for its orbit and TLE use get_satellite.

With a place (lat and lon, or location) it also gives where the satellite is in that place's sky (azimuth, apparent elevation, range and whether it is above the horizon), and the place sets the time zone for local times and for reading a time with no offset; without one, times are UTC.

With durationMinutes it also gives the ground track from that time on, one point every stepSeconds (up to a day, at most 720 points of about 0.3 KB each), with the sky fields too when a place is given. lonDeg jumps between 180 and -180 at the antimeridian, so split a drawn line there.

With a list of up to 10 satellites ("where are the ISS and Tiangong now?") it gives where each is at that one moment: positions has one entry per satellite with its name, noradId, url and the fields above (one that can't be found or worked out gets an error there; the others still answer), and time, resolvedLocation and interpretedAs stay at the top. Duplicates are listed once. A ground track takes one satellite, not a list.

A time more than 30 days from the orbital elements' epoch is refused. Read-only, free, no key needed; up to 120 requests per 60 seconds per IP address. A bad input or a failure comes back as an error result (isError) whose text names the problem and what to change. A place name is looked up with OpenStreetMap (one lookup a second, cached), which can add a few seconds; lat and lon or a grid square need none. With more than one satellite it is a heavy call: one at a time per caller; another waits up to 20 seconds, then is refused as busy.

Input parameters:

- `durationMinutes` (number): how long a ground track to return, in minutes from time, up to 1440 (a day); about 93 is one ISS orbit. Omit for one position.
- `lat` (number): observer latitude in decimal degrees, north positive (-90 to 90). Give it with lon, or give location instead.
- `location` (string): where the observer is, when lat and lon are not given (they win when both are): a Maidenhead grid square (EN52, EN52ve, EN52ve12), coordinates in any common form ("41.88, -87.63", "41.88N 87.63W", "4…
- `lon` (number): observer longitude in decimal degrees, east positive and west negative (-180 to 180).
- `satellite` (required): NORAD catalog number (as a number or a string) or a name, e.g. 25544, "25544" or "iss"; or a list of up to 10, e.g. [25544, 48274], for where each is at the same moment (no ground track with a list).
- `stepSeconds` (integer): seconds between track points, 10 to 3600. Default 60, or wider when needed to keep the track to 720 points; a step you give that would make more is refused, naming the smallest that fits.
- `time` (string): when (with durationMinutes, where the track starts). Default: now. ISO 8601 with Z or an offset, e.g. "2026-11-14T21:00:00-06:00"; a time with no offset, e.g. "2026-11-14T21:00", is read in the obser…

Output parameters:

- `aboveHorizon`
- `altitudeKm`
- `azimuthDeg`
- `elementAge`: how trustworthy the prediction is, from the age of the orbital elements
- `elevationDeg`
- `interpretedAs` (object): how a time input was read
- `latDeg`
- `lonDeg`
- `name`
- `noradId`
- `positions` (array): a list of satellites: one entry each, at time
- `rangeKm`
- `resolvedLocation` (object): the place the answer is for
- `source`
- `sunlit`
- `time` (string): the moment it describes (ISO 8601 UTC; a <name>Local twin gives the observer's clock)
- `tleAgeHours`
- `tleEpoch`
- `track` (array): with durationMinutes: the ground track from time on
- `trackStepSeconds`
- `url`

### `get_pass_weather` (~560 tokens)

Pass weather

Cloud-cover forecast (Open-Meteo and MET Norway) and the chance of a clear view for a location at one time, such as a pass's peak. The forecast reaches about 7 to 16 days ahead, and viewingProbability is blended toward 0.5 the further ahead the time is, since forecasts lose skill.

It knows nothing about satellites: give the place a pass was found for and that pass's peak time from find_passes or find_best_pass. In visual mode those already fold the forecast into their ratings, so call this to show the cloud numbers or to check another time. With no forecast for that time (in the past, beyond the forecast, a time it cannot read, or a failed fetch), available is false with a reason, never a stand-in number.

Read-only, free, no key needed; up to 120 requests per 60 seconds per IP address. A bad input or a failure comes back as an error result (isError) whose text names the problem and what to change. A place name is looked up with OpenStreetMap (one lookup a second, cached), which can add a few seconds; lat and lon or a grid square need none. Forecasts are cached for 10 minutes per area (rounded to about 11 km), and a fetch gives up after 8 seconds.

Input parameters:

- `lat` (number): observer latitude in decimal degrees, north positive (-90 to 90). Give it with lon, or give location instead.
- `location` (string): where the observer is, when lat and lon are not given (they win when both are): a Maidenhead grid square (EN52, EN52ve, EN52ve12), coordinates in any common form ("41.88, -87.63", "41.88N 87.63W", "4…
- `lon` (number): observer longitude in decimal degrees, east positive and west negative (-180 to 180).
- `time` (string, required): the time to check, e.g. a pass's peak. ISO 8601 with Z or an offset, e.g. "2026-11-14T21:00:00-06:00"; a time with no offset, e.g. "2026-11-14T21:00", is read in the observer's time zone, and the res…

Output parameters:

- `available` (boolean): false when there is no forecast for that time; reason says why
- `cloudCoverPct`
- `forecastFrom`
- `forecastSource`
- `forecastUntil`
- `interpretedAs` (object): how a time input was read
- `reason`
- `resolvedLocation` (object): the place the answer is for
- `time`
- `viewingProbability`

### `get_pass_chart` (~797 tokens)

Pass sky chart

Render a polar sky chart of a satellite's pass over a location: where to look, with the moon, planets and stars in place. Returns the charted pass (the same row find_passes gives) and a one-line summary as JSON, then the image, a PNG of 800 by 897 pixels, about 120 KB. By default it charts the next pass; give time (a pass's rise or peak from find_passes or find_best_pass) to chart that pass, with the same minElevation it came from. A geostationary satellite has no passes: stationary says where to point instead, with no image. A time more than 30 days from the orbital elements' epoch is refused. Read-only, free, no key needed; up to 120 requests per 60 seconds per IP address. A bad input or a failure comes back as an error result (isError) whose text names the problem and what to change. A place name is looked up with OpenStreetMap (one lookup a second, cached), which can add a few seconds; lat and lon or a grid square need none. A heavy call: one at a time per caller; another waits up to 20 seconds, then is refused as busy.

Input parameters:

- `lat` (number): observer latitude in decimal degrees, north positive (-90 to 90). Give it with lon, or give location instead.
- `location` (string): where the observer is, when lat and lon are not given (they win when both are): a Maidenhead grid square (EN52, EN52ve, EN52ve12), coordinates in any common form ("41.88, -87.63", "41.88N 87.63W", "4…
- `lon` (number): observer longitude in decimal degrees, east positive and west negative (-180 to 180).
- `minElevation` (number): lowest elevation that counts: a pass must climb above it, and rise and set are when it crosses it, in degrees above the horizon (0 to 90). Default 10.
- `mode` (string): "visual" (default): naked-eye passes, sunlit while the sky is dark; "radio": every line-of-sight pass, day or night.
- `satellite` (required): NORAD catalog number (as a number or a string) or a name, e.g. 25544, "25544" or "iss".
- `skyType` (string): how dark the observer's sky is, for the visual rating as on seeksat.com: "city" (stars to magnitude 3.5), "suburban" (stars to magnitude 4.5), "rural" (stars to magnitude 5.5), "dark" (stars to magni…
- `time` (string): charts the pass around this time (a pass's rise or peak from find_passes or find_best_pass). Default: the next pass from now. ISO 8601 with Z or an offset, e.g. "2026-11-14T21:00:00-06:00"; a time wi…
- `windowHours` (number): how far ahead to look, in hours, up to 240 (10 days). Default 72. Only used to find the next pass when no time is given.

Output parameters:

- `elementAge`: how trustworthy the prediction is, from the age of the orbital elements
- `noradId` (number): its NORAD number
- `note`
- `pass`: the charted pass, as find_passes gives it
- `resolvedLocation` (object): the place the answer is for
- `satellite` (string): the satellite's name
- `source`
- `stationary`: a geosynchronous satellite has no passes: where to point instead; null otherwise
- `summary`
- `tleAgeHours`
- `tleEpoch`
- `url` (string): its page on seeksat.com

### `get_satellite` (~302 tokens)

Satellite details

Facts about one satellite, for "what is this satellite?" or to get its TLE: a plain-words summary, object type, owner, launch and re-entry, orbit, size, radio downlinks and its current orbital elements (TLE lines, or OMM past NORAD 99999) with their age. It takes no location or time: for where it is use get_position, for when to see it use find_passes or find_best_pass, and for a pass's Doppler and reception use get_radio_pass.

Owner, launch and type come from CelesTrak's satellite catalog and are null when it does not say; orbit is null once it has re-entered. Outside the popular list a name resolves only on an exact whole-name match, so prefer NORAD numbers from search_satellites.

Most satellites come from SeekSat's own copy of the catalog, refreshed every four hours; one missing from it is fetched from CelesTrak, which can take a few seconds and is limited per hour. Read-only, free, no key needed; up to 120 requests per 60 seconds per IP address. A bad input or a failure comes back as an error result (isError) whose text names the problem and what to change.

Input parameters:

- `satellite` (required): NORAD catalog number (as a number or a string) or a name, e.g. 25544, "25544" or "iss".

Output parameters:

- `downlinks` (array): known radio downlinks, most recently heard first
- `elementAge`: how trustworthy the prediction is, from the age of the orbital elements
- `launchDate`
- `launchSite`
- `name` (string): name
- `noradId` (number): NORAD number
- `objectType`
- `omm` (object): the elements as OMM, when there is no TLE
- `orbit`: null once it has re-entered
- `owner`
- `reentryDate`
- `sizeM`
- `source`
- `summary`
- `tle`: current elements as TLE; null past NORAD 99999, where omm carries them
- `tleAgeHours`
- `tleEpoch`
- `url` (string): its page on seeksat.com

### `search_satellites` (~390 tokens)

Search satellites

Search the full satellite catalog by name, alias or NORAD number, best match first, to turn a name like "SDO" or "NOAA 19" into a NORAD number for the other tools (they resolve a name outside the popular list only on an exact whole-name match). For the popular satellites use list_satellites; for one satellite's facts and TLE use get_satellite.

Matching order: an exact NORAD number, the whole name, the start of the name or of a word, part of the number, anywhere in the name, then near misses, so a small typo still finds it. To find satellites by downlink kind, use mode "radio" with the kind as the query (query "sstv"). No match is an empty list. Reads only SeekSat's catalog. Read-only, free, no key needed; up to 120 requests per 60 seconds per IP address. A bad input or a failure comes back as an error result (isError) whose text names the problem and what to change.

Input parameters:

- `limit` (integer): how many results to return, 1 to 20. Default 10.
- `mode` (string): "visual" (default): best name match first; "radio": satellites with known radio downlinks first among equally good matches. To list satellites with a kind of downlink, set mode "radio" and put the ki…
- `query` (string, required): a name, part of one, or a NORAD number, e.g. "sdo", "noaa 19", "25544". With mode "radio", a downlink kind as the whole query (e.g. "sstv", "aprs", "cw") lists satellites that have one.

Output parameters:

- `query` (string): the query as read
- `results` (array): best match first; empty when nothing matches

### `get_radio_pass` (~817 tokens)

Radio pass details

Radio details for one pass of a satellite over a location: its known downlink (and uplink) frequencies, the Doppler swing, when to tune to what (at 10 and 30 degrees up and at closest approach), and a table of at most 40 evenly spaced rows for pointing an antenna and tuning a radio. To choose a satellite or pass first use find_best_pass with mode radio, or find_passes; for a sky chart of the pass use get_pass_chart.

It uses the first pass that climbs above minElevation within windowHours (default 48), or with time the pass peaking nearest it (past or future, within 30 days of the elements' epoch). If there is none, window is null and message says why; the downlinks are still listed. A satellite that never sets here (geosynchronous) gets the next 24 hours instead. frequencyMHz picks the downlink; by default it is the one SatNOGS stations heard most recently, else the catalog's.

Predictions come from published elements: the transmitter's own offset is unknown, so compare the curve's shape. passUrl opens this pass on seeksat.com on the same frequency, and its Radio chart downloads the full table as CSV. Reception data is from SatNOGS Network (CC BY-SA 4.0). Read-only, free, no key needed; up to 120 requests per 60 seconds per IP address. A bad input or a failure comes back as an error result (isError) whose text names the problem and what to change. A place name is looked up with OpenStreetMap (one lookup a second, cached), which can add a few seconds; lat and lon or a grid square need none.

Input parameters:

- `frequencyMHz` (number): the downlink to compute Doppler for, in MHz. Default: the satellite's default known downlink.
- `lat` (number): observer latitude in decimal degrees, north positive (-90 to 90). Give it with lon, or give location instead.
- `location` (string): where the observer is, when lat and lon are not given (they win when both are): a Maidenhead grid square (EN52, EN52ve, EN52ve12), coordinates in any common form ("41.88, -87.63", "41.88N 87.63W", "4…
- `lon` (number): observer longitude in decimal degrees, east positive and west negative (-180 to 180).
- `minElevation` (number): lowest elevation that counts: a pass must climb above it, and rise and set are when it crosses it, in degrees above the horizon (0 to 90). Default 10.
- `satellite` (required): NORAD catalog number (as a number or a string) or a name, e.g. 25544, "25544" or "iss". e.g. "so-50" or 27607.
- `time` (string): a time near the wanted pass's peak (e.g. from find_passes), past or future. Default: the next pass. ISO 8601 with Z or an offset, e.g. "2026-11-14T21:00:00-06:00"; a time with no offset, e.g. "2026-1…
- `windowHours` (number): how far ahead to look, in hours, up to 240 (10 days). Default 48. How far past the start to look for a pass.

Output parameters:

- `downlinks` (array): known radio downlinks, most recently heard first
- `elementAge`: how trustworthy the prediction is, from the age of the orbital elements
- `frequencyMHz`
- `interpretedAs` (object): how a time input was read
- `message`
- `noradId` (number): its NORAD number
- `note`
- `passUrl`
- `receptionSource`
- `resolvedLocation` (object): the place the answer is for
- `satellite` (string): the satellite's name
- `source`
- `summary`
- `table`
- `tleAgeHours`
- `tleEpoch`
- `tuneAt`
- `uplinkMHz`
- `url` (string): its page on seeksat.com
- `window`: the pass (or day) used; null when there is none, with message

### `find_best_pass` (~1396 tokens)

Best pass

The best upcoming passes over a location, ranked by the rating seeksat.com shows ("what's the best pass tonight?"): best is the top pass and passes the top limit (default 3, up to 20), each naming its satellite. Which pass tool: find_passes lists passes in time order, from the next one (limit 1) to every pass in the window; find_best_pass ranks them by rating, for one satellite or, with none named, from a scan of many ("what can I see tonight?"); get_radio_pass gives one pass's Doppler and tuning, the next one by default. For what is up at this moment use find_satellites_up_now; to draw the winning pass set chart:true, or give a pass's peak time to get_pass_chart.

What it searches. With satellite: that satellite's passes, the top limit and not every pass. Without, a scan: visual mode (default) covers the popular satellites plus CelesTrak's visual group of the brightest objects, over 72 hours (up to 168); radio mode covers every satellite with known downlinks over 24 hours (up to 72), optionally only those with a downlink in bands or of a kind in modes. A scan leaves out satellites whose elements are more than 14 days old and counts what it skipped.

mode "visual" (default) keeps only the part of each pass that can be seen by eye, so rise and set can fall mid-sky and the peak is the highest point of that part; mode "radio" keeps the whole pass above minElevation. Rise and set are where it crosses minElevation, not the horizon, so a higher minElevation gives shorter, fewer passes.

rating is the one seeksat.com shows. Visual mode: how much brighter than the faintest visible star for skyType the pass gets (headroomMag), a level lower for some forecast cloud and one bar for a cloudy forecast, up to 4 days ahead; at most Fair when the brightness is estimated or the peak is below 15 degrees, at most Good below 25 degrees or when seen for under 90 seconds, and Excellent only above 40 degrees. Radio mode: the peak height, a bar lower for each 6 dB of extra path loss beyon…

Input parameters:

- `bands` (array): radio scan only: keep satellites with a downlink in these bands: hf (3-30 MHz), wx (137 MHz weather), 2m (144-148 MHz), 70cm (420-450 MHz), l (1-2 GHz), s (2-4 GHz), other. Default: any band.
- `chart` (boolean): true to also render the winning pass's polar sky chart (PNG, 800 by 897 pixels, about 120 KB) and return it in this same result. Default false.
- `lat` (number): observer latitude in decimal degrees, north positive (-90 to 90). Give it with lon, or give location instead.
- `limit` (integer): how many ranked passes to return, 1 to 20. Default 3.
- `location` (string): where the observer is, when lat and lon are not given (they win when both are): a Maidenhead grid square (EN52, EN52ve, EN52ve12), coordinates in any common form ("41.88, -87.63", "41.88N 87.63W", "4…
- `lon` (number): observer longitude in decimal degrees, east positive and west negative (-180 to 180).
- `minElevation` (number): lowest elevation that counts: a pass must climb above it, and rise and set are when it crosses it, in degrees above the horizon (0 to 90). Default 10.
- `mode` (string): "visual" (default): naked-eye passes, sunlit while the sky is dark; "radio": every line-of-sight pass, day or night.
- `modes` (array): radio scan only: keep satellites with a downlink of one of these kinds, matched on its mode or label, e.g. ["fm", "apt", "sstv"]. Default: any.
- `satellite`: NORAD catalog number (as a number or a string) or a name, e.g. 25544, "25544" or "iss". Omit to scan: visual mode scans the popular satellites plus CelesTrak's visual group, radio mode every satellit…
- `skyType` (string): how dark the observer's sky is, for the visual rating as on seeksat.com: "city" (stars to magnitude 3.5), "suburban" (stars to magnitude 4.5), "rural" (stars to magnitude 5.5), "dark" (stars to magni…
- `windowHours` (number): how far ahead to look, in hours, up to 240 (10 days). Default 72. With no satellite named, a visual scan stops at 168, and a radio scan defaults to 24 and stops at 72.

Output parameters:

- `best`: the top pass, or null with a note
- `checkedInDetail`
- `matchedSatellites`
- `mode` (string): visual or radio
- `note`
- `passes` (array): the top passes, best first, up to limit
- `receptionSource`
- `resolvedLocation` (object): the place the answer is for
- `satellitesScanned`
- `skipped`
- `skippedCounts`
- `skippedStaleElements`
- `weather` (object): visual mode: whether a cloud forecast was used
- `windowHours` (number): hours searched

### `find_satellites_up_now` (~577 tokens)

Satellites up now

What is in the sky over a location right now, from every satellite in the catalog (active satellites plus CelesTrak's visual group). For upcoming passes use find_best_pass or find_passes; for one satellite at any time, get_position with a place.

mode "visual" (default): sunlit satellites above minElevation while the sky is dark there (the Sun more than about 6 degrees down), brightest first; magnitudes are measured for most bright satellites (McCants' observations) and estimated for the rest. mode "radio": satellites with known downlinks above minElevation, day or night, those a hobby receiver can tune (30 MHz to 1 GHz) first, then the most recently heard by SatNOGS, then the highest.

Up to limit (default 10, up to 50). Satellites whose elements are more than 14 days from now are left out and counted. Read-only, free, no key needed; up to 120 requests per 60 seconds per IP address. A bad input or a failure comes back as an error result (isError) whose text names the problem and what to change. A place name is looked up with OpenStreetMap (one lookup a second, cached), which can add a few seconds; lat and lon or a grid square need none. A heavy call: one at a time per caller; another waits up to 20 seconds, then is refused as busy.

Input parameters:

- `lat` (number): observer latitude in decimal degrees, north positive (-90 to 90). Give it with lon, or give location instead.
- `limit` (integer): how many satellites to return, 1 to 50. Default 10.
- `location` (string): where the observer is, when lat and lon are not given (they win when both are): a Maidenhead grid square (EN52, EN52ve, EN52ve12), coordinates in any common form ("41.88, -87.63", "41.88N 87.63W", "4…
- `lon` (number): observer longitude in decimal degrees, east positive and west negative (-180 to 180).
- `minElevation` (number): lowest elevation to list, in degrees above the horizon (0 to 90). Default 10.
- `mode` (string): "visual" (default): sunlit satellites in a dark sky, brightest first; "radio": satellites with known downlinks, day or night: those a hobby receiver can tune first, then the most recently heard, then…

Output parameters:

- `aboveCount`
- `minElevationDeg` (number): lowest elevation listed
- `mode` (string): visual or radio
- `note`
- `receptionSource`
- `resolvedLocation` (object): the place the answer is for
- `satellites` (array): visual: brightest first; radio: tunable by a hobby receiver first, then recently heard, then highest
- `satellitesScanned` (number): satellites looked at
- `skippedStaleElements` (number): left out for elements more than 14 days old
- `skyDark` (boolean): true when the sky is dark enough to see satellites
- `sunAltitudeDeg` (number): the Sun's height there; negative below the horizon
- `time` (string): the moment (ISO 8601 UTC; a <name>Local twin gives the observer's clock)

### `identify_satellite` (~764 tokens)

Identify a satellite

"What was that moving light?" Given where and when a light was seen, lists the satellites that were sunlit, above the horizon and within tolerance degrees of that spot, best match first, from every satellite in the catalog. For satellites up at this moment use find_satellites_up_now; for upcoming passes use find_passes or find_best_pass.

A match must lie within tolerance of the reported spot (azimuth or direction, plus elevation). travel never adds a match; it only re-ranks them by how well each one's direction of travel agrees. Sightings by eye are often 10 to 20 degrees off, so widen tolerance before concluding nothing matched.

It needs the Sun at least about 3 degrees below the horizon: if the sky was too bright, a note says so instead of a list, and with no match a note suggests checking the time and direction or widening tolerance. Satellites whose elements are more than 14 days from the sighting are left out and counted. Read-only, free, no key needed; up to 120 requests per 60 seconds per IP address. A bad input or a failure comes back as an error result (isError) whose text names the problem and what to change. A place name is looked up with OpenStreetMap (one lookup a second, cached), which can add a few seconds; lat and lon or a grid square need none. A heavy call: one at a time per caller; another waits up to 20 seconds, then is refused as busy.

Input parameters:

- `azimuth` (number): where it was, in degrees from north (90 = east), 0 to 360. Give this or direction.
- `direction` (string): where it was, as a compass word: N, NNE, NE, ... or "north-east".
- `elevation` (number, required): how high it was, in degrees above the horizon (0 to 90, 90 = straight up). Required.
- `lat` (number): observer latitude in decimal degrees, north positive (-90 to 90). Give it with lon, or give location instead.
- `limit` (integer): how many candidates to return, 1 to 10. Default 5.
- `location` (string): where the observer is, when lat and lon are not given (they win when both are): a Maidenhead grid square (EN52, EN52ve, EN52ve12), coordinates in any common form ("41.88, -87.63", "41.88N 87.63W", "4…
- `lon` (number): observer longitude in decimal degrees, east positive and west negative (-180 to 180).
- `time` (string): time of the sighting. Default: now. ISO 8601 with Z or an offset, e.g. "2026-11-14T21:00:00-06:00"; a time with no offset, e.g. "2026-11-14T21:00", is read in the observer's time zone, and the result…
- `tolerance` (number): how far off the reported spot a match may be, in degrees, 1 to 45. Default 10.
- `travel` (string): the compass direction it was moving towards, e.g. "NE". Optional, but it sharpens the match.

Output parameters:

- `candidates` (array): best match first
- `interpretedAs` (object): how a time input was read
- `note`
- `resolvedLocation` (object): the place the answer is for
- `satellitesScanned` (number): satellites looked at
- `sighting` (object): the sighting as read
- `skippedStaleElements` (number): left out for elements more than 14 days from the sighting
- `skyDark` (boolean): true when the sky was dark enough to see a satellite
- `sunAltitudeDeg` (number): the Sun's height then
- `time` (string): the sighting time (ISO 8601 UTC; a <name>Local twin gives the observer's clock)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-seeksat-seeksat/api-mcp#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 72
- 2026-11-15: 71

## Common questions

### What is the SeekSat MCP server?

SeekSat is an MCP server listed in the public MCP registry as com.seeksat/seeksat. Satellite passes, live positions, visibility, cloud forecasts and radio Doppler. Free, no key. This page covers its hosted endpoint (https://seeksat.com/api/mcp).

### Is the SeekSat MCP server safe to use?

SeekSat scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SeekSat MCP server expose?

SeekSat exposes 11 tools: list_satellites, find_passes, get_position, get_pass_weather, get_pass_chart, and 6 more. Their descriptions and schemas cost roughly 7,924 tokens of context every time the server is loaded.

### Does the SeekSat MCP server require authentication?

No. We connected to SeekSat without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SeekSat MCP server still maintained?

SeekSat is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the SeekSat MCP server?

VerifyMCP ran 13 checks on SeekSat, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://seeksat.com/api/mcp
- Website: https://seeksat.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-seeksat-seeksat/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-seeksat-seeksat/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-seeksat-seeksat/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-seeksat-seeksat/api-mcp
