Is Timeline Pulse free?

Yes, Timeline Pulse is free to use.

How do I install Timeline Pulse?

Timeline Pulse is a local plugin. Install it using npm package: timeline-pulse and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Timeline Pulse safe to use?

Timeline Pulse scored 5.2/10 (moderate risk) in MCP Marketplace's automated security scan. It has 3 high or critical findings to review. It's listed, but review the security report on this page before installing.

What AI apps work with Timeline Pulse?

Timeline Pulse uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Timeline Pulse MCP Server

by davidmosiah

Developer ToolsModerate5.2LocalNew

Free

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

About

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

Security Report

5.2

Moderate5.2Moderate Risk

Timeline Pulse is a well-structured, read-only MCP server for cultural folklore and Mandela Effect data. The codebase demonstrates solid security practices: no authentication is required (appropriate for a public, read-only archive), all tools are marked read-only, data is embedded locally, and dependencies are minimal and legitimate. The design/support.js file contains generated code with unsafe patterns (eval, Function constructor) but these are intentional for template rendering in a browser context and do not pose security risks to the MCP server itself. Minor code quality observations do not materially impact the security score. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

3 files analyzed · 6 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-davidmosiah-timeline-pulse": {
      "args": [
        "-y",
        "timeline-pulse"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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

{
  "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.

MCP tools

Tool	Purpose
`timeline_agent_manifest`	The rules of the corpus: safe language, citation policy, first calls. Call this first.
`timeline_search_reports`	Search reports by text, motif, phenomenon, source type, date, stance, or evidence grade. Paginated.
`timeline_get_report`	One full report with labeled claims, anchors, related reports, safety flags, and recommended phrasing.
`timeline_mandela_catalog`	Mandela Effect items: remembered vs on-record variants, community and mainstream notes side by side.
`timeline_motif_map`	Recurring symbols and their co-occurrence graph — the constellation, as JSON.
`timeline_story_threads`	Curated arcs written three ways: belief, neutral archive, skeptical.
`timeline_events`	Official science milestones and community waves on one axis, never blended.
`timeline_compare_sources`	Belief / neutral / skeptical framings for one topic, plus officially-sourced shared facts.
`timeline_deepen_story`	Research prompts and follow-up angles — never fabricated sources.
`timeline_stats`	Corpus 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

Grade	Meaning
`official`	Published by the institution itself — always linked
`firsthand`	A person reporting their own experience
`reported`	Shared accounts: forums, polls, threads
`interpretive`	Community meaning-making on top of events
`symbolic`	Allegory and teaching language, filed as such
`speculative`	Unverified conjecture, clearly flagged

Development

npm install
npm test        # policy guard + build + corpus validation + site-sync check + MCP smoke test
npm run build   # compile the server to dist/
npm run sync-site  # copy data/ JSON into site/ after editing the corpus
npx 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

Project brief
MCP tool spec
Data model
Site spec
Source and content policy ← the contract
Seed corpus notes
Roadmap
Design reference

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 ◉