Home / MCP registry index / com.teamcalendar/mcp

TeamCalendar

com.teamcalendar/mcp in the official MCP registry. Endpoint https://teamcalendar.com/api/mcp.

The registry describes it as: Sports schedules, slates and standings, and calendar feeds that keep a team's games up to date.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http teamcalendar https://teamcalendar.com/api/mcp

{
  "mcpServers": {
    "teamcalendar": {
      "url": "https://teamcalendar.com/api/mcp"
    }
  }
}

code --add-mcp '{"name":"teamcalendar","type":"http","url":"https://teamcalendar.com/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

create_composed_calendar create_league_calendar create_named_calendar find_teams get_all_games get_calendar_view get_field_session get_game_scoreboard get_highlight get_league_board get_league_bracket get_league_playoffs get_league_portal get_league_slate get_league_standings get_leagues get_meeting get_series_driver get_series_team get_sports get_team_glance get_team_schedule get_team_season list_league_season_slugs list_seasons list_teams list_upcoming_leagues save_calendar_settings save_team_settings get_published_blog_post list_published_blog_posts

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-13): 0cfd81f91bcc9912. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-teamcalendar-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/com-teamcalendar-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Calendar MCP servers