Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Artsdata

REMOTE · MCP.ARTSDATA.CA

Search Artsdata for authoritative data on Canadian events, artists, organizations, and places.

Available components

0 this week 81 Trust /100

Last scanned (18 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1859 tokens (~309/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 23 Oct 26 0
    • Tool “search_events” rewrote its description, which is the text the model reads security
  • 22 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_entity” rewrote its description, which is the text the model reads security
    • Tool “search_entities” rewrote its description, which is the text the model reads security
    • Tool “search_events” rewrote its description, which is the text the model reads security
    • Tool “sparql_query” rewrote its description, which is the text the model reads security
    • Schema quality: 235 → 308 ▼ functional
  • 8 Oct 26 0
    • “search_events” reworded the description of “artists” cosmetic
    • “search_events” reworded the description of “organizations” cosmetic
    • “search_events” reworded the description of “places” cosmetic

    3 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 29 Sept 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 19 Sept 26 0
    • Tool “search_events” rewrote its description, which is the text the model reads security
    • “search_events” reworded the description of “places” cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://mcp.artsdata.ca/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.artsdata.ca CN=YR1,O=Let's Encrypt,C=US 6 Oct 2026 4 Jan 2027 RSA 2048 SHA256-RSA 65f19e12cfb6ac90d831e2f805f060e3546
SANs: mcp.artsdata.ca
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.artsdata.ca. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ca. present 26384 13 Verified
artsdata.ca. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.artsdata.ca/mcp Verified 200
http (plaintext) http://mcp.artsdata.ca/mcp HTTPS enforced 301 https://mcp.artsdata.ca/mcp
MCP tools · 5 exposed · ~1,472 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_entity ~101

Tool to get entities details from Artsdata Knowledge Graph by entity URI. Entity URIs end in the Artsdata ID (K\d+-\d+, e.g. K12-345); cite it with the entity name. The result's `sources` lists the datasets the entity was built from: name them when you answer about the entity, linking `url` when present, else by `name`.

NameTypeReqDescription
uristringyesThe Artsdata entity URI.
NameTypeReqDescription
additional_propertiesarray––
alternate_namesarray––
descriptionarray––
disambiguatingDescriptionarray––
end_date––End date or end date-time of an event (ISO 8601).
event_attendance_modestring–Attendance mode of the event, it can one from the enumeration members of https://schema.org/EventAttendanceModeEnumeration
event_statusstring–Status of the event, it can one from the enumeration members of https://schema.org/EventStatusType
has_event_type_conceptarray–Concept URIs from the Artsdata Event Types vocabulary (adr:ArtsdataEventTypes)
idstringyesUnique identifier of the entity.
locationarray–List of locations, each with its Artsdata id, URI and name.
main_entity_of_pagestring–URI of the main entity page.
namearrayyes–
organizerarray–List of organizers, each with its Artsdata id, URI and name.
performerarray–List of performers, each with its Artsdata id, URI and name.
same_asarray––
sourcesarray–Datasets the entity was built from. A dataset with a maintainer is given by the maintainer's website (url), otherwise by name.
start_date––Start date or start date-time of an event (ISO 8601).
typesarrayyes–
uristringyesURI representing the entity.

No examples provided.

get_schema ~129

Returns the data model of the Artsdata Knowledge Graph: its entity classes (Event, Place, Organization, Person, LivePerformanceWork...), the properties of each with required/optional, cardinality, value types, linked classes and allowed values, the controlled vocabularies, the SPARQL prefixes, and conventions for querying. Derived from the Artsdata Ontology and the Artsdata CORE graph SHACL shapes. Call this before writing a SPARQL query to run with sparql_query against https://query.artsdata.ca/query, since Artsdata's model is not general knowledge. Takes no input.

Input schema present but exposes no named parameters.

NameTypeReqDescription
aboutobjectyes–
classesarrayyes–
conventionsarrayyesHow to read the digest and write SPARQL against the graph.
prefixesobjectyesPrefix name -> namespace IRI.
vocabulariesarrayyes–

No examples provided.

search_entities ~248

Tool to search for entities in the Artsdata knowledge graph by name, with optional filters on entity type and on the controlled vocabulary (skos:ConceptScheme) a concept belongs to. Each result has a markdown-link `label` like '[Name (K12-345)](https://kg.artsdata.ca/resource/K12-345)': use it verbatim when mentioning the entity.

NameTypeReqDescription
in_schemearray–Optional list of Artsdata controlled vocabulary (skos:ConceptScheme) URIs (e.g., ['http://kg.artsdata.ca/resource/ArtsdataEventTypes']). Paired with types: ['http://www.w3.org/2004/02/skos/core#Conce…
languagestring–Language code, restricted to 'en' or 'fr'.
limitinteger–Number of results to return.
querystringyesNon-empty mandatory search query.
typesarray–Optional list of type filters; can be empty.
NameTypeReqDescription
resultsarrayyes–

No examples provided.

search_events ~683

Tool to search for events in the Artsdata knowledge graph by place, artist, organization, has_event_type_concept and language. Places, artists and organizations are Artsdata entity URIs; the has_event_type_concept filter takes concept URIs from the Artsdata Event Types vocabulary (adr:ArtsdataEventTypes), not schema.org classes. Resolve any name or label to its URI with search_entities first. Places must be venues; for events in a city or region, use sparql_query (see the places parameter). At least one filter is required. Entity URIs end in the Artsdata ID (K\d+-\d+, e.g. K12-345); cite it with the entity name.

NameTypeReqDescription
artistsarray–Optional list of Artsdata artist URIs (e.g., ["http://kg.artsdata.ca/resource/K2-6574"]). If you only have a name, use search_entities (types: ['http://kg.artsdata.ca/ontology/Person']) to find its U…
has_event_type_conceptarray–Optional list of concept URIs from the Artsdata Event Types vocabulary (http://kg.artsdata.ca/resource/ArtsdataEventTypes). Must be valid concept URIs (e.g., http://kg.artsdata.ca/resource/ClassicalM…
languagestring–Language for the labels in the response (e.g. 'en', 'fr'); default is 'en'. This selects the output language only — it does NOT filter events by the language they are performed in.
limitinteger–Number of results to return.
organizationsarray–Optional list of Artsdata organization URIs (e.g., ["http://kg.artsdata.ca/resource/K5-72"]). If you only have a name, use search_entities (types: ['http://kg.artsdata.ca/ontology/Organization']) to…
placesarray–Optional list of Artsdata VENUE URIs (e.g., ["http://kg.artsdata.ca/resource/K11-2"]) for a theatre, hall, auditorium, room or stage. Only venue URIs work: a city, region or country (e.g. 'Toronto',…
startDateFromstring–Optional lower bound filter. Includes events starting on or after this date/time. ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:mm:ssZ).
startDateTostring–Optional upper bound filter. Includes events starting on or before this date/time. ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:mm:ssZ).
NameTypeReqDescription
resultsarrayyes–

No examples provided.

sparql_query ~311

Runs a read-only SPARQL 1.1 SELECT or ASK query against the Artsdata Knowledge Graph (https://query.artsdata.ca/query) and returns the result as SPARQL 1.1 Query Results JSON, exactly as the endpoint returns it: head.vars and results.bindings for SELECT, boolean for ASK. Call get_schema first and build the query from the classes, properties, prefixes and conventions it returns, since Artsdata's model is not general knowledge. Declare every PREFIX you use and always add a LIMIT: at most 1000 rows are returned (the rest is cut and truncated is true; page with OFFSET), and a query gets 25 seconds. If the endpoint rejects the query, its error message is returned so you can fix the query and retry. For the details of an entity URI in the results use get_entity; to find an entity's URI from its name use search_entities. Always SELECT the entity URI next to its label so its Artsdata ID can be cited. Entity URIs end in the Artsdata ID (K\d+-\d+, e.g. K12-345); cite it with the entity name. To find who claims a property value, see the sources guidance in the get_schema conventions.

NameTypeReqDescription
querystringyesA complete SPARQL 1.1 SELECT or ASK query, with a PREFIX declaration for every prefix it uses. Build it from the classes, properties and prefixes returned by get_schema, and add a LIMIT.
NameTypeReqDescription
booleanboolean–The answer to an ASK query.
headobjectyes–
resultsobject––
truncatedboolean–Present and true when the endpoint returned more rows than the server's row cap and only the first rows are included. Add or lower the LIMIT, or page with OFFSET.

No examples provided.

Install

How do I install the Artsdata MCP server?

Artsdata is a hosted endpoint at https://mcp.artsdata.ca/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.artsdata.ca

# add to Claude Code
claude mcp add --transport http ca-artsdata-mcp 'https://mcp.artsdata.ca/mcp'
Common questions

What is the Artsdata MCP server?

Artsdata is an MCP server listed in the public MCP registry as ca.artsdata/mcp. Search Artsdata for authoritative data on Canadian events, artists, organizations, and places. This page covers its hosted endpoint (https://mcp.artsdata.ca/mcp).

Is the Artsdata MCP server safe to use?

Artsdata scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Artsdata MCP server expose?

Artsdata exposes 5 tools: search_entities, get_entity, search_events, get_schema, sparql_query. Their descriptions and schemas cost roughly 1,472 tokens of context every time the server is loaded.

Does the Artsdata MCP server require authentication?

No. We connected to Artsdata without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Artsdata MCP server still maintained?

Artsdata is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.