Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Kit Memory Demo

by PeterAtPondoversion 1.0.1i★ –iRuns in the cloud
Registry nameio.github.PeterAtPondo/kit-memory-demo

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Search & AI memory
  • You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: Authorization

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http kit-memory-demo https://demo-mcp.kit-project.com/mcp --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "kit-memory-demo": {
      "url": "https://demo-mcp.kit-project.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "kit-memory-demo": {
      "type": "http",
      "url": "https://demo-mcp.kit-project.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • Authorization required HTTP header
    Public shared read-only bearer key, deliberately published. Current value is always printed at https://demo.kit-project.com/llms.txt (it may rotate).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account PeterAtPondo, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 5654 servers in this category
  • Published to the registry more recently than 26% of the other 5654 servers in this category
  • Basic checks equal to or better than 100% of the other 5654 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Kit Memory Demo safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

serverendpointwhat it holds
Lady Whiskerdown (the Society Papers)https://demo-mcp.kit-project.com/mcpAn invented regency world seen from the ballroom. 118 memories. Half of a mystery.
The Area Cat (The Mews)https://mews-mcp.kit-project.com/mcpThe same town from below stairs. 88 memories. The other half.
The ballast case filehttps://real-mcp.kit-project.com/mcpA real five-year engineering decision (OpenTelemetry Collector's memory ballast), every entry with its GitHub source URL. 65 memories.

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 memory_ballast 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

Read-only museum copies of Kit substrates: hybrid semantic + keyword recall, typed knowledge graphs (including supersedes edges that keep replaced truth citable), source artifacts with real URLs, and honest empty results when nothing is held. They demonstrate read-time behavior; a full Kit also writes, consolidates while it sleeps, and hands off between sessions on your own machine. There is a replayable benchmark built on these exact servers: kit-memory-eval.

The build story: kit-project.com/blog, note No. 022 in particular. The product: kit-project.com, local-first, invite beta.

License

MIT (code and examples in this repo). The demo worlds themselves are licensed with the benchmark: see kit-memory-eval's DATA-LICENSE.

Ask PopNx