PXL8 verified fight records

io.pxl8由 pxl8.io 發布官方發布者v1.0.0更新於 Oct 27, 2026

Verified fight records for AI assistants: look up a fighter or fight card, cite the pxl8.io page.

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取知識與記憶

概覽

AI 產生的概覽

遠端 MCP 伺服器,讓助理查詢經核實的格鬥運動比賽紀錄、賽事對戰卡及相關公開紀錄,並附可引用的來源頁面。

可以做什麼
  • 依姓名解析選手,回傳候選選手頁面、信心區間與已建檔比賽
  • 讀取單一選手的核實紀錄:比賽日期、結果、勝負方式、發布委員會與文件雜湊
  • 讀取已發布的賽事對戰卡,含賽事單位、日期、場地、狀態與依序排列的對戰
  • 解析並讀取 Pansofica 個人與組織紀錄,含分級事實、來源與狀態
  • 依姓名跨選手與主體紀錄搜尋,並用回傳的 id 讀取任一紀錄
適用情境
適合需要回答選手、比賽歷史或賽事對戰卡問題並引用公開來源頁面的情境,也適合取得分級的人物與組織紀錄。適用於重視出處的研究與事實查核。
執行需求
遠端 streamable HTTP 端點;未宣告任何套件、環境變數或請求標頭,也未宣告身分驗證。需要能存取提供方 API 及其連結的公開頁面。
安裝前請注意
結果僅限提供方已建檔的內容,統計數字是這些比賽的數量而非完整歷史。查詢為唯讀,但回答應使用提供的引用行與標準頁面連結標明出處。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 PXL8 verified fight records,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.pxl8%2Frecords/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "pxl8-verified-fight-records": {
      "type": "http",
      "url": "https://api.pxl8.io/sports-data/mcp"
    }
  }
}

工具

7

find_fighter

Find a fighter

Resolve a fighter's name (optionally with a hometown or region and a discipline) to candidate fighter pages on https://pxl8.io. Answers at most 5 candidates, each with a confidence band, the bouts on file, its canonical page URL and its slug. The name must be at least 3 characters. Every result carries its canonical page URL (`canonicalUrl`) and a `citeAs` attribution line. A tally or bout count is a count of bouts on file from the earliest date on file — it is not a career record. Results are as published by the named athletic commissions and federations. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

輸入參數name必填placediscipline

get_fighter_record

Get a verified fighter record

The verified record for one fighter page (https://pxl8.io/<slug>), exactly as the public page states it: every bout on file with its date, result, method, the commission that published it and the sha256 of that document, plus a tally labelled "on file from <date>". Where the reported grade is released, it is returned as a SEPARATE list that is never added to the verified tally. The record and every bout carry a record status (verified, confirmed by the athlete, corrected at the athlete's request, or disputed) with the date it was last reviewed; a disputed bout stays in the list — the status says only that it is disputed, never why. Every result carries its canonical page URL (`canonicalUrl`) and a `citeAs` attribution line. A tally or bout count is a count of bouts on file from the earliest date on file — it is not a career record. Results are as published by the named athletic commissions and federations. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

輸入參數slug必填

get_event_card

Get an event card

A published event card (https://pxl8.io/event/<slug>): promotion, date, venue, status and the bouts in order, with each corner's name and fighter page where one exists. Every result carries its canonical page URL (`canonicalUrl`) and a `citeAs` attribution line. A tally or bout count is a count of bouts on file from the earliest date on file — it is not a career record. Results are as published by the named athletic commissions and federations. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

輸入參數slug必填

find_subject

Find a person or an organization

Resolve the name of a person or an organization to published records on https://pansofica.com — records whose subject proved who they are and reviewed what is said about them. Answers at most 5 candidates (the name must be at least 3 characters), each carrying its handle and kind. This is a lookup, not a list. The facts come in three separate grades, each its own list, never one merged list or count: facts from a registry document, facts from the open web, and facts stated by the subject. A fact stated by the subject is the subject's own statement, not a confirmation; a disputed fact remains in the answer, marked Disputed, with no reason attached. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

輸入參數kindname必填

get_subject

Get the record of a person or an organization

One published record (https://pansofica.com/<handle> for a person, https://pansofica.com/org/<handle> for an organization), exactly as its public page states it: the facts in three separate lists by grade, each fact with its field, value, sources and status, plus the record status and when it was last reviewed. A fact from a registry document or from the open web carries a status (verified, reported, confirmed by the subject, or disputed); a fact stated by the subject carries NO status — it is a statement, not a confirmation. The facts come in three separate grades, each its own list, never one merged list or count: facts from a registry document, facts from the open web, and facts stated by the subject. A fact stated by the subject is the subject's own statement, not a confirmation; a disputed fact remains in the answer, marked Disputed, with no reason attached. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

輸入參數kind必填handle必填

fetch

Fetch one record

Read one record by the id search returned (person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, au_company:<subject_key>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, eu_tender_notice:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, jp_corporation:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, sg_entity:<subject_key>, company:<subject_key>, uk_contracts_finder_notice:<subject_key>, uk_tender_notice:<subject_key>, uk_sanction:<subject_key>, significant_control:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key>, contract_notice:<subject_key> or restricted_party:<subject_key>). Answers { id, title, text, url, metadata } as one JSON document; metadata carries kind, recordStatus, citeAs and lastReviewed. The text presents facts in three separate grades, each its own list; a fact stated by the subject is the subject's own statement; a disputed fact remains present, marked Disputed. The url and the citeAs line in metadata identify the page for attribution. Each result carries its `url` and the `citeAs` attribution line in `metadata`; a disputed fact remains in the answer, marked with the word Disputed. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

輸入參數id必填

版本歷史

1
  1. v1.0.0最新Sep 18, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。