Skip to content
ProtocolProbe
Explore

MCP servers › io.usefulapi › zenbooker

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.usefulapi/zenbooker

Read Zenbooker jobs, customers, invoices and timeslots; add customers and job notes. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23Topic: commerce-and-marketing · AI-classifiedversion 1.0.1JavaScriptstreamable HTTP21 tools

Summary

io.usefulapi/zenbooker is a remote MCP server listed in the official MCP registry at version 1.0.1. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 21 tools, 0 resources and 1 prompt.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: 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: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Repository
public
Tools
21
Described as changing data
2 of 21 toolsAI-classified
Mainly works on
files and code on the machine it runs on; accounts and data in outside web servicesAI-classified
Topic
commerce-and-marketingAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 2 tools whose name or declaration suggests they change data (zenbooker_add_job_note, zenbooker_create_customer). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 2 tools are described as changing something (zenbooker_add_job_note, zenbooker_create_customer): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

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

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.1 (published 2026-10-22).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
21tools
0resources
1prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; accounts and data in outside web services.

2 of 21 tools are described as changing something (creating, editing, deleting, sending or running).

  • zenbooker_list_jobsreads or searches

    “List jobs (booked appointments), by start time by default, with filters: customer id, assigned team member id, territory id, recurring booking id, status, canceled flag, creation time and scheduled s…”

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

    14 inputs
    • customerstring“Only jobs of this customer id.”
    • assignedstring“Only jobs assigned to this team member (service provider) id.”
    • territorystring“Only jobs in this service territory id.”
    • recurring_bookingstring“Only jobs that belong to this recurring booking id.”
    • statusstring“Only jobs with this status.”
    • canceledboolean“true = only canceled jobs, false = only jobs that are not canceled.”
    • start_date_minstring“Only jobs scheduled to start on or after this ISO 8601 date-time.”
    • start_date_maxstring“Only jobs scheduled to start on or before this ISO 8601 date-time.”
    • created_afterstring“Only items created after this ISO 8601 date-time.”
    • created_beforestring“Only items created before this ISO 8601 date-time.”
    • sort_bystring“Sort field (default start_time).”
    • sort_orderstring“Sort order (default ascending).”
    • cursorinteger“Where to start in the list (default 0).”
    • limitinteger“Results per page, 1-100 (default 20).”
  • zenbooker_get_jobreads or searches

    “One job by id: appointment time, status, customer, service address, services and fields, assigned providers, notes and invoice summary.”

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

    1 input, 1 required
    • job_idstringrequired“The Zenbooker id (the id field of a list result).”
  • zenbooker_add_job_notecreates or changes datadescribed as changing data

    “WRITE: add an internal note (text) to a job.”

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

    2 inputs, 2 required
    • job_idstringrequired“The Zenbooker id (the id field of a list result).”
    • textstringrequired“The note text.”
  • zenbooker_list_recurring_bookingsreads or searches

    “List recurring bookings (repeating job series), by status (active or canceled), customer id, assigned team member id, territory id or creation time.”

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

    9 inputs
    • statusstring“Only recurring bookings with this status.”
    • customerstring“Only recurring bookings of this customer id.”
    • assignedstring“Only recurring bookings assigned to this team member id.”
    • territorystring“Only recurring bookings in this service territory id.”
    • created_afterstring“Only items created after this ISO 8601 date-time.”
    • created_beforestring“Only items created before this ISO 8601 date-time.”
    • sort_orderstring“Sort order (default ascending).”
    • cursorinteger“Where to start in the list (default 0).”
    • limitinteger“Results per page, 1-40 (default 20).”
  • zenbooker_get_recurring_bookingreads or searches

    “One recurring booking by id: first job date, job count, time slot, status, territory, service, pricing and its job ids.”

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

    1 input, 1 required
    • recurring_booking_idstringrequired“The Zenbooker id (the id field of a list result).”
  • zenbooker_list_customersreads or searches

    “List or search customers by name, email or phone, by creation time, or by default address near a place (location + radius in miles).”

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

    10 inputs
    • namestring“Search by customer name.”
    • emailstring“Search by customer email.”
    • phonestring“Search by phone number.”
    • locationstring“A place or address; finds customers whose default address is near it (geocoded by Zenbooker).”
    • radiusinteger“Search radius in miles, used with location.”
    • created_afterstring“Only items created after this ISO 8601 date-time.”
    • created_beforestring“Only items created before this ISO 8601 date-time.”
    • sort_orderstring“Sort order (default ascending).”
    • cursorinteger“Where to start in the list (default 0).”
    • limitinteger“Results per page, 1-100 (default 20).”
  • zenbooker_get_customerreads or searches

    “One customer by id: contact details, notes, addresses, job and recurring booking ids and linked Stripe customer.”

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

    1 input, 1 required
    • customer_idstringrequired“The Zenbooker id (the id field of a list result).”
  • zenbooker_create_customercreates or changes datadescribed as changing data

    “WRITE: create a new customer record in Zenbooker (name required; phone and email optional).”

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

    3 inputs, 1 required
    • namestringrequired“The customer's name.”
    • phonestring“The customer's default phone number.”
    • emailstring“The customer's email address.”
  • zenbooker_list_invoicesreads or searches

    “List invoices, optionally by status (draft, unpaid, partial_paid, paid, void), customer id, territory id or creation time.”

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

    9 inputs
    • statusstring“Only invoices in this status (default: any status).”
    • customerstring“Only invoices of this customer id.”
    • territorystring“Only invoices in this service territory id.”
    • created_afterstring“Only items created after this ISO 8601 date-time.”
    • created_beforestring“Only items created before this ISO 8601 date-time.”
    • sort_bystring“Sort field (default creation_date).”
    • sort_orderstring“Sort order (default ascending).”
    • cursorinteger“Where to start in the list (default 0).”
    • limitinteger“Results per page, 1-100 (default 20).”
  • zenbooker_get_invoicereads or searches

    “One invoice by id: recipient, line items, discounts, tax, totals, amount paid and due, status and transactions.”

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

    1 input, 1 required
    • invoice_idstringrequired“The Zenbooker id (the id field of a list result).”
  • zenbooker_list_transactionsreads or searches

    “List payment transactions, optionally by type (stripe_payment, external_transaction), payment method, status (succeeded, failed, voided), customer id, territory id, creation time or payment date.”

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

    13 inputs
    • typestring“Only transactions of this type.”
    • payment_methodstring“Only transactions paid by this method.”
    • statusstring“Only transactions in this status.”
    • customerstring“Only transactions of this customer id.”
    • territorystring“Only transactions in this service territory id.”
    • transaction_date_afterstring“Only transactions dated after this ISO 8601 date-time.”
    • transaction_date_beforestring“Only transactions dated before this ISO 8601 date-time.”
    • created_afterstring“Only items created after this ISO 8601 date-time.”
    • created_beforestring“Only items created before this ISO 8601 date-time.”
    • sort_bystring“Sort field (default creation_date).”
    • sort_orderstring“Sort order (default ascending).”
    • cursorinteger“Where to start in the list (default 0).”
    • limitinteger“Results per page, 1-100 (default 20).”
  • zenbooker_get_transactionreads or searches

    “One payment transaction by id: status, type, method, amount, invoice and customer ids, Stripe references.”

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

    1 input, 1 required
    • transaction_idstringrequired“The Zenbooker id (the id field of a list result).”
Show 9 more tools
  • zenbooker_list_servicesreads or searches

    “List the services a business offers, with pricing method, base price and duration, option sections and recurring frequencies.”

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

    7 inputs
    • is_visibleboolean“true = only services visible in online booking.”
    • category_idstring“Only services in this category id.”
    • created_afterstring“Only items created after this ISO 8601 date-time.”
    • created_beforestring“Only items created before this ISO 8601 date-time.”
    • sort_orderstring“Sort order (default ascending).”
    • cursorinteger“Where to start in the list (default 0).”
    • limitinteger“Results per page, 1-100 (default 20).”
  • zenbooker_get_servicereads or searches

    “One service by id: pricing, duration, option sections and their options.”

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

    1 input, 1 required
    • service_idstringrequired“The Zenbooker id (the id field of a list result).”
  • zenbooker_list_territoriesreads or searches

    “List the service territories (areas a business serves) with timezone, service area, providers and operating hours.”

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

    7 inputs
    • enabledboolean“true = only active territories, false = only deactivated ones (default both).”
    • namestring“Search by territory name.”
    • created_afterstring“Only items created after this ISO 8601 date-time.”
    • created_beforestring“Only items created before this ISO 8601 date-time.”
    • sort_orderstring“Sort order (default ascending).”
    • cursorinteger“Where to start in the list (default 0).”
    • limitinteger“Results per page, 1-100 (default 20).”
  • zenbooker_get_territoryreads or searches

    “One service territory by id.”

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

    1 input, 1 required
    • territory_idstringrequired“The Zenbooker id (the id field of a list result).”
  • zenbooker_list_team_membersreads or searches

    “List team members (staff and service providers) with role, status, assigned territories, skill tags and work hours.”

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

    9 inputs
    • service_providerboolean“true = only team members who can be assigned jobs.”
    • deactivatedboolean“true = only deactivated team members, false = only active ones.”
    • territorystring“Only providers assigned to this service territory id.”
    • emailstring“Find a team member by email address.”
    • created_afterstring“Only items created after this ISO 8601 date-time.”
    • created_beforestring“Only items created before this ISO 8601 date-time.”
    • sort_orderstring“Sort order (default ascending).”
    • cursorinteger“Where to start in the list (default 0).”
    • limitinteger“Results per page, 1-100 (default 20).”
  • zenbooker_get_team_memberreads or searches

    “One team member by id: contact details, role, status, territories, skill tags and work hours.”

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

    1 input, 1 required
    • team_member_idstringrequired“The Zenbooker id (the id field of a list result).”
  • zenbooker_list_service_requestsreads or searches

    “List incoming service requests (booking requests and quote requests) with status, customer, territory, duration, requested dates, services and pricing.”

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

    8 inputs
    • request_typestring“Only this kind of request.”
    • customerstring“Only requests of this customer id.”
    • territorystring“Only requests in this service territory id.”
    • created_afterstring“Only items created after this ISO 8601 date-time.”
    • created_beforestring“Only items created before this ISO 8601 date-time.”
    • sort_orderstring“Sort order (default ascending).”
    • cursorinteger“Where to start in the list (default 0).”
    • limitinteger“Results per page, 1-100 (default 20).”
  • zenbooker_check_service_areareads or searches

    “Check whether a location is inside the business's service area: returns in_service_area, the matching territory and other territories that serve it (or the closest territory when it is outside every …”

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

    4 inputs
    • postal_codestring“ZIP or postal code.”
    • addressstring“Street address (needed only when there is no postal code or lat/lng).”
    • latnumber“Latitude; send together with lng.”
    • lngnumber“Longitude; send together with lat.”
  • zenbooker_get_timeslotsreads or searches

    “Available booking time slots for a service territory, grouped by day (days[].timeslots[] with start, end and id).”

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

    10 inputs, 2 required
    • territorystringrequired“The service territory id (required).”
    • durationintegerrequired“Service length in minutes (required).”
    • datestring“First day to check, yyyy-mm-dd (default today).”
    • daysinteger“How many days to return (default 7, max 60).”
    • latnumber“Customer latitude (for drive-time aware availability); send with lng.”
    • lngnumber“Customer longitude; send with lat.”
    • min_providers_neededinteger“Minimum number of providers a slot needs (default 1).”
    • service_providersstring“Comma-separated team member ids to restrict slots to.”
    • required_skillsstring“Comma-separated skill tag ids a provider must have.”
    • timeslot_templatestring“A timeslot template id.”

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-10-23.

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

Says what the tool does
100% of 21 tools
Says what it returns
90% of 21 tools
States limits, defaults or errors
40% of 20 tools
Says when to use it
10% of 21 tools
Items covered per tool
2.4 of 4 on average

Counted from the listing

Parameters with a description
100% of 113
Tools with a description
100% of 21
Typical description length
189 characters

The tool set

Counted from the listing

Tools
21
Size of the list
about 6,481 tokens for an agent to load (characters ÷ 4)
Naming
21 of 21 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 21 of 21 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-10-23 (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://zenbooker.usefulapi.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "zenbooker": {
      "url": "https://zenbooker.usefulapi.io/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "zenbooker": {
      "type": "http",
      "url": "https://zenbooker.usefulapi.io/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"zenbooker","type":"http","url":"https://zenbooker.usefulapi.io/mcp"}'
Claude Code
claude mcp add --transport http zenbooker https://zenbooker.usefulapi.io/mcp
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://zenbooker.usefulapi.io/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • 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). 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.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint zenbooker.usefulapi.io/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23
Repository github.com/m190/usefulapi-mcpOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.usefulapi · 341 servers
GitHub owner
a personal account (m190)
Repository
github.com/m190/usefulapi-mcp
Stars
0
Repository age
91–180 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • 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-10-23. 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. How each check works · Leaderboards

Common questions about io.usefulapi/zenbooker

Answered from the data above

Is io.usefulapi/zenbooker safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 2 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/zenbooker need an API key or sign-in?

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

Has io.usefulapi/zenbooker been security tested?

Partly. 3 of the 16 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. No security verdict is published before verification.

What can io.usefulapi/zenbooker do?

It lists 21 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and create or change data. We did not call any tool, so this describes the text, not the behaviour.

Can io.usefulapi/zenbooker change or delete data?

2 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.usefulapi/zenbooker publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.usefulapi/zenbooker?

In github.com/m190/usefulapi-mcp, which opens publicly.

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.

Similar servers

Same topic · AI-read

Active servers whose topic is also “commerce-and-marketing” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

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-10-23
  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: not run · nothing to check it against
  13. Fake assistant turns: not run · an error was returned
  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

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 13
  • 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; 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; 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; 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; 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; 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
  • 12Hidden content
    audience-hiding    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 13Fake assistant turns
    fake-assistant-turn    Checks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
  • 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 · 2
  • 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-10-23, 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. 368 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 21 tools, 0 resources, 1 prompt.
  4. 1,633 msFinished: 3 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
commerce-and-marketing
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
No value: the AI answer was held back because the quoted text did not clearly support it.
Programming language
JavaScript
api.github.com · 2026-10-23
Hosting type
remote (hosted by the publisher)
registry · 2026-10-23
MCP capability
prompts, tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · 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-10-23
Lifecycle status
active
registry · 2026-10-23
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
owner: a personal account · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-10-23
Maintenance
active
api.github.com · 2026-10-23
Environment
the publisher's infrastructure
where it runs, from the hosting type

“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. “io.usefulapi/zenbooker: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.usefulapi/zenbooker

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: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/zenbooker)](https://protocolprobe.com/mcp/servers/io.usefulapi/zenbooker)

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.

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