MCP server for databases, spreadsheets, structured files, and directed graphs.
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":"localdata-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.
<p align="center"> <img src="assets/logo.png" alt="LocalData MCP Server" width="250"> </p> # LocalData MCP Server [](https://opensource.org/licenses/MIT) [](https://github.com/ChrisGVE/localdata-mcp/releases) [](https://github.com/ChrisGVE/localdata-mcp/actions/workflows/ci.yml) [](https://pypi.org/project/localdata-mcp/) [](https://www.python.org/downloads/) [](https://localdata-mcp.readthedocs.io) [](https://github.com/jlowin/fastmcp) [](https://mseep.ai/app/cd737717-02f3-4388-bab7-5ec7cbe40713)   LocalData MCP gives LLM agents access to local and remote data — databases, files, graphs, and structured documents — along with a full data science toolkit for analysis and modeling. It exposes 52 MCP tools across 13 database types and 20+ file formats, with memory-bounded streaming so agents can work safely on large datasets without exceeding available RAM. [](https://mseep.ai/app/chrisgve-localdata-mcp) ## Quick Start ```bash # Install permanently uv tool install localdata-mcp # Or run directly without installing uvx localdata-mcp ``` > **First-run note:** Data science dependencies (scipy, scikit-learn, statsmodels, geopandas) total around 200 MB and…
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.