Skip to content

Artlist — Czech contemporary art archive (artlist.cz) MCP server

cz.artlist/archiveartlist.czstreamable-httpv0.5.2Scanned

Czech contemporary art archive: ~24k artists, theorists, artworks, spaces, videos. Free, read-only.

7 tools: 3 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 3 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Artlist — Czech contemporary art archive (artlist.cz) MCP server can do

The Artlist — Czech contemporary art archive (artlist.cz) MCP server is published by artlist.cz, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: artlist-describe, artlist-related and artlist-facets), but cannot delete data. 4 tools only read.

1 tool reads private data (search); 2 tools bring in text other people can write (artlist-get and fetch); 1 tool can send data out of your system (artlist-get). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 7, 2026, version 0.5.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 3Claude Code: ask
  • artlist-describeCall this first.1 finding

    Why it is in this group

    • The name "artlist-describe" says "describe": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "artlist-describe" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true}; The name "artlist-describe" says "describe": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Call this first. Explains record types, public fields, how records link to each other, languages, record counts and how to search well.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • title: Describe the Artlist archive
  • artlist-facetsRecord counts per type and language, and the most used topics; with type: distribution by decade, its topics and the most common places (birth places of persons, cities of spaces).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Record counts per type and language, and the most used topics; with type: distribution by decade, its topics and the most common places (birth places of persons, cities of spaces). Good for overviews and for choosing filters.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • title: Artlist overview numbers
Only reads 4Show 4 read-only tools
  • artlist-getFull public record by id (or page url): all public fields (biography, exhibitions, bibliography, technique, annotations …), every linked record grouped by type (id, type, name, yea…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "artlist-get" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Full public record by id (or page url): all public fields (biography, exhibitions, bibliography, technique, annotations …), every linked record grouped by type (id, type, name, years), and the other language versions. Long texts are cut at 5000 chars unless full=true; images only as image_count unless images=true. For a contributor: annotations_written (every annotation they wrote, with the record, date and text).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • title: Get one Artlist record
  • fetchFull text of one Artlist record by id from search: all public fields, linked records, annotations, with the page URL for citation.Reads text others writeNo findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Full text of one Artlist record by id from search: all public fields, linked records, annotations, with the page URL for citation.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • title: Fetch (standard)

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__archive__artlist-get"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://artlist.cz/wp-json/artlist/mcp: tools/list returned 7 tools to an anonymous client, including artlist-describe (write), artlist-related (write), artlist-facets (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "artlist-describe" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true}; The name "artlist-describe" says "describe": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 0.5.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http archive https://artlist.cz/wp-json/artlist/mcp
claude mcp add --transport http archive https://artlist.cz/wp-json/artlist/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__archive__artlist-search",
      "mcp__archive__search",
      "mcp__archive__fetch"
    ],
    "ask": [
      "mcp__archive__artlist-describe",
      "mcp__archive__artlist-get",
      "mcp__archive__artlist-related",
      "mcp__archive__artlist-facets"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as archive. Review it before you use it.

Capability tags behind 3 rules
  • mcp__archive__artlist-get untrusted-input, outbound
  • mcp__archive__search private-data
  • mcp__archive__fetch untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/cz.artlist/archive/verify?hash=597749a6482ce00ddcf9f6139ccb8cf37937ac2ec253b51d9a40bf7d3552546d" | jq -e '.changed == false'

Pinned hash 597749a6482c, from Nov 7, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/cz.artlist/archive/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for cz.artlist/archive
[![Anlyon Radar](https://radar.anlyon.com/badge/cz.artlist/archive.svg)](https://radar.anlyon.com/servers/cz.artlist/archive)

Source: MCP Registry. Synced Nov 7, 2026, 20:17 UTC.

Artlist — Czech contemporary art archive (artlist.cz) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Artlist — Czech contemporary art archive (artlist.cz) MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Artlist — Czech contemporary art archive (artlist.cz) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Artlist — Czech contemporary art archive (artlist.cz) MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Artlist — Czech contemporary art archive (artlist.cz) MCP server have?

7 tools: 3 write, 4 read. artlist-describe, artlist-related, artlist-facets, artlist-search, artlist-get, search and fetch.

Does the Artlist — Czech contemporary art archive (artlist.cz) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Artlist — Czech contemporary art archive (artlist.cz) MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): artlist-get.

Has the Artlist — Czech contemporary art archive (artlist.cz) MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 7, 2026. Every change is on this page and in its Atom feed.