Authenticated MCP access to local MoniKa chat databases and a multi-instance router
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":"monika-mcp","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.
# MoniKa MCP This directory provides two authenticated Streamable HTTP MCP services: - `monika-mcp`: lists chatroom databases, reports session/account and DEK availability, reads bounded decrypted message rows, and checks for messages after a Unix timestamp. - `monika-mcp-router`: concurrently probes several instances and routes an allow-listed read tool to a named instance. Raw DEKs never appear in MCP responses. Both services require the `monika:read` bearer-token scope. They bind to loopback by default; use a TLS reverse proxy for remote access. Plain HTTP instance URLs are rejected except on loopback. `instance_status` discloses the 40-hex Kakao profile-directory identifier as `profile_id` and the distinct 32-hex `hashed_talk_user_id` when the process scan confirms a signed-in session. Cached identity survives logout, so `account` is deliberately `null` for signed-out, interstitial, candidate, and unknown states. The response includes `observed_at` so callers can judge freshness. ## Install Install the released package from PyPI: ```powershell uv tool install monika-mcp monika-mcp ``` Run the router instead with `monika-mcp-router`. To work from a source checkout: ```powershell uv sync --all-packages uv run --package monika-mcp monika-mcp ``` Create an opaque token, then configure its SHA-256 digest (not the token itself): ```powershell $token = python -c "import secrets; print(secrets.token_urlsafe(32))" $digest = python -c "import hashlib,sys; print(hashlib.sha256(sys.argv[1].encode()).hexdigest())" $token $env:MONIKA_MCP_TOKENS_JSON = '{"' + $digest + '":{"client_id":"local-client","scopes":["monika:read"],"expires_at":1893456000}}' ``` For an instance, set `MONIKA_USER_DIR` and `MONIKA_MCP_ISSUER_URL`; optionally set `MONIKA_CACHE_DB` and `MONIKA_MCP_PUBLIC_URL`, then run `monika-mcp`. The issuer is mandatory so a deployment cannot accidentally advertise a fake authorization server. For the router, copy `instances.example.json` outside the repo…
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.