Skip to content

MCP servers › co.zindies › zindies

MCP server · registry snapshot 2026-11-19 · last tested 2026-11-19

zindies MCP server

Registry name co.zindies/zindies

by zindies.co · domain (the registry's namespace rule)Website ↗

Search independent ZINEs, creators, shops and ZINE events in Japan. No sign-in needed to read. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-19version 1.0.3streamable HTTP13 tools

Summary

co.zindies/zindies is a remote MCP server listed in the official MCP registry at version 1.0.3, under the namespace of the domain zindies.co. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 13 tools, 1 resource and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
13
Last tested
2026-11-19

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-19 (mcp.zindies.co), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.3).

Add to your client

Observed fact

This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (toggle_favorite). That is our reading of the names; we did not call it. Source: our connection, 2026-11-19.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-19
Mode
read-only (no tool calls)
Latest version
1.0.3, published 2026-11-18 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-17 (earliest version still in the registry; older removed versions would be earlier)
Version history
4 versions listed, 2026-11-17 to 2026-11-18; 4 in the 90 days before the 2026-11-19 snapshot.
Most recent 4 versions
  • 1.0.3 · 2026-11-18
  • 1.0.2 · 2026-11-18
  • 1.0.1 · 2026-11-18
  • 1.0.0 · 2026-11-17
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.2 (published 2026-11-18) → 1.0.3 (published 2026-11-18), between the registry lists of 2026-11-18 and 2026-11-19.

No release note: the registry entry links no GitHub repository.

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.

What it is

What does this server offer?

Observed inventory
13tools
1resources
0prompts

None of its 13 tools are described as changing anything. For 13 the reading was uncertain, so no mark is shown.

  • “Search across Zindies creators, creations (zines), places (shops/venues), and events by keyword.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • querystringrequired“Keyword(s), at least 2 characters, e.g.”
    • typestring“Which resource to search: `creator` (authors / artists), `creation` (ZINEs and other works), `place` (shops / venues), `event`, or `all` (default) for the four…”
    • limit_per_typeinteger“Max items per resource type.”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
  • “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • tokenstringrequired“Public token of the creator: a short lowercase string such as "fqpi", taken as-is from the `token` field of a creator in search, get_creation (`creators[].toke…”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
  • get_creationon 4 other servers

    “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).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • tokenstringrequired“Public token of the creation: a short lowercase string such as "k3wd", taken as-is from the `token` field of a creation in search, get_creator (`creations[].to…”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
  • “Get a single Zindies place (shop/venue) by token, with address, geo coordinates, place type, zines available there, and business hours.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • tokenstringrequired“Public token of the place: a short lowercase string such as "fqpi", taken as-is from the `token` field of a place in search, find_places_nearby, get_creation (…”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
  • “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 (works…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • idintegerrequired“Numeric id of the event, e.g.”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
  • “List upcoming and ongoing Zindies events (festivals, fairs, exhibitions).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs
    • fromstring“First day of the range, as an ISO 8601 calendar date in Japan time (YYYY-MM-DD, e.g.”
    • tostring“Last day of the range, inclusive (YYYY-MM-DD, e.g.”
    • areastring“Return only events held in this region of Japan (lowercase slug, e.g.”
    • kindstring“Return only events of this kind (non_genre = general ZINE event, zine_making = ZINE-making workshop, author = author event (talk, signing), festival_style = fa…”
    • event_typestring“`day` = single-day events (they have `started_at` / `ended_at`), `period` = multi-day exhibitions and fairs (`start_date` / `end_date`), `all` = both (default).”
    • limitinteger“Maximum number of events to return, soonest first.”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
  • list_events_by_place

    “List upcoming and ongoing Zindies events held at a specific place (shop/venue), identified by its public token.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs, 1 required
    • place_tokenstringrequired“Public token of the place: a short lowercase string such as "fqpi", the `token` field of a place from search, find_places_nearby, get_place or an event's `plac…”
    • fromstring“First day of the range, as an ISO 8601 calendar date in Japan time (YYYY-MM-DD, e.g.”
    • tostring“Last day of the range, inclusive (YYYY-MM-DD, e.g.”
    • kindstring“Return only events of this kind (non_genre = general ZINE event, zine_making = ZINE-making workshop, author = author event (talk, signing), festival_style = fa…”
    • event_typestring“`day` = single-day events (they have `started_at` / `ended_at`), `period` = multi-day exhibitions and fairs (`start_date` / `end_date`), `all` = both (default).”
    • limitinteger“Maximum number of events to return, soonest first.”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
  • list_events_by_creator

    “List upcoming and ongoing Zindies events a creator (author/artist) is involved in, identified by the creator's public token.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    8 inputs, 1 required
    • creator_tokenstringrequired“Public token of the creator: a short lowercase string such as "fqpi", the `token` field of a creator from search, get_creator, get_creation or get_event.”
    • relationstring“Which events to include: `organized` = events the creator itself hosts, `participating` = events they join through a reserved booth, a listing as participating…”
    • fromstring“First day of the range, as an ISO 8601 calendar date in Japan time (YYYY-MM-DD, e.g.”
    • tostring“Last day of the range, inclusive (YYYY-MM-DD, e.g.”
    • kindstring“Return only events of this kind (non_genre = general ZINE event, zine_making = ZINE-making workshop, author = author event (talk, signing), festival_style = fa…”
    • event_typestring“`day` = single-day events (they have `started_at` / `ended_at`), `period` = multi-day exhibitions and fairs (`start_date` / `end_date`), `all` = both (default).”
    • limitinteger“Maximum number of events to return, soonest first.”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
  • find_places_nearbyon 4 other servers

    “Find Zindies places (bookshops, galleries, cafes and other venues that carry ZINEs or host events) around a point, nearest first.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs, 2 required
    • latitudenumberrequired“Latitude of the search centre in decimal degrees (WGS 84), north positive, e.g.”
    • longitudenumberrequired“Longitude of the search centre in decimal degrees (WGS 84), east positive, e.g.”
    • radius_kmnumber“Search radius in kilometres, straight-line from the centre; a strict upper bound.”
    • limitinteger“Maximum number of places to return, nearest first.”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
  • “List the free, no-sign-up tools Zindies offers under zindies.co/apps/ (not data Zindies holds about creators / shops / events).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • appstring“Return only this tool: `orizine` (fold-up mini ZINE template PDFs and convenience-store print codes) or `calendar` (opening-days image maker).”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
  • list_followable_zones

    “List the event lists (nationwide / each region / each kind) and the new-arrivals list that a user can follow.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • kindstring“Return the lists for this event kind: that kind nationwide and in each region, plus the wider lists covering them (non_genre = general ZINE event, zine_making …”
    • areastring“Return the lists for this region of Japan (lowercase slug, e.g.”
    • combinationsboolean“true = also return every kind x region combination (about a hundred entries); false (default) = only the single-axis lists: nationwide, each region, each kind.”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
  • toggle_favorite

    “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).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 2 required
    • target_typestringrequired“What `token` refers to: `creator`, `creation`, `place` or `event` for a single record; `event_zone` for an event list (the page /events/<kind>/<area>); `creati…”
    • tokenstringrequired“Identifier of the target; its form depends on `target_type`.”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”
Show 1 more tool
  • “Register ("join") or withdraw ("cancel") the authenticated user's intention to attend a Zindies event.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    4 inputs, 1 required
    • event_idintegerrequired“Numeric id of the event, e.g.”
    • actionstring“`join` (default) = make the user a participant; `cancel` = withdraw.”
    • commentstring“Optional short message from the user shown publicly with their participation on the event page, e.g.”
    • localestring“Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-19.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 52
Tools with a description
100% of 13
Typical description length
1,172 characters

The tool set

Counted from the listing

Tools
13
Size of the list
about 9,929 tokens for an agent to load (characters ÷ 4)
Naming
12 of 13 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 13 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-19 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.zindies.co/
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "zindies": {
      "url": "https://mcp.zindies.co/"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "zindies": {
      "type": "http",
      "url": "https://mcp.zindies.co/"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"zindies","type":"http","url":"https://mcp.zindies.co/"}'
Claude Code
claude mcp add --transport http zindies https://mcp.zindies.co/
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "zindies": {
      "type": "streamableHttp",
      "url": "https://mcp.zindies.co/",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "zindies": {
      "httpUrl": "https://mcp.zindies.co/"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.zindies]
url = "https://mcp.zindies.co/"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "zindies": {
      "url": "https://mcp.zindies.co/"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.zindies.co/ --transport http
  • Optional settings the entry also lists (left out above): Authorization.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Own host

  • security.txt. No security.txt at https://mcp.zindies.co/.well-known/ (HTTP 405, 2026-11-19). No security.txt at https://zindies.co/.well-known/ (HTTP 404, 2026-11-19). Source: mcp.zindies.co/.well-known/security.txt · read 2026-11-19.
  • A2A agent card. No A2A agent card at https://mcp.zindies.co/.well-known/ (HTTP 405, 2026-11-19). No A2A agent card at https://zindies.co/.well-known/ (HTTP 404, 2026-11-19). Source: mcp.zindies.co/.well-known/agent-card.json · read 2026-11-19.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.zindies.co/Session openedmatchesour test · 2026-11-19
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-19

Tool list changes

Our reads compared · no tool called

Hosted endpoint mcp.zindies.co

1 of 2 comparisons between consecutive reads showed a change (3 reads, 2026-11-17 to 2026-11-19; versions 1.0.0 to 1.0.3).

Last change seen between our reads on 2026-11-17 (version 1.0.0) and 2026-11-18 (version 1.0.2).

Added (1):

list_followable_zones

Changed (12):

find_places_nearby: description, input schemaget_creation: input schemaget_creator: description, input schemaget_event: description, input schemaget_place: description, input schemalist_apps: input schemalist_events: description, input schemalist_events_by_creator: input schemalist_events_by_place: input schemarsvp_event: description, input schemasearch: description, input schematoggle_favorite: description, input schema

No change in the 1 read since (to 2026-11-19).

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-19 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about co.zindies/zindies

Answered from the data above

Who publishes co.zindies/zindies?

The registry ties the namespace co.zindies to the domain zindies.co; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does co.zindies/zindies need an API key or sign-in?

It opened a session without any credential on 2026-11-19. The registry entry declares no required credential; no declaration is not a guarantee.

Has co.zindies/zindies been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-19
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-19, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 723 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 13 tools, 1 resource, 0 prompts.
  4. 3,580 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-19
MCP capability
logging, prompts, resources, tools
our test · 2026-11-19
Transport
streamable HTTP
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-19

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “co.zindies/zindies: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/co.zindies/zindies

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/co.zindies/zindies)](https://protocolprobe.com/mcp/servers/co.zindies/zindies)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology