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

Citybook

REMOTE · MCP.CITYBOOK.AI

Live Calgary events for AI agents.

Available components

0 this week 82 Trust /100

Last scanned (9 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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

Endpoint Security71
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 370 tokens (~370/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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

  • 10 Oct 26 +2
    • Stability: 0.83 → pass security
  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 9 Sept 26 0
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
  • 28 Aug 26 0

    First indexed and scored.

Diagnostics

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

Captured 5 Nov 2026 · Probed https://mcp.citybook.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=citybook.ai CN=WE1,O=Google Trust Services,C=US 9 Sept 2026 8 Dec 2026 ECDSA 256 ECDSA-SHA256 801963095ad279ae138aa1d550002c08
SANs: citybook.ai, mcp.citybook.ai, *.mcp.citybook.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.citybook.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
citybook.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Protected resource metadata

Retrieved No
Problem no_resource_metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.citybook.ai/mcp Verified 200
http (plaintext) http://mcp.citybook.ai/mcp Inconclusive 405
MCP tools · 1 exposed · ~370 tokens

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

Tool Tokens
fetch_events ~370

Find upcoming local events — community programs, markets, festivals, fitness classes, workshops, and entertainment. Filter by city, neighbourhood, sector, date range, and accessibility flags. Returns rich metadata including geo coordinates, images, structured pricing, recurrence, and accessibility info. Connect and list the paid event tool without a Citybook key. Credential-free fetch_events calls require x402 payment; other tools require Bearer authentication.

NameTypeReqDescription
afterstring–ISO 8601 datetime — only events starting after this time.
beforestring–ISO 8601 datetime — only events starting before this time.
citystringyesCity name (e.g. Calgary, Banff)
commitmentstring–Filter by engagement type: 'drop_in' (no registration), 'register_required' (single-occurrence event needing RSVP/registration), or 'multi_week_program' (recurring multi-week series like 8-week socce…
family_friendlyboolean–Filter for family-friendly events only.
indoor_outdoorstring–Filter by venue type: 'indoor', 'outdoor', or 'both'.
limitnumber–Max results (default 10, max 50)
neighbourhoodstring–Neighbourhood within the city
offsetnumber–Skip first N results for pagination. Default 0.
pet_friendlyboolean–Filter for pet-friendly events only.
sector_idstring–One of: /events/community, /events/government, /events/market, /events/fitness, /events/education, /events/entertainment, /events/tourism
sincestring–ISO 8601 datetime — only events submitted after this time. Use for incremental polling.

No output schema declared.

No examples provided.

Install

How do I install the Citybook MCP server?

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

remote · mcp.citybook.ai

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

What is the Citybook MCP server?

Citybook is an MCP server listed in the public MCP registry as ai.citybook/citybook. Live Calgary events for AI agents. This page covers its hosted endpoint (https://mcp.citybook.ai/mcp).

Is the Citybook MCP server safe to use?

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

What tools does the Citybook MCP server expose?

Citybook exposes 1 tool: fetch_events. Their descriptions and schemas cost roughly 370 tokens of context every time the server is loaded.

Does the Citybook MCP server require authentication?

Yes. Citybook asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Citybook MCP server still maintained?

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