io.github.davidmosiah/timeline-pulse
NPM · TIMELINE-PULSE · SCANNED SEP 21
Source-aware archive for timeline-shift folklore, Mandela Effect reports, and collider myths.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 815 tokens (~81/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.davidmosiah/timeline-pulse MCP server?
io.github.davidmosiah/timeline-pulse runs locally as an npm package, launched with npx -y timeline-pulse. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · timeline-pulse
claude mcp add davidmosiah-timeline-pulse -- npx -y timeline-pulse
{
"mcpServers": {
"davidmosiah-timeline-pulse": {
"command": "npx",
"args": [
"-y",
"timeline-pulse"
]
}
}
} {
"servers": {
"davidmosiah-timeline-pulse": {
"command": "npx",
"args": [
"-y",
"timeline-pulse"
]
}
}
} codex mcp add davidmosiah-timeline-pulse -- npx -y timeline-pulse
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"davidmosiah-timeline-pulse": {
"type": "local",
"command": [
"npx",
"-y",
"timeline-pulse"
],
"enabled": true
}
}
} openclaw mcp add davidmosiah-timeline-pulse --command npx --arg -y --arg timeline-pulse
mcp_servers:
davidmosiah-timeline-pulse:
command: "npx"
args: ["-y", "timeline-pulse"] {
"McpServers": {
"davidmosiah-timeline-pulse": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"timeline-pulse"
]
}
}
} assistant mcp add davidmosiah-timeline-pulse -t stdio -c npx -a -y timeline-pulse
{
"mcpServers": {
"davidmosiah-timeline-pulse": {
"command": "npx",
"args": [
"-y",
"timeline-pulse"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/timeline-pulse@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
timeline_agent_manifest ~41
The rules of the corpus: what it is, safe language, citation policy, recommended first calls, install snippet, and raw data endpoints. Call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
timeline_compare_sources ~83
Compare belief-framed, neutral-archive, and skeptical framings for one topic, with the shared facts (officially sourced) and disputed points separated out.
| Name | Type | Req | Description |
|---|---|---|---|
| frames | array | – | subset of frames; default all three |
| topic | string | yes | e.g. 'CERN shutdown and timeline shifts', 'mandela waves', 'apophis window' |
No output schema declared.
No examples provided.
timeline_deepen_story ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| motif | string | – | – |
| report_id | string | – | – |
| thread_id | string | – | – |
No output schema declared.
No examples provided.
timeline_events ~63
Timeline events on one axis, three labeled layers: official-science (always cited), community-wave (interpretation), symbolic-anchor (reading). Layers never blend.
| Name | Type | Req | Description |
|---|---|---|---|
| date_end | string | – | – |
| date_start | string | – | – |
| layer | string | – | – |
No output schema declared.
No examples provided.
timeline_get_report ~57
Return one full report: long summary, labeled claims, source metadata, anchors, motifs, related reports, safety flags, and recommended phrasing for agents.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | report id, e.g. 'tp-001' |
No output schema declared.
No examples provided.
timeline_mandela_catalog ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| motif | string | – | motif id filter |
| query | string | – | free text over titles and variants |
| status | string | – | – |
No output schema declared.
No examples provided.
timeline_motif_map ~64
The motif constellation: recurring symbols with definitions, families, frequencies, and weighted co-occurrence edges — ready for graph rendering or motif-based filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | – | – |
| motif | string | – | focus on one motif: returns it plus its direct neighbors |
No output schema declared.
No examples provided.
timeline_search_reports ~247
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | opaque cursor from a previous call |
| date_end | string | – | ISO date — reports observed on/before |
| date_start | string | – | ISO date — reports observed on/after |
| evidence_grade | string | – | – |
| limit | integer | – | – |
| motifs | array | – | motif ids — a report must carry ALL listed motifs; call timeline_motif_map for valid ids |
| phenomenon_types | array | – | e.g. 'mandela-effect', 'cern-lore', 'timeline-shift', 'synchronicity', 'simulation-glitch', 'symbolic-alchemy', 'dream-vision' |
| query | string | – | free text matched against title, summary, motifs, phenomenon |
| source_types | array | – | e.g. 'firsthand-report', 'forum-thread', 'social-post', 'symbolic-teaching-summary', 'project-note', 'article' |
| stance | string | – | – |
No output schema declared.
No examples provided.
timeline_stats ~39
Corpus statistics: totals by phenomenon, motif, source type, evidence grade, stance, year, and language, plus catalog/thread/event counts and flagged items.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
timeline_story_threads ~73
Curated narrative arcs, each written three ways (belief / neutral / skeptical) with motif chips, timeline anchors, member reports, and research prompts.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | one thread id, e.g. 'machine-silence-calibration' |
| lens | string | – | optionally mark one frame as active |
No output schema declared.
No examples provided.
What is the io.github.davidmosiah/timeline-pulse MCP server?
io.github.davidmosiah/timeline-pulse is an MCP server listed in the public MCP registry as io.github.davidmosiah/timeline-pulse. Source-aware archive for timeline-shift folklore, Mandela Effect reports, and collider myths. This page covers its npm package (timeline-pulse).
Is the io.github.davidmosiah/timeline-pulse MCP server safe to use?
io.github.davidmosiah/timeline-pulse scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.davidmosiah/timeline-pulse MCP server expose?
io.github.davidmosiah/timeline-pulse exposes 10 tools: timeline_search_reports, timeline_get_report, timeline_mandela_catalog, timeline_motif_map, timeline_story_threads, and 5 more. Their descriptions and schemas cost roughly 815 tokens of context every time the server is loaded.
Is the io.github.davidmosiah/timeline-pulse MCP server still maintained?
io.github.davidmosiah/timeline-pulse is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.davidmosiah/timeline-pulse MCP server under?
io.github.davidmosiah/timeline-pulse declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.