Koskamo

DataArt Case Studies MCP

A public, read-only Model Context Protocol server that lets AI assistants and agents search DataArt's client case studies by technology, industry, service, or keyword. It provides tools to search cases, retrieve full case study text, and get available tags, with data refreshed every 6 hours from dataart.com.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

DataArt Case Studies MCP logo, by DataArtVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by DataArt
MCP endpoint (Streamable HTTP)
https://mcp.dataart.com/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

3 of 3 have a description · 3 of 3 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to dataart.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search case studies by technology, industry, service, or keyword
  • Retrieve full text of a specific case study in Markdown
  • List available filters for industries, technologies, and services

Source and maintenance

Vendor evidenceRegistry 1.1.0

Protocol and capabilities

Server
com.dataart/case-studies 1.1.0
MCP protocol negotiated in check
2025-11-25
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "logging": {}
}

Tools

3 advertised

search_cases — Search DataArt case studies
Advertised by the server during the last successful anonymous check.
Advertised read-only

Search DataArt case studies by text query and/or tag IDs with pagination. The query can be keywords or a whole question: it is split into words, common words are ignored, whole words are matched in the title, description and tag names (British/American spelling and plurals are folded). Cases containing every word come first (allTermsTotal of them), then cases containing some of the words, best match first. Pass an empty query to browse all cases. Use get_case_tags to discover available tag IDs before filtering. Text and tags combine with AND. Multiple tags combine per tagMatch: "any" (default) or "all". Returns short records; use get_case with the id, slug or url of a result to get its full text.

search_cases input schema
{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "default": 1,
      "description": "Page number, 1-based. Default is 1."
    },
    "query": {
      "type": "string",
      "description": "Keywords or a question, e.g. \"telemedicine\" or \"Have you built a trading platform?\". Pass empty string to skip text filtering."
    },
    "tagIds": {
      "type": "string",
      "default": "",
      "description": "Comma-separated tag IDs to filter by (e.g. \"12,45\"). Pass empty string to skip tag filtering."
    },
    "pageSize": {
      "type": "integer",
      "default": 20,
      "description": "Items per page. Default is 20, maximum 50."
    },
    "tagMatch": {
      "type": "string",
      "default": "any",
      "description": "\"any\" (default) - case has at least one of the tags; \"all\" - case has every tag."
    }
  }
}
search_cases annotations
{
  "title": "Search DataArt case studies",
  "readOnlyHint": true,
  "openWorldHint": false
}
get_case — Get a DataArt case study
Advertised by the server during the last successful anonymous check.
Advertised read-only

Get the full content of one case study (article text, challenge, solution, conclusion). The texts are Markdown. Pass the id, slug or url returned by search_cases.

get_case input schema
{
  "type": "object",
  "required": [
    "idOrSlug"
  ],
  "properties": {
    "idOrSlug": {
      "type": "string",
      "description": "Case study id, slug or url from search_cases."
    }
  }
}
get_case annotations
{
  "title": "Get a DataArt case study",
  "readOnlyHint": true,
  "openWorldHint": false
}
get_case_tags — List DataArt case study filters
Advertised by the server during the last successful anonymous check.
Advertised read-only

Get all available tags that can be used to filter case studies. Returns a list of tags with id, parentId, and title. The list is flat: parentId is always null. Use the tag ids in the search_cases tagIds parameter.

get_case_tags input schema
{
  "type": "object",
  "properties": {}
}
get_case_tags annotations
{
  "title": "List DataArt case study filters",
  "readOnlyHint": true,
  "openWorldHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
215 ms
95th percentile latency
215 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 215 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http dataart-case-studies-mcp https://mcp.dataart.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add dataart-case-studies-mcp --url https://mcp.dataart.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable dataart-case-studies-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "dataart-case-studies-mcp": {
      "url": "https://mcp.dataart.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "dataart-case-studies-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.dataart.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start dataart-case-studies-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "dataart-case-studies-mcp": {
      "type": "http",
      "url": "https://mcp.dataart.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http dataart-case-studies-mcp https://mcp.dataart.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.dataart.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "dataart-case-studies-mcp": {
      "serverUrl": "https://mcp.dataart.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like DataArt Case Studies MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run DataArt Case Studies MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing