LimeliJourney MCP server — tenant-scoped tools over the key-authed PartnerApi /v1 (API key) or the Cognito AdminApi/AiApi (token).
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":"limelijourney-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.
# LimeliJourney MCP server (spec 008) A **tenant-scoped MCP server** that exposes the LimeliJourney AdminApi **and the Track B AiApi** to AI assistants (Claude Desktop, Claude Code, any MCP client) as typed tools — `list_/get_/create_/update_` per entity plus `report_*` and the AI-operator surfaces (`list_tenant_ai_fraud_cases`, `list_tenant_ai_prospects`, `list_tenant_ai_decisions`, `list_tenant_ai_autonomy`, `list_tenant_ai_sending_domains`, `list_tenant_ai_report`, …). The tool surface is **generated from [`docs/openapi.yaml`](../docs/openapi.yaml)** (spec 007), so it tracks the API automatically. Authenticate with a **revocable API key** (`llj_live_…`) over the versioned `/v1` surface (**KEY mode**, recommended for clients) or a **Cognito id token** against the AdminApi/AiApi (**TOKEN mode**, unchanged). See [Two authentication modes](#two-authentication-modes). Install in one command: `uvx limelijourney-mcp` (see [Install](#install-one-command)). **Why it's different.** Competitor affiliate-tracker MCPs (where they exist) are read-only. Ours exposes the full governed **read** surface *and* can trigger the exact same **proposals** the dashboard does — fraud-case triage, prospect invite/dismiss, sending-domain attestation, autonomy, policy — each running the server-side governance spine (autonomy lattice, audit, reversibility). Those writes stay **gated** behind `LIMELI_ALLOW_DESTRUCTIVE=1`; the reads do not. ## Two authentication modes **KEY mode (recommended)** — authenticate with a **revocable API key** (`llj_live_…`, minted in the dashboard) against the versioned, key-authed **`/v1`** surface. This is the mode to hand to a client: it is revocable, scoped, and never expires mid-session like a Cognito token. Enable it by setting `LIMELI_API_KEY`. **TOKEN mode (unchanged)** — forward a short-lived **Cognito id token** (the dashboard login token) to the AdminApi + AiApi. Used automatically when `LIMELI_API_KEY` is unset. ### How it stays safe (the boundar…
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.