Timeline Pulse

io.github.davidmosiahPublished by GitHub account davidmosiahv0.1.1Updated Oct 24, 2026

Source-aware archive for timeline-shift folklore, Mandela Effect reports, and collider myths.

VerifiedSTDIODesktop onlyWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

A read-only local MCP server that lets an assistant search and explore a curated archive of timeline-shift folklore, Mandela Effect reports and collider myths.

What you can do
Search and read reports by text, motif, phenomenon, source type, date, stance or evidence grade, with labeled claims and safety flags per report. Browse Mandela Effect items with remembered versus on-record variants and community and mainstream notes. Explore recurring motifs and their co-occurrence graph, and curated story threads written in belief, neutral and skeptical framings. View official science milestones and community waves on one timeline, and compare belief, neutral and skeptical framings for a topic. Get corpus statistics and research prompts, plus the corpus rules and citation policy via a manifest tool.
When to use it
Useful when an assistant needs to discuss Mandela Effects, timeline-shift folklore or collider-era myths while keeping official facts, community beliefs and speculation clearly separated and sourced. Suited to cultural, editorial or educational exploration rather than factual verification of physics claims.
Requirements
Runs locally over stdio via npx from the npm package timeline-pulse; Node.js is needed. No API keys, accounts or backend. An optional loopback-only HTTP mode is configured with TIMELINE_PULSE_HOST, TIMELINE_PULSE_PORT and TIMELINE_PULSE_TRANSPORT.
Before you install
The corpus is cultural and speculative storytelling, not evidence of supernatural or physical timeline manipulation; treat its claims accordingly. All tools are read-only, so nothing is written or sent. Optional HTTP mode is described as loopback only.

Installation

In SourceWeft

  1. Open Timeline Pulse in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Timeline Pulse ◉

The machine went quiet. The stories didn't.

Timeline Pulse is an open-source MCP server and interactive atlas of timeline-shift folklore, Mandela Effect reports, collider-era myths, and symbolic reality stories — every claim labeled, every source graded.

On 2026-06-29 the LHC was switched off for Long Shutdown 3, and won't collide again until ~2030 (CERN). Communities tell stories around machines like this. This project files those stories properly: official facts on one shelf (always cited), beliefs and symbols on another (always labeled), and tools so humans and AI agents can explore both without confusing them.

Timeline Pulse treats its material as cultural, symbolic, experiential, and speculative storytelling. It does not claim that CERN, the LHC, particle physics, timelines, or Mandela Effects prove supernatural or physical timeline manipulation.

  • Site: https://timeline-pulse.vercel.app
  • Package: timeline-pulse on npm — no keys, no backend, read-only
  • Built end-to-end with Claude (Claude Code + Claude in the browser designed, documented, and implemented this repo), reviewed by a human

Use it as an MCP server

json
{  "mcpServers": {    "timeline-pulse": {      "command": "npx",      "args": ["-y", "timeline-pulse"]    }  }}

The seed corpus ships inside the package: 20 reports, 17 motifs (24 co-occurrence edges), 6 Mandela catalog items, 8 story threads, 9 timeline events with 5 officially-sourced CERN anchors.

HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

bash
npx -y timeline-pulse --http# GET  http://127.0.0.1:3000/health# POST http://127.0.0.1:3000/mcp   (sessionless)

Env: TIMELINE_PULSE_HOST, TIMELINE_PULSE_PORT, TIMELINE_PULSE_TRANSPORT=http.

MCP tools

ToolPurpose
timeline_agent_manifestThe rules of the corpus: safe language, citation policy, first calls. Call this first.
timeline_search_reportsSearch reports by text, motif, phenomenon, source type, date, stance, or evidence grade. Paginated.
timeline_get_reportOne full report with labeled claims, anchors, related reports, safety flags, and recommended phrasing.
timeline_mandela_catalogMandela Effect items: remembered vs on-record variants, community and mainstream notes side by side.
timeline_motif_mapRecurring symbols and their co-occurrence graph — the constellation, as JSON.
timeline_story_threadsCurated arcs written three ways: belief, neutral archive, skeptical.
timeline_eventsOfficial science milestones and community waves on one axis, never blended.
timeline_compare_sourcesBelief / neutral / skeptical framings for one topic, plus officially-sourced shared facts.
timeline_deepen_storyResearch prompts and follow-up angles — never fabricated sources.
timeline_statsCorpus totals by phenomenon, motif, source type, year, grade — and what still needs sources.

Every tool is read-only (readOnlyHint: true), local-first, and returns structured JSON with uncertainty made visible.

The site

https://timeline-pulse.vercel.app is the same corpus as a public instrument:

  • Archive — searchable reports with evidence-grade filters and a full-record drawer.
  • Timeline — official CERN anchors above the line, community waves and symbolic anchors below. One axis, never one claim.
  • Motifs — an interactive constellation of 17 recurring symbols (machine silence, rainbow bridge, serpent time, heart collider…).
  • Mandela Catalog — classic memory variants with the mainstream explanation always attached.
  • Story Threads — eight arcs, each readable through a belief / neutral / skeptic lens switch.
  • For agents — MCP install, raw JSON endpoints, llms.txt, and the language rules.

Plus one honest easter egg: press M and the site quietly Mandela-affects itself. See if you notice everything that changed.

Raw data endpoints (CORS-open)

/reports.json · /mandela-items.json · /motifs.json · /events.json · /story-threads.json · /sources.json · /llms.txt · /openapi.json

The site serves the exact JSON files the npm package ships — one corpus, three doors (site, MCP, raw JSON).

Evidence grades

GradeMeaning
officialPublished by the institution itself — always linked
firsthandA person reporting their own experience
reportedShared accounts: forums, polls, threads
interpretiveCommunity meaning-making on top of events
symbolicAllegory and teaching language, filed as such
speculativeUnverified conjecture, clearly flagged

Development

bash
npm installnpm test        # policy guard + build + corpus validation + site-sync check + MCP smoke testnpm run build   # compile the server to dist/npm run sync-site  # copy data/ JSON into site/ after editing the corpusnpx serve site  # run the site locally

The repo enforces its own content policy in CI: official claims must carry official URLs, speculative claims must carry safety flags, and one symbolic source family is never named — checked by hash, so the name appears nowhere, including in the check itself (scripts/check-policy.mjs).

Contributing

Reports, corrections, and motifs are welcome — see CONTRIBUTING.md and the issue templates. The fastest way to help: find official sources for anything flagged ⚑ needs source.

Documentation map

License

Code is MIT. Data: original summaries and metadata authored by the project; official facts link to their institutional sources; excerpts stay short and attributed. Details in docs/SOURCE_POLICY.md.

EST. 2026 · SEED CORPUS v0.1 · NO PHYSICS WERE HARMED ◉

Source: README.md at commit 53ccf85

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts