Verified fight records for AI assistants: look up a fighter or fight card, cite the pxl8.io page.
Connect Remote server
claude mcp add --transport http records https://api.pxl8.io/sports-data/mcp
{
"mcpServers": {
"records": {
"url": "https://api.pxl8.io/sports-data/mcp"
}
}
}
{
"servers": {
"records": {
"type": "http",
"url": "https://api.pxl8.io/sports-data/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.pxl8.io/sports-data/mcp
Tools 7 found in our last check
find_fighterResolve 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 characte…
get_fighter_recordThe 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 rep…
get_event_cardA 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…
find_subjectResolve 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 kin…
get_subjectOne 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 stat…
searchSearch 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…
fetchRead one record by the id search returned (person:<handle>, organization:<handle>, fighter:<slug>, hypd:<slug>, event:<slug>, golden_gloves:<tournament>, parcel:<jurisdiction>/<apn>, provider:<npi>, au_company:<subject_key>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>,…
Details
| Endpoint | https://api.pxl8.io/sports-data/mcp (Streamable HTTP) |
| First published | 18 Sep 2026 |
| Last updated | 18 Sep 2026 |
| Registry name | io.pxl8/records |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
