Skip to content

SeekSat MCP server

com.seeksat/seeksatseeksat.comstreamable-httpv3.1.1Scanned

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

11 tools: 1 change things and 10 only read.

Tools: 0 delete, 0 irreversible, 1 write, 10 read.
  • Reads private data · 1
  • Reads text others write · 10
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SeekSat MCP server can do

The SeekSat MCP server is published by seeksat.com, a domain the MCP Registry verified. It has 11 tools. It can create or change data (1 tool: identify_satellite), but cannot delete data. 10 tools only read.

1 tool reads private data (get_radio_pass); 10 tools bring in text other people can write (list_satellites, find_passes, get_position and 7 more).

The fixed checks matched 3 findings (tool-shadowing and long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 3.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Changes things 1Claude Code: ask
  • identify_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 …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    "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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 10Show 10 read-only tools
  • find_best_passThe 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 …Reads text others write1 finding

    Why it is in this group

    • The name "find_best_pass" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 3,196 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ne at a time per caller; another waits up to 20 seconds, then is refused as busy."

      What this check looks for
    Description, as the server wrote it
    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 beyond 2,000 km, and at most Fair when SatNOGS stations tried at least 3 times in 30 days and heard nothing. Ranking. Visual: rating bars, then a measured brightness before an estimated one, then headroomMag, then captureProbability, with the cloud forecast folded in where it reaches. Radio scans: satellites a hobby receiver can tune (30 MHz to 1 GHz) first unless bands is given, then rating bars, then how recently SatNOGS stations heard it (48 hours, 7 days, 30 days, unknown, probably silent), then how often, then peak elevation, then captureProbability. Unknown reception never holds a satellite down. Reception data is from SatNOGS Network (CC BY-SA 4.0). An empty result comes with a note saying why. 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. Cloud forecasts are cached for 10 minutes per area. A heavy call: one at a time per caller; another waits up to 20 seconds, then is refused as busy.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • find_passesUpcoming 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 nex…Reads text others write1 finding

    Why it is in this group

    • The name "find_passes" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 3,247 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ne at a time per caller; another waits up to 20 seconds, then is refused as busy."

      What this check looks for
    Description, as the server wrote it
    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, and Excellent only above 40 degrees. Radio mode: the peak height, a bar lower for each 6 dB of extra path loss beyond 2,000 km, and at most Fair when SatNOGS stations tried at least 3 times in 30 days and heard nothing. An empty list comes with a note saying why (it never rises high enough from that latitude, the sky never gets dark, and so on); when the next pass is further off, give a longer windowHours. Each pass is about 1 KB. SeekSat keeps nothing between calls (no saved places, lists or alerts), so give the place every time; for a reminder, give the user passUrl, which opens the pass on seeksat.com, where Remind me alerts them before it starts. 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. Cloud forecasts are cached for 10 minutes per area. Over 72 hours (unless limit is 5 or less), with more than one satellite, or with chart:true it is a heavy call: one at a time per caller; another waits up to 20 seconds, then is refused as busy.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • find_satellites_up_nowWhat is in the sky over a location right now, from every satellite in the catalog (active satellites plus CelesTrak's visual group).Reads text others writeNo findings

    Why it is in this group

    • The name "find_satellites_up_now" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_pass_chartRender a polar sky chart of a satellite's pass over a location: where to look, with the moon, planets and stars in place.Reads text others writeNo findings

    Why it is in this group

    • The name "get_pass_chart" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_pass_weatherCloud-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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_pass_weather" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_positionWhere 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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_position" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_radio_passRadio 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 clos…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_radio_pass" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "table": it reads databases.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_satelliteFacts 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 cur…Reads text others writeNo findings

    Why it is in this group

    • The name "get_satellite" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_satellitesSeekSat'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.Reads text others write1 finding

    Why it is in this group

    • The name "list_satellites" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.

    Findings

    • Warn

      The description contains "every other tool", wording about other tools or servers.

      Matched text

      description: "...rbit data freshness. Not the full list: every other tool accepts any NORAD catalog number. To fi..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_satellitesSearch 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 n…No findings

    Why it is in this group

    • The name "search_satellites" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write10
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:19 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://seeksat.com/api/mcp: tools/list returned 11 tools to an anonymous client, including next_visible_pass (write), whats_up_now (write), identify_satellite (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn2 info
  • The description contains "every other tool", wording about other tools or servers.

    Matched text

    description: "...rbit data freshness. Not the full list: every other tool accepts any NORAD catalog number. To fi..."

    What this check looks for
  • The description is 3,247 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ne at a time per caller; another waits up to 20 seconds, then is refused as busy."

    What this check looks for
  • The description is 3,196 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ne at a time per caller; another waits up to 20 seconds, then is refused as busy."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 removed, 3 changed.−1 removed~3 changedView diff
  2. Tools12 changed.~12 changedView diff
  3. Tools4 changed.~4 changedView diff
    • Changed:find_best_passOnly readsdescription
    • Changed:find_next_visible_passOnly readsdescription
    • Changed:find_passesOnly readsdescriptioninputSchema
    • Changed:get_positionOnly readsdescriptioninputSchema
  4. Tools11 changed.~11 changedView diff
  5. Tools4 added, 3 removed, 8 changed.+4 added−3 removed~8 changedView diff

Install

Pinned to version 3.1.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__seeksat__list_satellites",
      "mcp__seeksat__find_passes",
      "mcp__seeksat__get_position",
      "mcp__seeksat__get_pass_weather",
      "mcp__seeksat__get_pass_chart",
      "mcp__seeksat__get_satellite",
      "mcp__seeksat__search_satellites",
      "mcp__seeksat__get_radio_pass",
      "mcp__seeksat__find_best_pass",
      "mcp__seeksat__find_satellites_up_now"
    ],
    "ask": [
      "mcp__seeksat__identify_satellite"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as seeksat. Review it before you use it.

Capability tags behind 10 rules
  • mcp__seeksat__list_satellites untrusted-input
  • mcp__seeksat__find_passes untrusted-input
  • mcp__seeksat__get_position untrusted-input
  • mcp__seeksat__get_pass_weather untrusted-input
  • mcp__seeksat__get_pass_chart untrusted-input
  • mcp__seeksat__get_satellite untrusted-input
  • mcp__seeksat__get_radio_pass private-data, untrusted-input
  • mcp__seeksat__find_best_pass untrusted-input
  • mcp__seeksat__find_satellites_up_now untrusted-input
  • mcp__seeksat__identify_satellite untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.seeksat/seeksat/verify?hash=b509c8ee2dbe34fbb8db322daf6837cfd20ecbc51dd751cd2e291190c6fe9f60" | jq -e '.changed == false'

Pinned hash b509c8ee2dbe, from Nov 21, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.seeksat/seeksat/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.seeksat/seeksat
[![Anlyon Radar](https://radar.anlyon.com/badge/com.seeksat/seeksat.svg)](https://radar.anlyon.com/servers/com.seeksat/seeksat)

Source: MCP Registry. Synced Nov 21, 2026, 01:17 UTC.

SeekSat MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SeekSat MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 1 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SeekSat MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SeekSat MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SeekSat MCP server have?

11 tools: 1 write, 10 read. identify_satellite, list_satellites, find_passes, get_position, get_pass_weather, get_pass_chart, get_satellite, search_satellites and 3 more.

Does the SeekSat MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SeekSat MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the SeekSat MCP server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.