729,588 tools. Updated 2026-10-31 19:48
"UFC" matching MCP tools:
- A player's recent games with every raw box-score stat per game — one call instead of one request per event. Use this to answer 'how has X actually performed lately?' and to build L5/L10/L20, season splits and head-to-head yourself. Pass `opponent` for H2H (accepts a full name, nickname or abbreviation — 'Boston Red Sox', 'Red Sox', 'BOS'); the limit applies AFTER that filter, so opponent + limit=10 means the last 10 MEETINGS, not the Boston games among the last 10 games. H2H is not capped to the current season. IMPORTANT: this is the raw box-score archive, NOT graded-prop history — it covers every game with a box score on file, including games no sportsbook priced, so a 'last 10 games' window here really is the last 10 games (one built from propline_get_player_trends silently skips unpriced games). It carries no line, price or grade; use propline_get_player_trends for hit rates against a posted line. `player_team`/`opponent`/`is_home` are null when the player's side can't be identified, and always for individual sports (tennis, golf, UFC) — report them as unknown rather than guessing. Accepts a player_id in place of the name; the response carries player_id (null when the player has none yet).ConnectorNo auth
- Upcoming matches/events for one game, with game-specific filters. When to use: - "What's on this week?" - Calendar UI; team next matches Prefer over: live_matches for not-yet-started fixtures. Do not use when: only in-progress matches needed → live_matches. Filter support (unsupported params are ignored with meta.warnings — do not assume filtering worked): - lol: hours, team (slug), league (slug) - cs2: team, from, to (ISO); hours not applied upstream - cod: team, tournamentId - dota2: limit/cursor primarily; team may be client-filtered where data allows - ufc: hours / from / to applied client-side after bout expansion (API has no hours); event shells labeled by event name; bouts use fighters[] corners Parallel-safe: yes. Upstream cost: 1–2. Example: { "game": "lol", "hours": 72, "team": "t1", "limit": 20 }ConnectorOAuth
- Deep match package: optional timelines, advanced stats, live state/snapshots, full map/game tree, media inventory. When to use: - Analyst deep dive - Live in-game window (LoL/CS2/UFC) - Full demo list Prefer over match_summary only when summary is insufficient. Prefer match_summary for short answers and default cards. Do not use when: first-pass live board (use live_matches + match_summary). Section selection: pass includeTimeline / includeLiveState / includeAdvanced booleans, OR an explicit sections[] list. UFC betting lines: sections:["odds"] (opt-in, never in the default set). If sections[] is non-empty it wins (booleans are ignored). LoL liveState/advanced require gameId. Parallel-safe: yes. Upstream cost: 1–8 (section-gated). Example: { "game": "lol", "matchId": "lol-match-1", "includeTimeline": true, "includeLiveState": false }ConnectorOAuth
- Team/org card: identity, roster, recent matches, and form/trends/radar when available. When to use: - Team page / "who is on this roster?" - Builder team screen sample Prefer over: separate roster + matches + detail via call_api. Do not use when: UFC fighters → player_profile; unknown name → resolve_entity first. Dota may return partial roster (API gap). Prefer slug for lol/cod; teamId for cs2. Parallel-safe: yes. Upstream cost: 2–4. Example: { "game": "lol", "slug": "t1", "recentLimit": 10 }ConnectorOAuth
- COMPOSITE event / fight-night card: identity, bout or match list, optional standings snippet. When to use: - UFC fight night / numbered event page ("UFC 300 card", "Fight Night") - CS2 event hub with match list - Tournament/event overview before match_preview drill-down Bouts come back in card order — main event first, then prelims, then early prelims. Each bout carries weightClass, titleBout, card placement, and (once fought) result { method, round, time, referee, winnerSlug }. Each corner carries images { headshotUrl, bodyImageUrl, imageUrl, proxiedImageUrl }, record, nickname, rank, championStatus, country and flag when upstream supplies them. Use proxiedImageUrl in browsers — the image host sends no CORS header. You do not need call_api per fighter for faces. Prefer over: agent-side resolve + call_api /ufc/events + bout expansion; N+1 match_summary for the card list only; per-fighter call_api just to fetch headshots. Prefer match_preview for one bout/match briefing; match_summary for completed recaps; live_matches for live-only strips; standings alone for pure tables. Do not use when: you only need live scores (live_matches); single finished match recap (match_summary); no event name/id yet and game unknown. Tennis: pass a tournament id/slug to get the draw bracket — rounds carry a round code (Q1..R128, QF, SF, F) with each match's players and score. Set is the primary tennis path here; there is no separate draw tool. Parallel-safe: yes. Upstream cost: 1–4. Example: { "game": "ufc", "eventIdOrSlug": "ufc-300", "includeMatches": true, "includeStandings": false }ConnectorOAuth
- Browse/search teams, players, tournaments, events, fighters with type filter and pagination. When to use: - Typeahead / pickers - "List teams matching…" - Exploring entities without committing to one ID - UFC fighter lookup by name/nickname (uses /ufc/search + client re-rank) Prefer over resolve_entity when the user wants a list. Prefer resolve_entity when chaining one name into a profile tool. Do not use when: fetching a known entity profile — use team_profile or player_profile. UFC: with q set, results are ranked (exact name > multi-token match > nickname). "Jon Jones" should return jon-jones first — never the generic P4P list. Parallel-safe: yes. Upstream cost: 1–3. Example: { "game": "ufc", "q": "Jon Jones", "type": "fighter", "limit": 10 }ConnectorOAuth
Matching MCP Servers
- AlicenseNot gradedqualityBmaintenanceA local file conversion server supporting audio, video, image, document, and specialized formats via Model Context Protocol. It enables batch and single-file conversions without cloud dependencies.6 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables an agent to query MMA data—fight schedules, results, per-round stats, rankings history, judges' scorecards, and consensus odds—across UFC and other promotions directly via Model Context Protocol.17 npmMIT
Matching MCP Connectors
MMA MCP: UFC, PFL, BKFC, RIZIN, OKTAGON results, stats, rankings, scorecards. Free plan, no card.
Give your agents the best data to grow your UGC program. Search 28,000+ Instagram and TikTok UGC creators with public emails, source new creators from a brief, see which of 500+ brands run UGC and who makes it for them, track creator videos, and manage outreach in a creator CRM. Sign in with OAuth (no API key needed); MCP access needs a Premium, Ultra or Enterprise plan, and every plan starts with a 3-day trial. Docs: https://ugcagent.app/features/ugc-agent-mcp/
- Live matches board across primary games, or a single game filter. Normalized labels, scores, and matchIds. When to use: - "What's live right now?" - Ops/dashboard live strip Prefer over: sequential per-game call_api live probes. Do not use when: user wants upcoming fixtures → upcoming_schedule; historical results → match_summary. CS2 live path is /cs2/live; UFC is included in multi-game fan-out. UFC empty board: section.note + emptyReason + health (workerAlive/lag) + optional supervisor/nextCard (non-live); never fake match items from events[]. Parallel-safe: yes. Upstream cost: 1–5 (allSettled). Example: { "game": "all", "limitPerGame": 10 }ConnectorOAuth
- COMPOSITE fight card for one RAF, BKFC or MMA archive event: event identity + bouts in running order with results. When to use: - "RAF 14 card", "BKFC 95 results", "Bellator 142 card", "PRIDE 34", "who won the main event at the last BKFC?" - Event pages and results pages event accepts a slug (e.g. "raf13", "bkfc-95-newark", "bellator-142", "pride-34", "wec-48") or "next" / "last". Bouts come main event first; each carries weight class, title stakes, both sides (athletes for RAF, red/blue fighters for BKFC with punch totals, red/blue fighters for the MMA archives with UFC-format totals and ufcFighterSlug), and once finished the winner and result (RAF: score, takedowns, method; BKFC/MMA archives: method, round, time). MMA archives are closed: event defaults to "last" (the most recent card; for mma, across every promotion), and "next" is a non-retryable NOT_IMPLEMENTED (there are no upcoming cards). Prefer over: combat_events + call_api per bout. Do not use when: you need one bout's period/round breakdown (combat_bout). Parallel-safe: yes. Upstream cost: 2–3. Example: { "league": "raf", "event": "last" }ConnectorOAuth
- COMPOSITE RAF athlete / BKFC or MMA archive fighter page: profile + recent bouts + career stats. When to use: - "Kyle Snyder's RAF record", "Arlovski BKFC stats", "Tito Ortiz in Bellator", "Fedor's PRIDE record", athlete/fighter profile pages athlete accepts a slug ("kyle-snyder") or a name ("Andrei Arlovski"); names are resolved through the league's search, and several matches return AMBIGUOUS_ENTITY with candidates. Profile carries record, division, nickname, country, official headshot (+ its credit — show it with the image). Career stats need the Starter plan; on Free they come back as a partial note while profile and history still return. MMA archives: profile is bio (DOB, height, reach, stance, hometown) + the record in that promotion's archive (not the whole career); stats are career totals in UFC's format. league "mma" covers every archived promotion at once, and data.recordByPromotion splits the record ({ pride: {...}, strikeforce: {...} }). A fighter we also hold a UFC record for keeps the SAME slug as /ufc/fighters/{slug}: data.ufcFighterSlug is set then (a UFC slug is accepted here too). Keep the records apart: archive fights never belong in a UFC answer. Prefer over: call_api profile + history + stats separately. Parallel-safe: yes. Upstream cost: 2–4. Example: { "league": "raf", "athlete": "Kyle Snyder", "historyLimit": 5 }ConnectorOAuth
- The single next upcoming card for one promotion, or across all of them: the soonest event that has not finished. For UFC, developmental sub-series cards (Dana White's Contender Series, Road to UFC) are skipped while a numbered card or Fight Night is booked; pass skip_series=false to include them. Pass include_card=true to get the full bout list in the same metered call.ConnectorNo auth
- Fetch the full fight card for Yahoo Sports' currently featured next UFC event; no event selector is available. Use yahoo_sports_mma_schedule to browse the event schedule instead.ConnectorNo auth
- Lists the 32 SofaScore rankings (type id, name, sport, gender and ranked entity kind) covering FIFA and UEFA football, rugby, ATP/WTA/UTR tennis, padel and UFC/Fight Nation MMA divisions. Use it to find the type id to pass to sofascore_rankings.ConnectorNo auth
- Fetch the full fight card for Yahoo Sports' currently featured next UFC event; no event selector is available. Use yahoo_sports_mma_schedule to browse the event schedule instead.ConnectorNo auth
- Lists the 32 SofaScore rankings (type id, name, sport, gender and ranked entity kind) covering FIFA and UEFA football, rugby, ATP/WTA/UTR tennis, padel and UFC/Fight Nation MMA divisions. Use it to find the type id to pass to sofascore_rankings.ConnectorNo auth
- Use for betting lines: each posted sportsbook's opening, closing and current moneyline for both fighters, with implied probabilities and the total-rounds line. Opening and closing lines start with the UFC cards of June 2020; a median of 5 to 7 books per fight (some fights since mid-2024 have only one book). Pass bout_id for one fight (5 credits) or event_id for a whole card (10 credits). Prices are market information: never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook.ConnectorNo auth
- Composed head-to-head record between two teams, two UFC fighters, or two tennis players. No first-class REST H2H exists — this tool filters match history server-side. When to use: - Rivalry / series record questions - Supporting context for previews Prefer over: agent-side double match-list filtering. Do not use when: single-side form only → team_profile or player_profile. Caveat: Dota filters are weaker; expect meta.warnings when data is sparse. Parallel-safe: yes. Upstream cost: 2–4. Example: { "game": "cs2", "sideA": "faze", "sideB": "navi", "limit": 20 }ConnectorOAuth
- League/event standings or world/division rankings normalized to ranked rows. When to use: - Table / playoff picture - UFC rankings; CS2 world or event standings; CDL standings; LoL league/tournament tables Prefer over: raw standings via call_api for agent-normalized rows. Do not use when: single team form → team_profile; live scores → live_matches. Dota has no first-class standings (may NOT_IMPLEMENTED or weak worldRanking). Required scope keys by game: - lol: leagueId OR tournamentId - cs2: omit for world rankings; eventId for event standings - cod: optional season/stage - ufc: optional division (scope=division) - tennis: optional division (ATP or WTA tour; default ATP) - dota2: best-effort worldRanking only Parallel-safe: yes. Upstream cost: 1–2. Example: { "game": "cod", "season": "2026", "limit": 50 }ConnectorOAuth
- Champions and rankings: RAF title holders per division, BKFC official rankings + champions. BKFC: omit division for every division's ranked list (champion, interim champion, ranked fighters), or pass one (e.g. "heavyweight", "womens-flyweight"). RAF has no ranked lists; it returns every title and its holder, or one division's detail when division is given (e.g. "men-heavyweight"). The MMA archives (bellator, pride, strikeforce, wec, dream, elitexc, affliction, mma) have no rankings: they return a non-retryable NOT_IMPLEMENTED. Never answer with UFC rankings instead. Parallel-safe: yes. Upstream cost: 1. Example: { "league": "bkfc", "division": "heavyweight" }ConnectorOAuth
- Index of raw REST routes from the live OpenAPI spec: method, path, summary, tag. When to use: - You need a long-tail path for call_api and do not want to guess - Checking whether an endpoint exists before building around it - Mapping what raw data backs a curated tool Prefer curated tools for standard jobs — this indexes the escape hatch, it is not a replacement for list_capabilities. Do not use when: a curated tool already covers the outcome (call list_capabilities instead). Note: the spec omits /lol entirely, though LoL routes work. Filtering by game=lol returns that caveat rather than an empty list. Parallel-safe: yes. Upstream cost: 1. Example: { "game": "ufc", "q": "rankings" }ConnectorOAuth
- Fetch Yahoo Sports known UFC event calendar data. Use yahoo_sports_mma_fight_card for the bouts in one event.ConnectorNo auth
- Fetch Yahoo Sports known UFC event calendar data. Use yahoo_sports_mma_fight_card for the bouts in one event.ConnectorNo auth