Skip to content

Zindies MCP server

co.zindies/zindieszindies.costreamable-httpv1.0.3Scanned

Search independent ZINEs, creators, shops and ZINE events in Japan. No sign-in needed to read.

13 tools: 2 change things and 11 only read.

Tools: 0 delete, 0 irreversible, 2 write, 11 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • 2 findings, 1 high

Tools listed without sign-in. Remote posture

With Anlyon

2 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 Zindies MCP server can do

The Zindies MCP server is published by zindies.co, a domain the MCP Registry verified. It has 13 tools. It can create or change data (2 tools: toggle_favorite and rsvp_event), but cannot delete data. 11 tools only read.

1 tool reads private data (get_event); 1 tool brings in text other people can write (get_event).

The fixed checks matched 2 findings, 1 of them high severity (model-directed-text and long-description). Each one comes with the text it matched.

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

Last scanned Nov 18, 2026, version 1.0.3.

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.

13 tools

Changes things 2Claude Code: ask
  • rsvp_eventRegister ("join") or withdraw ("cancel") the authenticated user's intention to attend a Zindies event.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.
    Description, as the server wrote it
    Register ("join") or withdraw ("cancel") the authenticated user's intention to attend a Zindies event. This is a free RSVP shown on the event page; it is not a ticket purchase or a paid booking. Requires a Bearer token (a User API token, or an OAuth token with the participations:write scope). Act only when the user asked to; to just bookmark an event without attending, use toggle_favorite instead. Unlike toggle_favorite this is not a toggle: `action` states the outcome you want, and repeating a call is safe. - join: adds the user to the event's participants (the public participant count goes up by one and, when the event has a capacity, one place is taken) and also favorites the event. Joining again when already joined creates no duplicate: it succeeds and only replaces the comment if `comment` is given. A new join is refused with `error: "full"` when the capacity is reached and `error: "cancelled"` when the event has been called off. - cancel: removes the participation and deletes its comment for good (the place is freed at once and the count goes down), and also removes the user's favorite on the event, even one made before joining. Cancelling when not joined succeeds and changes nothing else. Joining again later is allowed while places remain. The comment is public: it appears with the participation on the event page. Returns `joined` (the state after the call), `comment` (the stored comment, null when none or after cancel) and `event` (`id`, `title`, `url`). Errors come back as an error result with `error`: "unauthorized", "insufficient_scope", "not_found" (unknown or not yet announced event), "full", "cancelled" or "unprocessable_entity".

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • toggle_favoriteToggle the authenticated user's favorite (shown to them as "follow") on a creator, creation, place, or event, or on an event list (event_zone) / the new-arrivals list of creations …No findings

    Why it is in this group

    • The name "toggle_favorite" says "toggle": a word for a change.
    Description, as the server wrote it
    Toggle the authenticated user's favorite (shown to them as "follow") on a creator, creation, place, or event, or on an event list (event_zone) / the new-arrivals list of creations (creation_zone). Requires a Bearer token (a User API token, or an OAuth token with the favorites:write scope). Act only when the user asked to. It flips the current state: not favorited becomes favorited, favorited becomes not favorited. There is no separate add / remove, so do not call it twice to "make sure" — the second call undoes the first. Read the result to learn the state you ended in; for lists you can check beforehand with list_followable_zones (`following`). Effects: favoriting a creator, creation, place or event adds it to what the user follows on Zindies. Following a list also subscribes the user to notifications of new entries in it. To attend an event use rsvp_event, which favorites the event by itself. Returns `favorited` (true / false: the state after this call) and `target`, the record acted on: `type`, `id`, `token` (null for events) and `name` for a creator / creation / place / event; `type`, `id`, `slug`, `name`, `kind`, `area` and `url` for a list. Errors come back as an error result (`isError: true`) with `error`: "unauthorized" (no or invalid token), "insufficient_scope", or "not_found" — an unknown or non-public token, an event not yet announced, or a list slug that is malformed or names an unknown kind / area. Nothing changes on error.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
Only reads 11Show 11 read-only tools
  • find_places_nearbyFind Zindies places (bookshops, galleries, cafes and other venues that carry ZINEs or host events) around a point, nearest first.No findings

    Why it is in this group

    • The name "find_places_nearby" says "find": a word for reading.
    Description, as the server wrote it
    Find Zindies places (bookshops, galleries, cafes and other venues that carry ZINEs or host events) around a point, nearest first. Use it for "shops near me / near this station"; to find a shop by name use search (type: "place") instead. This tool takes coordinates only, so turn an address or station name into latitude / longitude yourself first. `radius_km` is a hard cutoff on straight-line distance: a place farther away is never returned, however few results there are. When nothing is in range the result is `places: []` with `count: 0` (not an error); retry with a larger radius. At most `limit` places are returned (the nearest ones), with no pagination; `count` is the number returned, not the total in range. Places without known coordinates are never returned. Each place carries `token` (pass it to get_place for address, opening hours and stocked ZINEs, or to list_events_by_place), `name`, `description`, `latitude`, `longitude`, `country`, `distance_km` (rounded to metres) and `url`. `near` echoes the centre and the radius actually applied.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_creationGet a single Zindies creation (zine/publication) by token, with its full creator list, the shops that carry it (places, with address and geo coordinates) and its online shop links …No findings

    Why it is in this group

    • The name "get_creation" says "get": a word for reading.
    Description, as the server wrote it
    Get a single Zindies creation (zine/publication) by token, with its full creator list, the shops that carry it (places, with address and geo coordinates) and its online shop links (online_links). Use it to answer "where can I buy this zine?". Also returns signed testimonials written by recommenders; when quoting one, always include its attribution_text, keep the wording unchanged, and link to its url (the creation page; its share preview shows the testimonial).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_creatorGet the profile of one Zindies creator (author / artist / ZINE maker) by public token: `name`, `title` (their own one-line byline), `bio`, the public page `url`, and `creations`, t…No findings

    Why it is in this group

    • The name "get_creator" says "get": a word for reading.
    Description, as the server wrote it
    Get the profile of one Zindies creator (author / artist / ZINE maker) by public token: `name`, `title` (their own one-line byline), `bio`, the public page `url`, and `creations`, their public works. When to use which tool: - You only have a name or a keyword, not a token: call search first (type: "creator") and pass a hit's `token` here. - Details of one work (description, price, co-creators, shops that carry it, online shop links, testimonials): pass a `creations[].token` to get_creation. This tool returns only `id`, `token`, `title`, `released_year` and `url` per work. - Events the creator hosts or takes part in, or a calendar feed of them: list_events_by_creator with the same token. This tool returns no events. `creations` holds at most the 24 most recently added public works, newest first, and is not paginated; a creator with more shows all of them on the `url` page. It is an empty array when the creator has no public work yet. An unknown token, a private creator, or a person who is only named on an event or a co-authored work and has no Zindies page of their own (such entries carry `name` but no `token`) returns an error result (`isError: true`) with `error: "not_found"`.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_eventGet a single Zindies event by id, with its host (`place`, `organizer_creator`, or `organizer` = an organizing body such as a festival committee), registered creators, reserved boot…Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "get" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "get" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Get a single Zindies event by id, with its host (`place`, `organizer_creator`, or `organizer` = an organizing body such as a festival committee), registered creators, reserved booths, programs (workshops, talks and other sessions held within the event), and `source_posts` (the organizer's own Instagram or note posts introducing exhibitors who are not in `booths`; these people have no Zindies page, so link to `url` for details). `zones` lists the event lists this event appears in, narrowest first (kind in its region, its region, its kind nationwide, nationwide); it is empty when the event is not on the public lists. Each entry in `zones` is an event list on Zindies (`name`, `url`) that you can point the user to for more events like these. Lists can be followed: pass `type` and `slug` to toggle_favorite (target_type = type, token = slug) and new events in the list are delivered to the user. Mention a list once if it helps; follow only when the user asks. list_followable_zones lists every list and whether the user already follows it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_placeGet a single Zindies place (shop/venue) by token, with address, geo coordinates, place type, zines available there, and business hours.2 findings

    Why it is in this group

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

    Findings

    • High

      The description contains "do not tell the user", an instruction to keep something from the user.

      Matched text

      description: "...id so on Zindies — it is not a refusal; do not tell the user the place rejects events. Each entry in..."

      What this check looks for
    • Info

      The description is 2,488 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: ".... list_followable_zones lists every list and whether the user already follows it."

      What this check looks for
    Description, as the server wrote it
    Get a single Zindies place (shop/venue) by token, with address, geo coordinates, place type, zines available there, and business hours. `area` is the JP region slug of the place (null when unknown) and `zones` the event lists for that region and nationwide (empty when the region is unknown): where to look for ZINE events around this shop. `business_hours` (null when the place has published nothing about its hours) carries `status_now` (open / closed / unknown, same judgement as the web page badge), `regular` (free-text hours / holidays / special notes as written by the place) and `calendar` (the place's day-by-day calendar for this month and next: `days` lists only dates the place has set, each with state open / open2 / closed, a `symbol` (○ / ◎ / ✕), opening times and `is_open`; `months[].legend` explains the symbols, `months[].note` carries the month's remark and `ics_url` is an iCal feed of the same calendar for subscribing). A date missing from `calendar.days` has no day-specific setting: fall back to `regular`, do not treat it as closed. Use this to answer "is this shop open on (date)?" without fetching the web page. `events` points at the place's events: `url` (the upcoming-events page) and `calendar`, a subscribable iCal feed of upcoming events (`ics_url`, `webcal_url` for Apple Calendar / Outlook, `google_calendar_url` to add it to Google Calendar). The place thus has two distinct feeds: opening days (`business_hours.calendar.ics_url`) and events (`events.calendar.ics_url`). When the user asks to import or subscribe to a shop's events in their calendar, give them `events.calendar`; for the event list itself use list_events_by_place. `event_proposals` is non-null only when the place has said it is open to people proposing an event to hold there: `terms` (what the place wrote about its space and conditions; may be null) and `contact_url` (the page where a creator or another shop starts that conversation). null means the place has not said so on Zindies — it is not a refusal; do not tell the user the place rejects events. Each entry in `zones` is an event list on Zindies (`name`, `url`) that you can point the user to for more events like these. Lists can be followed: pass `type` and `slug` to toggle_favorite (target_type = type, token = slug) and new events in the list are delivered to the user. Mention a list once if it helps; follow only when the user asks. list_followable_zones lists every list and whether the user already follows it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_appsList the free, no-sign-up tools Zindies offers under zindies.co/apps/ (not data Zindies holds about creators / shops / events).No findings

    Why it is in this group

    • The name "list_apps" says "list": a word for reading.
    Description, as the server wrote it
    List the free, no-sign-up tools Zindies offers under zindies.co/apps/ (not data Zindies holds about creators / shops / events). Use this when the user wants to make a small ZINE by hand (a printable fold-up template) or wants an image of a shop's monthly opening days for Instagram. - `orizine`: a printable template that turns one A4 sheet, cut and folded, into an 8-page A7 mini book. `files` lists every public PDF (pattern / page numbers / binding) with a direct `pdf_url`, and `netprint` when a Japanese convenience-store "Network Print" code is available for it (`user_code`, `expires_at`, `qr_url`; null when there is none right now). Codes are shared by everyone and are renewed before they expire, so always read them from this tool rather than reusing an old one. Print single-sided at 100% scale. The template is CC BY 4.0: credit Zindies; printing, handing out, adapting and selling the ZINEs made with it are free. - `calendar`: a web page that draws a month of opening days / closed days as a 1080x1350 PNG in the browser. It cannot be run through MCP: give the user `url`. If the shop is already registered on Zindies, its opening days are public data — use get_place (`business_hours`) instead of asking the user to re-enter them. Each app carries `next_step`: how its output connects to Zindies (the signature printed on the output, registering as a creator / shop). Mention it once, quietly; do not push it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_eventsList upcoming and ongoing Zindies events (festivals, fairs, exhibitions).No findings

    Why it is in this group

    • The name "list_events" says "list": a word for reading.
    Description, as the server wrote it
    List upcoming and ongoing Zindies events (festivals, fairs, exhibitions). DayEvent (single-day) and PeriodEvent (multi-day) are unified, distinguished by event_type. Default range: today through 60 days ahead. All filters are optional and combine by AND; with none, events nationwide are returned. The response carries `zone`: the event list on Zindies that matches the `area` / `kind` filters used (`type`, `slug`, `name`, `url`), where the user can find more events like these. It reflects those two filters only, not the date range. Lists can be followed: pass `type` and `slug` to toggle_favorite (target_type = type, token = slug) and new events in the list are delivered to the user. Mention a list once if it helps; follow only when the user asks. list_followable_zones lists every list and whether the user already follows it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_events_by_creatorList upcoming and ongoing Zindies events a creator (author/artist) is involved in, identified by the creator's public token.No findings

    Why it is in this group

    • The name "list_events_by_creator" says "list": a word for reading.
    Description, as the server wrote it
    List upcoming and ongoing Zindies events a creator (author/artist) is involved in, identified by the creator's public token. A creator relates to an event in two ways: as the host (events the creator itself hosts; relation "organized") or as a participant (a reserved booth, being listed as a participating creator, or hosting/speaking in one of the event's programs such as a workshop or talk). Use `relation` to choose which to include. Each event carries a `relations` array describing how this creator relates to it. Note that the `organizer` field is a different thing: it is the organizing body (a festival committee or group) that hosts some events, not this creator. Same response shape as list_events otherwise. Default range: today through 60 days ahead. The response also carries `calendar`: a subscribable iCal feed of the creator's upcoming events (`ics_url`, `webcal_url`, `google_calendar_url` — same shape as list_events_by_place). Hand these to the user when they want to follow a creator's events in their calendar app.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_events_by_placeList upcoming and ongoing Zindies events held at a specific place (shop/venue), identified by its public token.No findings

    Why it is in this group

    • The name "list_events_by_place" says "list": a word for reading.
    Description, as the server wrote it
    List upcoming and ongoing Zindies events held at a specific place (shop/venue), identified by its public token. Same semantics and response shape as list_events, but scoped to one place. Default range: today through 60 days ahead. The response also carries `calendar`: a subscribable iCal feed of this place's upcoming events (`ics_url`, plus `webcal_url` for Apple Calendar / Outlook and `google_calendar_url` to add it to Google Calendar). When the user wants to import, subscribe to, or sync a place's events into their calendar app, hand them these URLs instead of copying events one by one — the feed stays up to date as the place adds events. Note this is distinct from the place's opening-days calendar (`business_hours.calendar.ics_url` on get_place).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_followable_zonesList the event lists (nationwide / each region / each kind) and the new-arrivals list that a user can follow.No findings

    Why it is in this group

    • The name "list_followable_zones" says "list": a word for reading.
    Description, as the server wrote it
    List the event lists (nationwide / each region / each kind) and the new-arrivals list that a user can follow. Following a list delivers notifications of new events in it. Pass an entry's `type` and `slug` to toggle_favorite (target_type = type, token = slug) to follow or unfollow it. Coverage: a wider list includes narrower ones. Following nationwide (`all/all`) already covers every region and kind, so do not also follow a region on top of it. `all/<area>` covers every kind in that region, `<kind>/all` covers that kind in every region. By default only single-axis lists are returned. Pass `kind` and/or `area` to also get the combinations for them (e.g. kind=book_club returns book clubs nationwide and in each region, plus the wider lists that cover them), or `combinations: true` for every combination. Filtering by kind or area leaves out the new-arrivals (creation_zone) entry. With a Bearer token that has favorites:read, each entry also carries `following` (true/false) and `covered_by` (the slug of a wider list the user already follows that includes it, or null). `covered_by` is set even when `following` is true, which means the follow is redundant.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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 17, 2026, 15:18 UTC, unchanged since Nov 17, 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
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.zindies.co/.well-known/oauth-protected-resource
Authorization servers
https://zindies.co
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
yes
  • WarnThe whole server

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

    Matched text

    https://mcp.zindies.co/: tools/list returned 12 tools to an anonymous client, including toggle_favorite (write), rsvp_event (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 high1 info
  • The description contains "do not tell the user", an instruction to keep something from the user.

    Matched text

    description: "...id so on Zindies — it is not a refusal; do not tell the user the place rejects events. Each entry in..."

    What this check looks for
  • The description is 2,488 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: ".... list_followable_zones lists every list and whether the user already follows it."

    What this check looks for

History

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

  1. Tools13 changed.~13 changedView diff
  2. Tools1 added, 12 changed.+1 added~12 changedView diff

Install

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

claude mcp add --transport http zindies https://mcp.zindies.co/
claude mcp add --transport http zindies https://mcp.zindies.co/

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__zindies__search",
      "mcp__zindies__get_creator",
      "mcp__zindies__get_creation",
      "mcp__zindies__get_place",
      "mcp__zindies__get_event",
      "mcp__zindies__list_events",
      "mcp__zindies__list_events_by_place",
      "mcp__zindies__list_events_by_creator",
      "mcp__zindies__find_places_nearby",
      "mcp__zindies__list_apps",
      "mcp__zindies__list_followable_zones"
    ],
    "ask": [
      "mcp__zindies__toggle_favorite",
      "mcp__zindies__rsvp_event"
    ],
    "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 zindies. Review it before you use it.

Capability tags behind 1 rule
  • mcp__zindies__get_event private-data, 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/co.zindies/zindies/verify?hash=fe8bd5644bd8a8224f97dc332324f5c28b90566a3fb8269c6a036a5b01e4dad6" | jq -e '.changed == false'

Pinned hash fe8bd5644bd8, from Nov 18, 2026, 14:17 UTC.

Watch

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

https://radar.anlyon.com/servers/co.zindies/zindies/changes.xml

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

Badge

Anlyon Radar badge for co.zindies/zindies
[![Anlyon Radar](https://radar.anlyon.com/badge/co.zindies/zindies.svg)](https://radar.anlyon.com/servers/co.zindies/zindies)

Source: MCP Registry. Synced Nov 18, 2026, 14:17 UTC.

Zindies MCP server: questions and answers

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

Is the Zindies MCP server safe?

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

Can the Zindies MCP server delete data?

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

Can the Zindies 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 Zindies MCP server have?

13 tools: 2 write, 11 read. toggle_favorite, rsvp_event, search, get_creator, get_creation, get_place, get_event, list_events and 5 more.

Does the Zindies MCP server need sign-in or OAuth?

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

Does the Zindies MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Zindies MCP server changed its tools?

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