MCP connector for The Source. Self-contained REST client for api.thesrc.ai.
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":"thesrc-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.
# thesrc-mcp (source-mcp) MCP connector for The Source. Thin wrapper over `source-sdk`. ## Install ```bash pip install thesrc-mcp # PyPI distribution name # or: uvx thesrc-mcp # run without installing ``` Console scripts `source-mcp` and `thesrc-mcp` are equivalent (same entrypoint). Two tools: - `source_search` — find an entity (Drug or Gene) by partial name - `source_ask` — ask a structured question, get a full answer with authority chain ## Configuration Reads from environment: | Var | Default | Notes | |-----|---------|-------| | `SOURCE_API_URL` | `https://api.thesrc.ai` | Override to `http://localhost:8000` for local dev | | `SOURCE_API_TOKEN` | — | API key (`src_live_...`) sent as `X-API-Key`, or JWT sent as Bearer | | `SOURCE_TIMEOUT` | `30` | Per-request timeout, seconds | ## Run ```bash source-mcp ``` The Claude Code / Claude Desktop config block: ```json { "source-mcp": { "command": "source-mcp", "env": { "SOURCE_API_URL": "https://api.thesrc.ai", "SOURCE_API_TOKEN": "src_live_..." } } } ``` ## Claude Code install See [INSTALL_CLAUDE_CODE.md](INSTALL_CLAUDE_CODE.md) and the **source** plugin under `plugins/source/`.
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.