public evidence dossier
com.upstash/server
Upstash’s official documentation explicitly states that it publishes an “Upstash MCP server” for managing and debugging Upstash resources and provides the official @upstash/mcp-server installation command. This independently verifies the vendor-official MCP server claim on Upstash’s own registrable domain, although the documentation describes the stdio package rather than the harvested mcp.upstash.com endpoint.
Latest visible observation: 2026-08-30T22:30:41.080Z
Identity
namespacedomain · observed 2026-08-21 23:16:25
registry statusUnknown
origin systemshosted_endpoint, registry · observed 2026-08-30T22:30:41.080Z
Distribution
repositoryUnknown · observed 2026-08-21 23:16:25
npm packageUnknown · observed 2026-08-21 23:16:25
PyPI packageUnknown
hosted endpointhttps://mcp.upstash.com/mcp · observed 2026-08-22T21:31:12.334Z
Maintenance and public findings
repository pushedUnknown
repository archivedUnknown · observed 2026-08-21 23:16:25
npm deprecatedUnknown · observed 2026-08-21 23:16:25
OSV package advisoryUnknown · observed 2026-08-21 23:16:25
Hosted liveness
last endpoint observationhealthy · observed 2026-08-22T21:31:12.334Z
reported MCP revisionunknown · observed 2026-08-25 09:12:51
Limits
This dossier reports public evidence. It is not a safety, code, permission, scope, runtime, or penetration-test verdict. Missing evidence remains unknown.