PXL8 verified fight records MCP Server

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.

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.

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.

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.

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.

Read one record by the id search returned (person:<handle>, organization:<handle> or fighter:<slug>). 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.

Search Pansofica records of people and organizations and pxl8.io fighter records by name. Each result carries an id in the form the fetch tool reads, and its url. Answers { results: [{ id, title, url }] } as one JSON document: at most 5 person or organization records first, then at most 5 fighter records; a query under 3 characters answers an empty list. A notice member says when one of the two sources could not be searched. This is a lookup, not a list. 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.