MCP server for 0Latency — persistent memory layer for AI agents. Give Claude, Cursor, or any MCP client long-term memory.
Free
Nothing to run from here
Timeline Pulse is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server + public atlas of timeline-shift folklore, Mandela Effect reports, and collider-era myth — every claim labeled, every source graded. A cultural archive, not a proof engine. Built while the LHC sleeps (LS3, 2026–2030).
Quickstart
# 1 — run it from where its publisher ships it
npx -y timeline-pulse
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> MCP server + public atlas of timeline-shift folklore, Mandela Effect reports, and collider-era myth — every claim labeled, every source
Publishernot claimed
DAAll 25 servers
davidmosiah25 servers
5 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Timeline Pulse as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add timeline-pulse-mcp -- npx -y timeline-pulseReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search the report archive by free text, motifs, phenomenon type, source type, stance, evidence grade, or date range. Returns brief records with grades and safety flags; use timeline_get_report for the full record.
Takes no parameters.
Example callreturns →
Return one full report: long summary, labeled claims, source metadata, anchors, motifs, related reports, safety flags, and recommended phrasing for agents.
Takes no parameters.
Example callreturns →
Browse Mandela Effect catalog items: remembered vs on-record variants, why communities link them to timeline lore, and the mainstream memory-science explanation for each.
Takes no parameters.
Example callreturns →
The motif constellation: recurring symbols with definitions, families, frequencies, and weighted co-occurrence edges — ready for graph rendering or motif-based filtering.
Takes no parameters.
Example callreturns →
Curated narrative arcs, each written three ways (belief / neutral / skeptical) with motif chips, timeline anchors, member reports, and research prompts.
Takes no parameters.
Example callreturns →
Timeline events on one axis, three labeled layers: official-science (always cited), community-wave (interpretation), symbolic-anchor (reading). Layers never blend.
Takes no parameters.
Example callreturns →
Compare belief-framed, neutral-archive, and skeptical framings for one topic, with the shared facts (officially sourced) and disputed points separated out.
Takes no parameters.
Example callreturns →
Generate research directions for a report, motif, or thread: source-search queries, related motifs, comparison questions, story-expansion prompts, and a verification checklist. Never invents sources.
Takes no parameters.
Example callreturns →
Corpus statistics: totals by phenomenon, motif, source type, evidence grade, stance, year, and language, plus catalog/thread/event counts and flagged items.
Takes no parameters.
Example callreturns →
The rules of the corpus: what it is, safe language, citation policy, recommended first calls, install snippet, and raw data endpoints. Call this first.
Takes no parameters.
Example callreturns →
Standardmost installed
$19 / month
- 16,000 calls a month, included
- 192 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Pro
$69 / month
- 160,000 calls a month, included
- 1,920 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $19 a month covers every tool at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 96 / 100
Release 0.1.3 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest0198db0b7c9a040fbe0bd4acbe7e77cd7e25df47f18cf314c483fa9556ab8e15
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| timeline_search_reports | no tags | |
| timeline_get_report | no tags | |
| timeline_mandela_catalog | untrusted-input | |
| timeline_motif_map | no tags | |
| timeline_story_threads | no tags | |
| timeline_events | no tags | |
| timeline_compare_sources | no tags | |
| timeline_deepen_story | no tags | |
| timeline_stats | no tags | |
| timeline_agent_manifest | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest0198db0b7c9a040f
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.1.3 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.1.3
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Timeline Pulse in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.