Atlas entry

`planvoyager.com`

5 capabilities over MCP 2026-07-28. First atlas observation.

Observed 7 Nov 2026, 03:04 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 7 Nov 2026, 03:04 UTC
Signed: 7 Nov 2026, 12:03 UTC

Protocols: MCP
Tools: 5
Declared sign-in: None declared

Effects counted AI readings, beta

Moves money: 0
Deletes or cancels records: 0
Sends messages to people: 0
Changes permissions: 0
Runs code: 0
Asks a person: 0

5 tools examined; 5 counted above a measured threshold.

Declared vs read disagreements

Declared read-only, read as writing: 0
Declared destructive, read as not writing: 0
Declared non-destructive, read as deleting: 0
Declared closed-world, read as reaching out: 0

Change since previous: First observation
Label status: Current

Atlas history

1 observation

7 Nov 2026, 03:04 UTC5 capabilities · MCP 2026-07-28 · MCP endpoint validFirst observation
Fingerprint and versions
Fingerprint
dbb84ab9a8e82ea92d8a5132dc03cd835f5ba8a6e92945dfeaa22f09af09249c
Passport schema
0.5.0, passport-semantic-v4
Consistency
MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: not applicable · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable

Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.

Declared and observed

Tool declarations are unavailable for this entry.

A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.

About this entry

io.github.gcarrenos/planvoyager
Listed
Official MCP Registry · first listed 7 Nov 2026 · last listed 7 Nov 2026

Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal

Identity and snapshot

Target key: sha256:ff0ed3be6b8a056aee8c202642a6d679d1c2bba910a1d1bc6dbc1c0302a590e7
Locator SHA-256: b2b3724a92e63d74d89f70b6401c5d5efa826e4a4f62ead55080e277cc17f3c3
Snapshot generated: 11 Nov 2026, 22:36 UTC

The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.