Unofficial, non-affiliated semantic voice/review harvest tools over the Mindcase API (shared core + MCP server and CLI surfaces)
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":"ca-mindcase-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.
# ca-mindcase-mcp -- semantic Mindcase harvest tools `ca-mindcase-mcp` is an **unofficial, non-affiliated** third-party client for the [Mindcase](https://mindcase.co) job API, built as one shared core with two thin surfaces: - a **stdio MCP server** for Claude Desktop, and - a **CLI** for server and batch use. > **Not affiliated with Mindcase.** This is an independent tool that talks to the > public Mindcase API. It is not produced or endorsed by Mindcase, and it is a > different package from Mindcase's own official `mindcase-mcp` server on PyPI. > The distribution name is `ca-mindcase-mcp`; the import package is `mindcase`. The tools are **semantic, not passthrough**. Every provider quirk real-world harvest testing surfaced, and every mechanical screen this project committed to, lives inside the tools, so a consuming agent cannot skip them. A raw API passthrough would push that knowledge back into prompt prose and recreate the failure class it exposed (enforcement over prose). This tool covers **voice and review harvest only**; ad intelligence is out of scope by design. ## Architecture ``` mindcase/ _client.py raw HTTP client (INSIDE-BOUNDARY, underscore-private) screens.py pure screens (contamination, reddit thread rank, youtube sorts) tools.py semantic tools = the public import API (MindcaseTools) mcp_server.py stdio MCP surface (imports the official mcp SDK) cli.py CLI surface + smoke subcommand ``` The **public import API is the tools layer** (`mindcase.tools`, re-exported from `mindcase`). A downstream orchestrator imports it and inherits the mechanical screens by construction: ```python from mindcase import MindcaseTools tools = MindcaseTools() result = tools.amazon_reviews_screened("B0XXXXXXXX") ``` The raw HTTP client lives in the underscore-private `mindcase._client` and has no MCP dependency, but it is not part of the public contract. ## Threat model: the enforcement boundary (a BOUNDED claim) The mechani…
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.