MCP server for prompt rewriting and memory recording.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"dmcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
DMCP ==== This repository contains the Python package `dmcp-server`, which installs the `dmcp-server` command. The MCP server exposes two tools: - `augument`: rewrites a prompt with relevant history and knowledge from the SQLite memory database. - `rewrite`: alias for `augument`. - `prompt`: alias for `augument`. - `record`: records a prompt/response pair and stores extracted knowledge in the SQLite memory database. Create or update the local development environment: ```sh uv sync ``` Validate the current API route config: ```sh uv run dmcp-server validate-config dmcp-api.json ``` Run the MCP server over stdio: ```sh uv run dmcp-server serve --db .dmcp/memory.sqlite3 ``` Run it over Streamable HTTP: ```sh uv run dmcp-server serve --transport http --host 127.0.0.1 --port 8000 --db .dmcp/memory.sqlite3 ``` Run the curl-based HTTP smoke test: ```sh make curl-test ``` Publish a built package to TestPyPI: ```sh cp .env.example .env # edit .env and set UV_PUBLISH_TOKEN make publish-test ``` Publish a built package to PyPI: ```sh make publish ```
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.