Developer · Remote MCP server
Dataassist IO
Query your org's data in natural language - read-only MCP access to SQL, NoSQL, files & warehouses.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.DataAssistIO/Dataassist-IO- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-06-24
- Updated
- 2026-06-24
- Publisher
- DataAssistIO (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/DataAssistIO) · how
- Website
- dataassist.io
- Repository
- github.com/DataAssistIO/dataassist-io
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.dataassist.io/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Dataassist IO
Dataassist IO is a remote MCP server: there is nothing to install. Its endpoint is https://app.dataassist.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Data Cleaner AgentClean messy CSVs: an LLM picks the steps, tested code does the work. Data untouched by the model. | Local · stdio |
| Data PrismFail-closed privacy layer that pseudonymises enterprise API data for LLM agents and MCP clients. | Local · HTTP |
| Data Profiler MCPProfiles CSV/Parquet/Excel/JSON files: schema, stats, quality flags and dtype tips for LLM agents. | Local · stdio |
| Data StudioUnified MCP server for SQL and NoSQL databases, powered by dockit and sqlkit desktop apps. | Local · stdio |
| DatabaseSQL formatting, schema visualization, migration generation. | Local · stdio |
| Database AdminDatabase admin MCP: schema inspection, query optimization for PostgreSQL and MySQL. | Local · stdio |
| Database MCPMCP server for database connectivity. Multi-DB (PostgreSQL, MySQL, SQLite), 19 tools. | Local · stdio |
| Database MCP LibsqlMCP server for libSQL/Turso, local or remote. Read-only by default, row caps, timeouts. | Local · stdio |