Commercial, login-gated MCP server serving FindData's own crawled data — zero upstream-provider exposure.
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":"fd-find-data-business-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.
# fd-find-data-business-mcp Commercial, login-gated MCP server that serves FindData's own crawled data to paying users. Depends on [`fd-open-data-mcp`](https://pypi.org/project/fd-open-data-mcp/) as a library and reuses its cache, dispatch, and catalog — but exposes **zero upstream-provider identity** in responses. Every value is branded `finddata`; no `source_used` / `real_source_used` key ever reaches a client. ## Tools | Tool | Purpose | |---|---| | `read` | One indicator for an entity over a list of dates (serves fresh OR stale cache; true miss dispatches in-process). | | `read_range` | Bulk series for one or more indicators over `[start, end]`. | | `list_concepts` | Browse all available FindData indicators. | | `ai_search` | Natural-language indicator + entity discovery (superset of all search tools). | | `graph_search` | Entity-relationship graph queries (bfs/dfs/neighbors/shortest_path/subgraph/ego_graph/statistics). | ## Install ```bash pip install fd-find-data-business-mcp ``` ## Run (local dev, no auth) ```bash export FD_OPEN_DATA_MCP_DATABASE_URL=postgresql://fd:***@localhost:30432/fd_open_data fd-find-data-business-mcp serve --transport http --host 0.0.0.0 --port 8310 ``` With `FDBIZ_JWKS_URI` unset, auth is disabled (smoke test / local dev). Set it in deploy to reject every request without a valid Logto-issued JWT (401 before any tool runs). ## Deploy (zihan k3s, namespace `fd-mcp`) Auth is Logto (ES384 JWT) via FastMCP's `JWTVerifier`. The canonical Logto instance runs on guangzhou-xinru: | Env var | Value | |---|---| | `FD_OPEN_DATA_MCP_DATABASE_URL` | `postgresql://fd:***@100.64.0.3:30432/fd_open_data` (mesh address of guangzhou-xinru) | | `FDBIZ_JWKS_URI` | `https://auth.finddatatech.cloud/oidc/jwks` | | `FDBIZ_ISSUER` | `https://auth.finddatatech.cloud/oidc` | | `FDBIZ_AUDIENCE` | the API resource identifier you register in Logto admin (recommended: `https://api.finddatatech.cloud/mcp`) | | `FDBIZ_ALGORITHM` | JWT signing alg (default `…
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.