Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Thatgfsj/neuroweave-timelineWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/thatgfsj/neuroweave-timeline/nwtimeline)<a href="https://agentmods.dev/mcp/thatgfsj/neuroweave-timeline/nwtimeline"><img src="https://agentmods.dev/badge/mcp/thatgfsj/neuroweave-timeline/nwtimeline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/thatgfsj/neuroweave-timeline/nwtimeline"><img src="https://agentmods.dev/badge/mcp/thatgfsj/neuroweave-timeline/nwtimeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
nwtimeline scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "nwtimeline": { "command": "uvx", "args": [ "NWtimeline" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 8 lines scan A d5db76019d2d
nwtimeline is an MCP server published in the GitHub repository Thatgfsj/neuroweave-timeline (1 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
coding-friend-memory
CLI for coding-friend — host learning docs, setup MCP server, initialize projects. Runs locally from the coding-friend-cli npm package.
agentmem
Trusted memory for long-lived coding agents. SQLite + FTS5. Truth governance built in. Runs locally from the quilmem Python package.
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.
open-design
MCP stdio server bridging coding agents to Open Design daemon (BYOK flow with full systemPrompt fidelity). Runs locally from the open-design-mcp npm package. Needs 1 environment variable to run.
engram
Your local, private memory layer. Index your notes and files, then recall anything with citations and temporal reasoning — 100% on your machine. Runs locally from the @jnmetacode/engram npm package.