# UFCalendar Fight API — MMA MCP server (remote · api.ufcalendar.com)

Fight API MCP: UFC, PFL, BKFC, RIZIN, OKTAGON events, results, stats, rankings, judges scorecards.

- Trust score: 82/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `api.ufcalendar.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-ufcalendar-fight-api/api.md), [page](https://verifymcp.io/servers/com-ufcalendar-fight-api/api)

## Channel facts

- Endpoint: `https://api.ufcalendar.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1684 tokens (~70/item across 24 items; 24 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 76% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the UFCalendar Fight API — MMA MCP server server?

UFCalendar Fight API — MMA MCP server is a hosted endpoint at https://api.ufcalendar.com/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.

### Claude

```bash
claude mcp add --transport http com-ufcalendar-fight-api 'https://api.ufcalendar.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-ufcalendar-fight-api": {
      "url": "https://api.ufcalendar.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-ufcalendar-fight-api": {
      "type": "http",
      "url": "https://api.ufcalendar.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-ufcalendar-fight-api]
url = "https://api.ufcalendar.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-ufcalendar-fight-api": {
      "type": "remote",
      "url": "https://api.ufcalendar.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-ufcalendar-fight-api --url 'https://api.ufcalendar.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-ufcalendar-fight-api:
    url: "https://api.ufcalendar.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-ufcalendar-fight-api": {
      "Transport": "http",
      "Url": "https://api.ufcalendar.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-ufcalendar-fight-api -t streamable-http -u 'https://api.ufcalendar.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-ufcalendar-fight-api": {
      "type": "http",
      "url": "https://api.ufcalendar.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 82, +1)

- [security] Tool “get_predictions_upcoming” rewrote its description, which is the text the model reads

### 2026-09-20 (score 81, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.1 → 1.1.0
- [functional] New tool “get_event_live”

### 2026-09-19 (score 81)

First indexed and scored.

## MCP tools (24)

### `get_plans` (~46 tokens)

Plans and quotas

List the UFCalendar Fight API plans, their monthly request quotas and per-minute limits, and the terms of the no-card trial. Answers "what does this cost" without a credential.

### `list_orgs` (~38 tokens)

List promotions

List the promotions the UFCalendar Fight API covers, with per-org capability flags (stats, rounds, rankings, broadcasts, predictions, scorecards).

### `how_to_connect` (~46 tokens)

How to connect

Explain how to authenticate against the UFCalendar Fight API from this MCP server: an API key bearer token, or signing in with a UFCalendar account. Returns the URLs to do it.

### `list_events` (~152 tokens)

List events

List fight cards by promotion, status and date range. A bare call returns the upcoming schedule, soonest first; pass order=desc for the archive, newest first. Cursor paginated.

Input parameters:

- `cursor` (string): meta.pagination.next_cursor from a previous call.
- `from` (string): Earliest event date, YYYY-MM-DD.
- `limit` (integer)
- `order` (string): asc = soonest first (default for upcoming), desc = newest first.
- `org` (string): Promotion slug, e.g. "ufc". Omit for every covered promotion.
- `status` (string): Filter by event status.
- `to` (string): Latest event date, YYYY-MM-DD.

### `get_event_card` (~53 tokens)

Get an event and its full card

Fetch one event by slug or id with its complete bout order, both corners, venue, broadcast listings and results when the card has been fought.

Input parameters:

- `event` (string, required): Event slug (preferred) or numeric id.

### `get_event_changes` (~50 tokens)

Get an event’s change log

The audit trail for one card: bouts added or cancelled, opponents swapped, start times moved, fighter profiles merged — newest first.

Input parameters:

- `event` (string, required): Event slug (preferred) or numeric id.

### `get_event_live` (~102 tokens)

Get live in-fight stats

The real-time document for an event on fight night: card statuses, the bout in the cage (phase, round, running clock, unofficial totals and per-round stats, referee, a timestamped action timeline) and the last result. Null when nothing is being streamed. UFC only; Pro plans and up. The same document is pushed over wss://live.ufcalendar.com/v1.

Input parameters:

- `event` (string, required): Event slug (preferred) or numeric id.

### `get_fight` (~81 tokens)

Get a bout

Fetch one bout by id. Pass include=stats for per-fight totals, include=rounds for round-by-round statistics, include=scorecards for the official judges’ cards.

Input parameters:

- `fight_id` (required): Bout id, as returned on an event card. Integer or numeric string.
- `include` (array): Extra blocks to fetch in the same call.

### `search` (~50 tokens)

Search fighters and events

Typeahead search across fighters and events in one call. Use it to turn a name a user typed into a slug you can pass to the other tools.

Input parameters:

- `q` (string, required): At least 2 characters.

### `search_fighters` (~95 tokens)

Search the roster

Search the fighter roster by name, nationality or promotion. Cursor paginated. Returns identity fields; use get_fighter for the full record.

Input parameters:

- `country` (string): ISO-3166 alpha-2 code or country name.
- `cursor` (string)
- `limit` (integer)
- `org` (string): Only fighters who have fought for this promotion.
- `q` (string): Name or nickname fragment.

### `get_fighter` (~103 tokens)

Get a fighter

Fetch one fighter by slug or id: bio, record, career statistics and freely licensed portraits. Pass include=history for the full multi-promotion career timeline, include=stats, include=rankings or include=power_index.

Input parameters:

- `fighter` (string, required): Fighter slug (preferred) or numeric id.
- `history_limit` (integer): Cap the career timeline at the N most recent bouts.
- `include` (array): Extra blocks to fetch in the same call.

### `get_rankings` (~115 tokens)

Get a rankings board

The official rankings board for one promotion, point-in-time: pass a date to read the board as it stood that day. Rank 0 is the champion. Pass a division to narrow it.

Input parameters:

- `board` (string): Board name; defaults to the official board.
- `date` (string): Read the board as it stood on this date, YYYY-MM-DD.
- `division` (string): One division, e.g. "lightweight". Omit for the whole board.
- `org` (string, required): Promotion slug.

### `get_champions` (~32 tokens)

Get current champions

Every current champion across the promotions the API covers, with the division and the snapshot date the board was published.

### `get_power_index` (~50 tokens)

Get the UFCalendar Power Index board

The UFCalendar Power Index board for one promotion — our own rating engine, refreshed hourly, with peak rating and fights rated.

Input parameters:

- `limit` (integer)
- `org` (string, required): Promotion slug.

### `get_predictions_upcoming` (~56 tokens)

Get model win probabilities

UFCalendar model win probabilities for upcoming UFC bouts, published about three weeks out and repriced at least weekly. Corner-stamped, so a probability is never shown against the wrong pair. Informational model output, not betting advice.

### `get_broadcast_rights` (~69 tokens)

Get broadcast rights

Who airs one promotion in each country: provider, kind and link. Pass a country code to narrow it to that market plus the worldwide row.

Input parameters:

- `country` (string): ISO-3166 alpha-2 code; adds the worldwide row.
- `org` (string, required): Promotion slug.

### `list_judges` (~88 tokens)

List judges

The judge directory with career aggregates: cards turned in, rounds scored, 10-8s, split cards and lone dissents. Filter by name, promotion or a minimum number of fights.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `min_fights` (integer)
- `org` (string)
- `q` (string): Name fragment.

### `get_judge_scorecards` (~73 tokens)

Get a judge’s scorecards

Every official card one judge has turned in, newest first: per-round points, card totals, decision type and point deductions. Commission records only.

Input parameters:

- `cursor` (string)
- `judge_id` (required): Judge id, from list_judges. Integer or numeric string.
- `limit` (integer)

### `get_usage` (~33 tokens)

Get your API usage

How many requests the calling account has used this month, the plan limit, the per-minute limit and when the counter resets.

### `get_venue` (~45 tokens)

Get a venue

Fetch one venue by id: name, city, region, country, capacity, coordinates and IANA time zone.

Input parameters:

- `venue_id` (required): Venue id. Integer or numeric string.

### `list_webhook_endpoints` (~32 tokens)

List webhook endpoints

List the signed webhook endpoints registered on the calling account, with the event kinds each one subscribes to.

### `create_webhook_endpoint` (~92 tokens)

Register a webhook endpoint

Register an https endpoint to receive signed webhooks (event announced, fight result, card changed, event completed). The signing secret is returned ONCE — store it before the reply is discarded. At most 3 active endpoints per account.

Input parameters:

- `events` (array): Event kinds to subscribe to; omit for all of them.
- `url` (string, required): https:// endpoint that will receive the signed POSTs.

### `rotate_webhook_secret` (~58 tokens)

Rotate a webhook signing secret

Replace the signing secret of one webhook endpoint. The old secret stops verifying immediately, so update the receiver first. The new secret is returned once.

Input parameters:

- `endpoint_id` (required): Endpoint id from list_webhook_endpoints. Integer or numeric string.

### `delete_webhook_endpoint` (~52 tokens)

Delete a webhook endpoint

Permanently remove one webhook endpoint from the calling account. Deliveries to it stop and its delivery history is dropped.

Input parameters:

- `endpoint_id` (required): Endpoint id from list_webhook_endpoints. Integer or numeric string.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-ufcalendar-fight-api/api#diagnostics

## Score history

- 2026-09-22: 82
- 2026-09-21: 82
- 2026-09-20: 81
- 2026-09-19: 81

## Common questions

### What is the UFCalendar Fight API — MMA MCP server server?

UFCalendar Fight API — MMA MCP server is listed in the public MCP registry as com.ufcalendar/fight-api. Fight API MCP: UFC, PFL, BKFC, RIZIN, OKTAGON events, results, stats, rankings, judges scorecards. This page covers its hosted endpoint (https://api.ufcalendar.com/mcp).

### Is the UFCalendar Fight API — MMA MCP server server safe to use?

UFCalendar Fight API — MMA MCP server 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 UFCalendar Fight API — MMA MCP server server expose?

UFCalendar Fight API — MMA MCP server exposes 24 tools: get_plans, list_orgs, how_to_connect, list_events, get_event_card, and 19 more. Their descriptions and schemas cost roughly 1,611 tokens of context every time the server is loaded.

### Does the UFCalendar Fight API — MMA MCP server server require authentication?

Yes. UFCalendar Fight API — MMA MCP server 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 UFCalendar Fight API — MMA MCP server server still maintained?

UFCalendar Fight API — MMA MCP server is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.ufcalendar.com/mcp
- Repository: https://github.com/UFCalendar/fight-api-skill
- Website: https://www.ufcalendar.com/developers/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-ufcalendar-fight-api/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ufcalendar-fight-api/api.json
- HTML version of this page: https://verifymcp.io/servers/com-ufcalendar-fight-api/api