public evidence dossier
so.voyager/mcp
Voyager’s own voyager.so Cloud page explicitly identifies an MCP server and publishes its remote server URL as https://mcp.voyager.so/mcp/machines, with setup commands for Claude Code and Codex. This independently confirms that Voyager officially operates an MCP service on its domain; the harvested base /mcp path appears to be a broader endpoint/root, while the vendor-documented usable endpoint is /mcp/machines.
Latest visible observation: 2026-11-18T12:01:41.000Z
Identity
publisher identityVendor-official for voyager (DNS-verified voyager.so)
registry titleUnknown
namespacedomain · observed 2026-11-14 23:16:23
registry statusUnknown
origin systemshosted_endpoint, registry · observed 2026-11-18T12:01:41.000Z
Distribution
repositoryUnknown · observed 2026-11-14 23:16:23
npm packageUnknown · observed 2026-11-14 23:16:23
PyPI packageUnknown
hosted endpointhttps://mcp.voyager.so/mcp · observed 2026-11-14T23:31:20.982Z
Maintenance and public findings
repository pushedUnknown
repository archivedUnknown · observed 2026-11-14 23:16:23
npm deprecatedUnknown · observed 2026-11-14 23:16:23
OSV package advisoryUnknown · observed 2026-11-14 23:16:23
Hosted liveness
last endpoint observationhealthy · observed 2026-11-14T23:31:20.982Z
reported MCP revisionunknown · observed 2026-11-18 12:01:41
Limits
This dossier reports public evidence. It is not a safety, code, permission, scope, runtime, or penetration-test verdict. Missing evidence remains unknown.