UFCalendar Fight API — MMA MCP server
REMOTE · API.UFCALENDAR.COM · SCANNED SEP 22
Fight API MCP: UFC, PFL, BKFC, RIZIN, OKTAGON events, results, stats, rankings, judges scorecards.
Available components
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1684 tokens (~70/item across 24 items; 24 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 76% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 25 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
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.
remote · api.ufcalendar.com
claude mcp add --transport http com-ufcalendar-fight-api 'https://api.ufcalendar.com/mcp'
{
"mcpServers": {
"com-ufcalendar-fight-api": {
"url": "https://api.ufcalendar.com/mcp"
}
}
} {
"servers": {
"com-ufcalendar-fight-api": {
"type": "http",
"url": "https://api.ufcalendar.com/mcp"
}
}
} [mcp_servers.com-ufcalendar-fight-api] url = "https://api.ufcalendar.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ufcalendar-fight-api": {
"type": "remote",
"url": "https://api.ufcalendar.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-ufcalendar-fight-api --url 'https://api.ufcalendar.com/mcp' --transport streamable-http
mcp_servers:
com-ufcalendar-fight-api:
url: "https://api.ufcalendar.com/mcp" {
"McpServers": {
"com-ufcalendar-fight-api": {
"Transport": "http",
"Url": "https://api.ufcalendar.com/mcp"
}
}
} assistant mcp add com-ufcalendar-fight-api -t streamable-http -u 'https://api.ufcalendar.com/mcp'
{
"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.
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.
- 21 Sept 26 +1
- Tool “get_predictions_upcoming” rewrote its description, which is the text the model reads security
- 20 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.1 → 1.1.0 functional
- New tool “get_event_live” functional
- 19 Sept 26 81
First indexed and scored.
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 22 Sept 2026 · Probed https://api.ufcalendar.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.ufcalendar.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 19 Aug 2026 | 4 Mar 2027 | RSA 2048 | SHA256-RSA | 709ffe4b31c11f57b03e202098eb5e2 |
| SANs: api.ufcalendar.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.ufcalendar.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ufcalendar.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.ufcalendar.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://api.ufcalendar.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://api.ufcalendar.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.ufcalendar.com/mcp |
| Authorisation server | https://www.ufcalendar.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.ufcalendar.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.ufcalendar.com/mcp | HTTPS enforced | 301 | https://api.ufcalendar.com/mcp |
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 →
create_webhook_endpoint Register a webhook endpoint ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | Event kinds to subscribe to; omit for all of them. |
| url | string | yes | https:// endpoint that will receive the signed POSTs. |
No output schema declared.
No examples provided.
delete_webhook_endpoint Delete a webhook endpoint ~52
Permanently remove one webhook endpoint from the calling account. Deliveries to it stop and its delivery history is dropped.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | – | yes | Endpoint id from list_webhook_endpoints. Integer or numeric string. |
No output schema declared.
No examples provided.
get_broadcast_rights Get broadcast rights ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO-3166 alpha-2 code; adds the worldwide row. |
| org | string | yes | Promotion slug. |
No output schema declared.
No examples provided.
get_champions Get current champions ~32
Every current champion across the promotions the API covers, with the division and the snapshot date the board was published.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_event_card Get an event and its full card ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | Event slug (preferred) or numeric id. |
No output schema declared.
No examples provided.
get_event_changes Get an event’s change log ~50
The audit trail for one card: bouts added or cancelled, opponents swapped, start times moved, fighter profiles merged — newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | Event slug (preferred) or numeric id. |
No output schema declared.
No examples provided.
get_event_live Get live in-fight stats ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | Event slug (preferred) or numeric id. |
No output schema declared.
No examples provided.
get_fight Get a bout ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fight_id | – | yes | Bout id, as returned on an event card. Integer or numeric string. |
| include | array | – | Extra blocks to fetch in the same call. |
No output schema declared.
No examples provided.
get_fighter Get a fighter ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fighter | string | yes | 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. |
No output schema declared.
No examples provided.
get_judge_scorecards Get a judge’s scorecards ~73
Every official card one judge has turned in, newest first: per-round points, card totals, decision type and point deductions. Commission records only.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| judge_id | – | yes | Judge id, from list_judges. Integer or numeric string. |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_plans Plans and quotas ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_power_index Get the UFCalendar Power Index board ~50
The UFCalendar Power Index board for one promotion — our own rating engine, refreshed hourly, with peak rating and fights rated.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| org | string | yes | Promotion slug. |
No output schema declared.
No examples provided.
get_predictions_upcoming Get model win probabilities ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rankings Get a rankings board ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Promotion slug. |
No output schema declared.
No examples provided.
get_usage Get your API usage ~33
How many requests the calling account has used this month, the plan limit, the per-minute limit and when the counter resets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_venue Get a venue ~45
Fetch one venue by id: name, city, region, country, capacity, coordinates and IANA time zone.
| Name | Type | Req | Description |
|---|---|---|---|
| venue_id | – | yes | Venue id. Integer or numeric string. |
No output schema declared.
No examples provided.
how_to_connect How to connect ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_events List events ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_judges List judges ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| min_fights | integer | – | – |
| org | string | – | – |
| q | string | – | Name fragment. |
No output schema declared.
No examples provided.
list_orgs List promotions ~38
List the promotions the UFCalendar Fight API covers, with per-org capability flags (stats, rounds, rankings, broadcasts, predictions, scorecards).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_webhook_endpoints List webhook endpoints ~32
List the signed webhook endpoints registered on the calling account, with the event kinds each one subscribes to.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rotate_webhook_secret Rotate a webhook signing secret ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | – | yes | Endpoint id from list_webhook_endpoints. Integer or numeric string. |
No output schema declared.
No examples provided.
search Search fighters and events ~50
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.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | At least 2 characters. |
No output schema declared.
No examples provided.
search_fighters Search the roster ~95
Search the fighter roster by name, nationality or promotion. Cursor paginated. Returns identity fields; use get_fighter for the full record.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.