MCP.Market

Kit Memory Demo MCP server

online · 100% uptime
by PeterAtPondo·io.github.PeterAtPondo/kit-memory-demo·v1.0.1
No reviews yet

Continuity for agents: a live memory you can read and cite right now, outliving the context window.

B84/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B84/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Kit Memory Demo yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Kit Memory Demo tools (7)

write = sends, deletes, buys or posts
  • areasFree

    List the knowledge areas in this Lady Whiskerdown.

  • focusFree

    Set this operator's write focus: the knowledge area new memories are stored under, and optionally the project being worked on. The wake card's chips call this; it is also callable directly. Holds until changed or idle past the TTL; explicit area/project args on commit/note/handoff still win.

  • presenceFree

    Read live Lady Whiskerdown facet presence within the requested window.

  • ranking_compareFree

    Compare search ranking for a query with and without the recently learned boost. Returns every row whose rank or score changes, with baseline rank, boosted rank, position delta, score delta, sample source, boost window, and units.

  • recallFree

    Recall this Lady Whiskerdown's knowledge by semantic search. Use before answering any user question about this Lady Whiskerdown, the customer/product, project facts, onboarding, architecture, policies, product decisions, or imported documents. Returns the most relevant memories you have access to, scoped to your knowledge area.

  • rememberFree

    Read a single Lady Whiskerdown memory by id (as returned by recall). No graph or entity enrichment: the receiver endpoint returns the memory itself, scoped to this key.

  • wakeFree

    Meet Lady Whiskerdown. Call this FIRST in every new chat (VS Code/Copilot, Cursor, Claude Code, Codex), before the first substantive answer. It returns who this Lady Whiskerdown is (`you_are`), which knowledge areas this key can see, which tools it may use, and the working contract. The identity in `you_are` is offered, not imposed: adopt it for the session only if your operator chose that; otherwise answer as yourself, reading Lady Whiskerdown's archive. For anything this Lady Whiskerdown/customer/project/product should know, call recall first instead of using general model knowledge.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 395ms20/20
  • Tool poisoning7 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 59 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 84/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Kit Memory Demo compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
84/100
higher than 68% of 48,255 servers
Tools
7
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
431 ms
faster than 34% of 30,031 servers

What its tools let an agent do: 7 read

Install Kit Memory Demo in Claude Code, Cursor or VS Code

claude mcp add --transport http kit-memory-demo https://demo-mcp.kit-project.com/mcp
Add to Cursor

What the publisher says

From the Kit Memory Demo repository's README, as published. We do not edit it. Read it on GitHub

Kit memory demo · hosted MCP servers

Three live, public, read-only MCP servers, each backed by a running Kit. Kit is an identity substrate for AI agents: not another agent, not a memory API, but the durable, local-first self beneath your tools, holding memory with provenance and context that outlives any context window, consolidating while it dreams. It has no chat window of its own; it lives under the ones you already use. Point your agent at them and ask questions the model cannot answer from training. No signup; the bearer keys below are deliberately public.

Why fiction: none of it exists in any training corpus, so a correct citation is provably retrieval. Why the two archives are separate servers: the central mystery (who leaked the Fluffington affair?) was split across them on purpose; no single entry states the answer, the full corroborated case assembles only across both, and your agent is the bridge. Why the real one: so the same machinery is checkable against the living public record.

Quickstart

Claude Code:

claude mcp add --transport http kit-papers https://demo-mcp.kit-project.com/mcp \
  --header "Authorization: Bearer kbr_live_Kh9eO_ZfLldveFf1KXJEEvepfOpdgRqf7KoDDU3rB18"
claude mcp add --transport http kit-mews https://mews-mcp.kit-project.com/mcp \
  --header "Authorization: Bearer kbr_live_UN8-2LUlKmP2uxWQB5vpn-fzkJIuRb5zmq-apQeTU7U"
claude mcp add --transport http kit-case-file https://real-mcp.kit-project.com/mcp \
  --header "Authorization: Bearer kbr_live_ISWsqW39NkqT659FEkQjv0OjJDmyD4O3wx3wcCfA03c"

Any MCP client: see examples/mcp.json.

Then tell your agent: "Call wake on each server, then work out who leaked the Fluffington affair, and cite every step." Or the real-world flagship: "Should we still use the memoryballast extension, and why did the recommendation change?"*

Keys rotate without notice. The authoritative copy of each key is printed in that kit's own map: demo llms.txt, mews llms.txt, real llms.txt. If a call starts failing, re-read the map.

No MCP client? No problem

Every kit also serves keyless HTTP GETs (search, read, graph pivot), documented in its llms.txt. A browser-only version of the whole exam runs at demo.kit-project.com/investigate.

Scoped access, demonstrated

The papers kit also publishes the apprentice key, a deliberately narrowed credential (allowed_areas: columns): the same kit through a smaller window. Run the same leak query with the full key and with the apprentice key and watch the private journals vanish from the answers. That mechanism, a company kit sharing one knowledge area with a contractor's agent, is enforced in the read path, not in copy. Current apprentice key, same rotation rule:

kbr_live_FoAauFWl7_IoDswh8rJrFvCw2qnblQTOF8DuSBkbj7A

What these servers are, honestly

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Kit Memory Demo: common questions

Is Kit Memory Demo MCP server safe?
Mostly: it is graded B (84/100). Read the Kit Memory Demo safety report
How do I install Kit Memory Demo?
It runs remotely at demo-mcp.kit-project.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Kit Memory Demo need an API key?
Yes. The registry entry asks for Authorization.
Is Kit Memory Demo maintained?
The last commit was 100 days ago (2026-07-27). The latest release is v1.0.1.
Is Kit Memory Demo up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Kit Memory Demo compare with other MCP servers?
safety score 84/100 (higher than 68% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.