Temporal Continuity MCP server
by VRhodes68·
io.github.VRhodes68/temporal-continuity·v0.1.1Local MCP adapter connecting AI clients to the hosted Temporal Continuity API.
C55/100grade C
Adoption
Not measured yet
Usage numbers are collected on the next scan
Reviews
Write oneNobody has reviewed Temporal Continuity yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Temporal Continuity tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it
no findings
- Code scan3 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancerepository not readable: repo not found3/15
- Maintainer identityno repository or website to verify2/10
Overall 55/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install Temporal Continuity in Claude Code, Cursor or VS Code
Runs npx -y temporal-continuity-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add temporal-continuity -- npx -y temporal-continuity-mcp
Temporal Continuity: common questions
- Is Temporal Continuity MCP server safe?
- With care: it is graded C, so read the findings first (55/100). Read the Temporal Continuity safety report
- How do I install Temporal Continuity?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Temporal Continuity need an API key?
- Yes. The registry entry asks for
TEMPORAL_CONTINUITY_API_KEY. - Is Temporal Continuity maintained?
- The latest release is v0.1.1.