MCP servers › io.github.dlamarre-dev › perigee
MCP server · registry snapshot 2026-11-01 · last tested 2026-11-01
io.github.dlamarre-dev/perigee
by dlamarre-dev · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗
Positions, distances, mission facts and 3D views of objects orbiting the Earth, Moon, Mars and Sun. — the publisher's description
Summary
io.github.dlamarre-dev/perigee is a remote and local MCP server listed in the official MCP registry at version 1.9.5, under the namespace of the GitHub account dlamarre-dev. Its linked repository, github.com/dlamarre-dev/Perigee, belongs to the same GitHub account. On 2026-11-01 ProtocolProbe connected to it in read-only mode and read its inventory: 19 tools, 0 resources and 0 prompts.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #1,067 of 18,055 packages by monthly downloads, tied with 1 other
- Not ranked by stars: 4 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself
Key facts
- Runs
- remote and local package
- Transport
- standard input/output, streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Package
- npm · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Tools
- 19
- Last tested
- 2026-11-01
Tool list size
9,512 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (19 tools). Counted with Anthropic's token counter on 2026-11-01, from the tool list we read on 2026-11-01. Median across 25,471 counted servers: 2,877 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-01 (perigee-mcp.perigeeinfo.workers.dev), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.9.5).
Worth knowing before you connect it
- Its package is signed and carries a build record naming its source.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-01
- Mode
- read-only (no tool calls)
- Latest version
- 1.9.5, published 2026-10-31 (registry, as of the 2026-11-01 snapshot)
- First listed version
- 2026-10-30 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 4 versions listed, 2026-10-30 to 2026-10-31; 4 in the 90 days before the 2026-11-01 snapshot.(versions still listed in the registry only)
Most recent 4 versions
1.9.5· 2026-10-311.9.4· 2026-10-311.9.3· 2026-10-311.9.2· 2026-10-30
- Registry data
- snapshot 2026-11-01
- Package and repository
- checked 2026-11-01
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 1.9.3 (published 2026-10-31) → 1.9.5 (published 2026-10-31), between the registry lists of 2026-10-31 and 2026-11-01.
The publisher published no GitHub release note for version 1.9.5: the repository has no release tagged for it and named for this package (the repository holds several packages).
Source: the official MCP Registry list on 2026-10-31 and on 2026-11-01; release notes from the GitHub Releases API, checked 2026-11-01.
What it is
What does this server offer?
Observed inventoryNone of its 19 tools are described as changing anything. For 19 the reading was uncertain, so no mark is shown.
- perigee_find
“Looks up objects by name or identifier (English or French, accents optional): planets, moons, missions beyond Earth orbit, featured science satellites, any active Earth satellite (by name, NORAD or C…”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
querystringrequired“Name or identifier to look up, e.g.”limitinteger“Maximum number of results (default 10).”
- perigee_object
“Facts about an object: name, agency, country, launch date, status, mission goals and notes, identifiers (NORAD, COSPAR, Horizons), official website, sources and verification date, a catalogue image w…”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
idstringrequired“Object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a dwarf p…”langstring“Language of names and texts (default en).”include_imageboolean“Also return the catalogue image itself, not only its link and credit (default false).”
- perigee_state
“Position (km, ICRF/J2000 equatorial axes) and velocity (km/s) of an object at a date, relative to a centre (default: the body it orbits or stands on), with distance, altitude above the centre, speed,…”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
idstringrequired“Object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a dwarf p…”datestring“ISO 8601 UTC instant, e.g.”centrestring“Reference object id, e.g.”
- perigee_orbit
“Orbit of an object: perigee and apogee altitudes (periapsis/apoapsis), period, inclination, eccentricity, semi-major axis.”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
idstringrequired“Object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a dwarf p…”datestring“ISO 8601 UTC instant, e.g.”centrestring“Body the orbit is around, e.g.”
- perigee_passes
“When an Earth satellite (ISS = 25544, Tiangong = 48274, Hubble = 20580, or any NORAD number) passes over a place: rise, highest point and set times with direction (azimuth, compass point) and elevati…”
Publisher declares: read-only yes · open-world yes
9 inputs, 3 required
idstringrequired“Object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a dwarf p…”latitudenumberrequired“Observer latitude, degrees (north positive).”longitudenumberrequired“Observer longitude, degrees (east positive).”height_mnumber“Observer height above sea level, m.”startstring“ISO 8601 UTC instant, e.g.”daysnumber“Search length in days (default 3).”min_elevationnumber“Lowest culmination kept and lowest elevation counted as visible, degrees (default 10).”time_zonestring“IANA time zone for local times, e.g.”langstring“Language of names and texts (default en).”
- perigee_sky
“What is in the sky from a place at a date (default: now): day, twilight or night; the Sun with its next rise, set and twilights; the Moon with its phase, illuminated share, rise and set; each planet …”
Publisher declares: read-only yes · open-world no
6 inputs, 2 required
latitudenumberrequired“Observer latitude, degrees (north positive).”longitudenumberrequired“Observer longitude, degrees (east positive).”height_mnumber“Observer height above sea level, m.”datestring“ISO 8601 UTC instant, e.g.”time_zonestring“IANA time zone for local times, e.g.”langstring“Language of names and texts (default en).”
- perigee_events
“Events over a period (default: the next 30 days, at most 31): Moon phases (super and micro full Moons), lunar perigee and apogee, lunar and solar eclipses (with a place: how they look from there), eq…”
Publisher declares: read-only yes · open-world no
7 inputs
startstring“ISO 8601 UTC instant, e.g.”daysnumber“Length of the period in days (default 30).”kindsarray“Kinds of events to include (default: all).”latitudenumber“Observer latitude, degrees (north positive).”longitudenumber“Observer longitude, degrees (east positive).”time_zonestring“IANA time zone for local times, e.g.”langstring“Language of names and texts (default en).”
- perigee_tonight
“What there is to see tonight from a place (the coming night, or the current one): the night's start and end, the Moon (phase, illuminated share, rise and set), the planets visible to the naked eye, t…”
Publisher declares: read-only yes · open-world yes
6 inputs, 2 required
latitudenumberrequired“Observer latitude, degrees (north positive).”longitudenumberrequired“Observer longitude, degrees (east positive).”height_mnumber“Observer height above sea level, m.”datestring“ISO 8601 UTC instant, e.g.”time_zonestring“IANA time zone for local times, e.g.”langstring“Language of names and texts (default en).”
- perigee_sky_conjunctions
“Apparent close pairings seen from a place over a period (default 7 days, at most 7): the Moon and the planets with each other and with the bright stars near the ecliptic (Regulus, Spica, Antares, Ald…”
Publisher declares: read-only yes · open-world yes
9 inputs, 2 required
latitudenumberrequired“Observer latitude, degrees (north positive).”longitudenumberrequired“Observer longitude, degrees (east positive).”height_mnumber“Observer height above sea level, m.”startstring“ISO 8601 UTC instant, e.g.”daysnumber“Length of the period in days (default 7; 1 with a satellite).”max_separationnumber“Widest separation kept, degrees (default 5).”satellitestring“An Earth satellite (NORAD number) to check against the Moon, planets and stars.”time_zonestring“IANA time zone for local times, e.g.”langstring“Language of names and texts (default en).”
- perigee_shadow
“Whether an object is in sunlight, in the penumbra or in the umbra of the body it orbits (Earth satellites: the Earth's shadow; lunar and Martian orbiters: the Moon's or Mars'), and when it next enter…”
Publisher declares: read-only yes · open-world yes
6 inputs, 1 required
idstringrequired“Object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a dwarf p…”datestring“ISO 8601 UTC instant, e.g.”hoursnumber“Length of the search in hours (default: two orbits).”centrestring“Body casting the shadow (default: the one the object orbits).”time_zonestring“IANA time zone for local times, e.g.”langstring“Language of names and texts (default en).”
- perigee_ground_track
“The path on the ground below an Earth satellite over one or two orbits: a list of points (time, latitude, longitude, height) and a GeoJSON MultiLineString split at the antimeridian, ready for a map.”
Publisher declares: read-only yes · open-world yes
5 inputs, 1 required
idstringrequired“Object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a dwarf p…”startstring“ISO 8601 UTC instant, e.g.”orbitsnumber“Number of orbits (default 1).”pointsinteger“Number of points (default 180 per orbit).”langstring“Language of names and texts (default en).”
- perigee_close_approach
“The closest distance between two objects in space over a period (default 1 day, at most 1): when, how close (timed to a fraction of a second) and, for two Earth satellites, how fast they pass each ot…”
Publisher declares: read-only yes · open-world yes
6 inputs, 2 required
fromstringrequired“First object id.”tostringrequired“Second object id.”startstring“ISO 8601 UTC instant, e.g.”daysnumber“Length of the search in days (default 1).”time_zonestring“IANA time zone for local times, e.g.”langstring“Language of names and texts (default en).”
Show 7 more tools
- perigee_stats
“Counts of the active satellites: total, by owner (country or organisation, e.g.”
Publisher declares: read-only yes · open-world yes
5 inputs
ownerstring“Narrow the owner list to this SATCAT owner code or name, e.g.”operatorstring“Narrow the operator list to this operator, e.g.”groupstring“Narrow the group list to this CelesTrak group, e.g.”limitinteger“Largest entries listed per category (default 25).”langstring“Language of names and texts (default en).”
- perigee_distance
“Centre-to-centre distance between two objects at a date (km and astronomical units) and the light travel time, with the provenance of both positions.”
Publisher declares: read-only yes · open-world yes
3 inputs, 2 required
fromstringrequired“First object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a d…”tostringrequired“Second object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a …”datestring“ISO 8601 UTC instant, e.g.”
- perigee_distance_series
“Distances between two objects sampled evenly over a period (for a table or a chart), with the closest and farthest samples.”
Publisher declares: read-only yes · open-world yes
5 inputs, 4 required
fromstringrequired“First object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a d…”tostringrequired“Second object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a …”startstringrequired“ISO 8601 UTC start.”endstringrequired“ISO 8601 UTC end.”stepsinteger“Number of intervals (default 50, at most 100).”
- perigee_view
“Link to Perigee showing an object (optionally at a date, paused or accelerated, followed), and an iframe snippet for a lesson page: the live 3D view without bars or panels.”
Publisher declares: read-only yes · open-world no
9 inputs, 1 required
idstringrequired“Object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a dwarf p…”datestring“ISO 8601 UTC instant, e.g.”langstring“Language of names and texts (default en).”ratenumber“Time multiplier: 1 real time, 0 paused.”followboolean“Follow the object (default true).”panelboolean“Keep the information panel in the embed.”time_barboolean“Keep the time bar in the embed.”star_mapboolean“Stars only (star:<id>): open the star's 3D map with the Sun, alone in the embed.”comparestring“With star_map: another star (star:<id>) drawn with its distance to compare.”
- perigee_describe_view
“Turns a Perigee link or embed URL (from perigee_view or a shared link) into words: a one-sentence alternative text for the image or iframe, and a description for lesson notes (which view, the selecte…”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
urlstringrequired“A Perigee URL, e.g.”langstring“Language of names and texts (default en).”time_zonestring“IANA time zone for local times, e.g.”
- perigee_define
“Student-level definitions (secondary school) of the terms shown in Perigee: NORAD number, COSPAR id, apogee and perigee, inclination, orbital period, element epoch, ephemeris window, phase… Without a…”
Publisher declares: read-only yes · open-world no
2 inputs
termstring“Term to define, e.g.”langstring“Language of names and texts (default en).”
- perigee_about
“What every answer rests on: data sources and when they were fetched, the models and their typical accuracy, catalogue sizes, frame, attribution and the educational-use disclaimer.”
Publisher declares: read-only yes · open-world yes
Takes no inputs.
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-01.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 100% of 92
- Tools with a description
- 100% of 19
- Typical description length
- 337 characters
The tool set
Counted from the listing
- Tools
- 19
- Size of the list
- about 6,029 tokens for an agent to load (characters ÷ 4)
- Naming
- 19 of 19 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 19 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the npm package perigee-mcp
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"perigee": {
"command": "npx",
"args": [
"-y",
"perigee-mcp@1.9.5"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"perigee": {
"command": "npx",
"args": [
"-y",
"perigee-mcp@1.9.5"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"perigee": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"perigee-mcp@1.9.5"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"perigee","type":"stdio","command":"npx","args":["-y","perigee-mcp@1.9.5"]}'Claude Code
claude mcp add --transport stdio perigee -- npx -y perigee-mcp@1.9.5
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"perigee": {
"command": "npx",
"args": [
"-y",
"perigee-mcp@1.9.5"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"perigee": {
"command": "npx",
"args": [
"-y",
"perigee-mcp@1.9.5"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.perigee] command = "npx" args = ["-y", "perigee-mcp@1.9.5"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"perigee": {
"command": "npx",
"args": [
"-y",
"perigee-mcp@1.9.5"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y perigee-mcp@1.9.5
- Optional settings the entry also lists (left out above): PERIGEE_SITE, PERIGEE_MCP_CACHE.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-01 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://perigee-mcp.perigeeinfo.workers.dev/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"perigee": {
"url": "https://perigee-mcp.perigeeinfo.workers.dev/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"perigee": {
"type": "http",
"url": "https://perigee-mcp.perigeeinfo.workers.dev/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"perigee","type":"http","url":"https://perigee-mcp.perigeeinfo.workers.dev/mcp"}'Claude Code
claude mcp add --transport http perigee https://perigee-mcp.perigeeinfo.workers.dev/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"perigee": {
"type": "streamableHttp",
"url": "https://perigee-mcp.perigeeinfo.workers.dev/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"perigee": {
"httpUrl": "https://perigee-mcp.perigeeinfo.workers.dev/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.perigee] url = "https://perigee-mcp.perigeeinfo.workers.dev/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"perigee": {
"url": "https://perigee-mcp.perigeeinfo.workers.dev/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://perigee-mcp.perigeeinfo.workers.dev/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 1.9.5
- Latest stable
- 1.9.5
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-01. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-01 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-f1iPBURQcam/iaUEl…
- Signature
- signed and attested
- License
- MIT
Source: the package registry · 2026-11-01.
Usage
- Downloads
- 2,309 in the last month
Source: api.npmjs.org · 2026-11-01.
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint perigee-mcp.perigeeinfo.workers.dev/mcp | Session opened | matches | our test · 2026-11-01 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-01 |
| Version 1.9.5 on npm | Exists and can be installed | matches | npm · 2026-11-01 |
| Repository github.com/dlamarre-dev/Perigee | Opens publicly | matches | api.github.com · 2026-11-01 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.dlamarre-dev
- GitHub owner
- a personal account (dlamarre-dev)
- Build record
- signed and attested
- Repository
- github.com/dlamarre-dev/Perigee
- Stars
- 4
- Repository age
- 31–90 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-01; security policy read from GitHub · 2026-11-01.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Tool list changes
Our reads compared · no tool calledHosted endpoint perigee-mcp.perigeeinfo.workers.dev/mcp
1 of 2 comparisons between consecutive reads showed a change (3 reads, 2026-10-30 to 2026-11-01; versions 1.9.2 to 1.9.5).
Last change seen between our reads on 2026-10-31 (version 1.9.3) and 2026-11-01 (version 1.9.5).
Changed (12):
perigee_define: input schemaperigee_distance: input schemaperigee_distance_series: input schemaperigee_find: input schemaperigee_ground_track: input schemaperigee_object: input schemaperigee_orbit: input schemaperigee_passes: input schemaperigee_shadow: input schemaperigee_state: input schemaperigee_stats: input schemaperigee_view: input schemaCompared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-01 is not known yet. No tool was called. How it is compared
Choosing
Record checks
Public records · not a safety rating8 of 9 record checks met
- #1,067 of 18,055 packages by monthly downloads, tied with 1 other
- Not ranked by stars: 4 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-01 (security policy 2026-11-01). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.dlamarre-dev/perigee
Answered from the data aboveWho publishes io.github.dlamarre-dev/perigee?
The registry ties the namespace io.github.dlamarre-dev to the GitHub account dlamarre-dev; only its owner can publish under it. Its linked repository, github.com/dlamarre-dev/Perigee, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.dlamarre-dev/perigee safe to install?
We do not rate servers as safe or unsafe. 8 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does io.github.dlamarre-dev/perigee need an API key or sign-in?
It opened a session without any credential on 2026-11-01. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.github.dlamarre-dev/perigee been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.
Does io.github.dlamarre-dev/perigee publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
Yes. The registry lists 1.9.5, the latest stable release on npm.
Where is the source code of io.github.dlamarre-dev/perigee?
In github.com/dlamarre-dev/Perigee, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-11-01, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 482 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 19 tools, 0 resources, 0 prompts.
- 1,219 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.dlamarre-dev/perigee: MCP server record.” Data checked 2026-11-01. https://protocolprobe.com/mcp/servers/io.github.dlamarre-dev/perigee
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.dlamarre-dev/perigee)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology