Boston Calendar
Server Details
The Boston Calendar MCP.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-boston-calendar
- GitHub Stars
- 0
- Server Listing
- mcp-boston-calendar
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 46 tools
Most tools are genuinely distinct (archive_evidence vs archive_compare, resolution_audit vs resolution_diff, company_facts vs entity_profile are all carefully differentiated in their descriptions). But there are real collision zones: ask_pipeworx / ask_pipeworx_beta (explicitly stated to currently behave identically) / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions form a six-tool cluster an agent must reason through before asking any question, and the prediction-market family (polymarket_edges, polymarket_arbitrage, bet_research, polymarket_edge_tracker, polymarket_fill_risk) requires reading long descriptions to pick correctly. Descriptions do the work, but the boundaries are learned, not obvious.
Everything is snake_case, which is good, and several families use clean prefixes (archive_*, polymarket_*, updown_*, ask_pipeworx*). However the verb/noun convention is mixed: verb_noun tools (resolve_entity, compare_entities, validate_claim, scan_dependency) sit alongside bare nouns (events, tags, company_facts, entity_profile) and bare verbs (remember, recall, forget, subscribe). Readable overall, but not a predictable pattern an agent can extrapolate from.
46 tools is well past the point where any single server's surface stays legible, and the count is inflated by meta-routing tools (discover, suggest, ask_pipeworx x3, deep_research, feedback, trending) layered on top of a catalog router. For a server labeled 'Boston Calendar' the count is wildly disproportionate to the stated purpose. Even judged as a general data gateway, this many tools pushes agents toward the router tools rather than direct calls.
For the apparent Boston Calendar domain there are only two tools (events, tags) — no event detail lookup, no venue/organizer filters, no categories beyond tags, no write or subscription operation specific to calendars. The remaining 44 tools serve an unrelated general-purpose data gateway, so the surface is simultaneously far too broad for the named purpose and thin on the calendar lifecycle itself.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
DataBoston MCP — City of Boston open data (data.boston.gov, CKAN API).
Eventbrite MCP.
Related MCP Servers
- ISC
- AlicenseNot gradedqualityBmaintenanceLets LLMs read and manage Google Calendar events.7,863 npm1,219MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for a desktop calendar that allows AI agents to manage events, check schedules, and avoid conflicts via standard MCP tools.2-
- AlicenseDqualityDmaintenanceMCP server for interacting with Google Calendar, enabling reading events from public calendars and, with OAuth, creating, updating, and deleting events.1ISC
Glama MCP Gateway
Add one secure layer between your agents and this server.