DataArt MCP server
Featured official server
3 tools · Last check that passed 4 Nov 2026, 12:15 UTC
DataArt's own remote MCP server gives an agent search across about 250 English-language client case studies published on dataart.com, with their full text and links back to the site, with no sign-in. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 3 tools
| Tool | Counted as |
|---|---|
get_case | Said to only read |
get_case_tags | Said to only read |
search_cases | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
21 of the last 21 checks passed
A check passes when the server lists its tools. Checked at https://mcp.dataart.com/mcp.
Recent changes
28 Oct 2026, 17:08 UTC, after a check on 28 Oct 2026, 10:46 UTC
Description rewritten on get_case.
From the scan of 4 Nov 2026, 12:43 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when DataArt's tools change.
One email when DataArt's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- DataArt says it logs each request with the caller's IP address, user agent and query text, and keeps the logs for 180 days. DataArt's MCP server page
- DataArt says the case studies are the ones it publishes about its own client work, refreshed from its website every 6 hours. DataArt's MCP server page
How to limit it
With DataArt's own settings, as its documentation describes them. Stackduke has not tested them.
- We recommend keeping names, client details and other private information out of queries, since DataArt logs query text with the caller's IP address. DataArt's MCP server page
- DataArt describes the server as public and read-only, with no authentication, so we recommend connecting it with no DataArt credentials. DataArt's MCP server page
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.