Atlas entry

mcp.dataart.com

3 capabilities over MCP. First atlas observation.

Observed · passive: no tools called, no credentials sent · sha256:9c5434…a7f2

Surfaces

5 protocols checked

ARDNot foundNo document retrieved
A2ANot found0 skills
MCPValid2025-11-25 · 3 tools · resources not advertised · prompts not advertised
OpenAPINot detected0 operations
WebMCPNot detected0 declarative form tools · experimental
Exact states and meaning
  • ARD
    absent

    Exact state: not found · No document retrieved

    The supported discovery location returned no matching document.

    Not found does not prove the service exposes no such interface elsewhere.

    Not observed / not fetched

  • A2A
    absent

    Exact state: not found · 0 skills

    The supported discovery location returned no matching document.

    Not found does not prove the service exposes no such interface elsewhere.

    Not observed / not fetched

  • MCP
    observed

    Exact state: valid · Revision 2025-11-25 · 3 tools · resources not advertised · prompts not advertised

    A usable protocol document was retrieved and validated.

    Directly observed

  • OpenAPI
    absent

    Exact state: not detected · 0 operations

    No endpoint was established from the evidence and scope that InterfaceDelta inspected.

    Not detected does not prove that no endpoint exists.

    Not observed / not fetched

  • WebMCP
    absent

    Exact state: not detected · 0 declarative form tools · experimental

    No named declarative WebMCP form tools were observed in the origin root HTML.

    Script-registered tools and other pages are not observed, so this does not mean the site has no WebMCP tools.

    Not observed / not fetched

Capabilities

3 · inventory complete

Summary of the AI readings · beta

The service lists 3 capabilities, and 3 have AI readings.

get_case_tags, search_cases and get_case are read as read-only.

Rows named: get_case_tags · search_cases · get_case

Written by code from the AI readings on this page: it groups them and says nothing they do not.

The atlas shows each capability by its plain identifier, inputs and declared sign-in. Publisher descriptions, paths, links and source evidence are not published here.

MCP tools 3

  • get_case

    inputs idOrSlug (required)

    AI Reads only 0.85

  • get_case_tags

    AI Reads only 0.80

  • search_cases

    inputs page, pageSize, query (required), tagIds and 1 more

    AI Reads only 0.90

Not observed in this Passport: A2A skills, MCP resources, MCP prompts, OpenAPI operations.

Declared and observed

3 tools declare hints; the AI readings agree with all 3 that have a reading.

A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.

Atlas history

1 observation

  • 3 capabilities · MCP 2025-11-25 · MCP endpoint validFirst observation
    Fingerprint and versions
    Fingerprint
    9c5434ac9714b3d8a9f0b49df1d7d457ac0abf6797f2ad1308fdb9f45e3ca7f2
    Passport schema
    0.5.0, passport-semantic-v4
    Consistency
    MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: not applicable · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable

Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.

About this entry

  • com.dataart/case-studies
    Listed

    Official MCP Registry · first listed 18 Sep 2026 · last listed 2 Nov 2026

Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal

Identity and snapshot
Target key
sha256:bbae624de32500eacb0aef7e647ff1659ba82cca8841a7612a18346153e0d399
Locator SHA-256
f5a680a9a222c8c2a4b24e86b4f5692407892841edaba41e83659de9b1e48adb
Snapshot generated
4 Nov 2026, 00:59 UTC

The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.