← Registry

Databases

ultrapedia.run

An MCP server exposing a read-only SQLite database of ultramarathon races, editions, and sources, with tools to search races, retrieve race details, and read cited web pages.

1 endpoint8 known toolsFirst detected November 1, 2026Last detected November 1, 2026

ENDPOINT 1

https://ultrapedia.run/mcp

No auth detected

MCP server metadata

Name
ultrapedia
Capabilities
promptsresourcestools
Server instructions

Ultrapedia is a table of US ultramarathons: dates, locations, distances, courses, prices, aid stations, airports and more. Every value carries the URL it was read from and a verbatim quote from that page, so you can check it and cite it. Use it freely. `search_races` finds races by name, place, distance and date; `get_race` gives one race with the source of every value; `query` runs any SQL SELECT over the views `races`, `editions` and `sources`; `describe` explains every column. The index is kept current by the agents that use it, and that includes you: 1. When you rely on a value for your user, check it against the race's own website if you can. Dates, start times and prices change. 2. If the race's site says something different, or gives a value the index is missing, send it with `propose_correction`: the field, the value, the page URL and a verbatim quote from that page. 3. If you find a race the index does not have, send it with `propose_race`. For anything else (a cancelled race, a duplicate), use `report_problem`. The server fetches each cited page and checks that your quote is on it before it changes anything, so copy the quote exactly. `read_source` shows a page the way the server reads it; copy quotes from there, and use it to open a page your own tools cannot reach. Contribute only what you read on a page, never a guess. Contributing is optional and never needed to answer your user.

Known tools 8

describe

What Ultrapedia holds: the queryable views, every column and what it means, the allowed values of category columns, and how many races there are.

Inferred read-only
query

Run one read-only SQL SELECT (SQLite) over the views `races`, `editions` and `sources`.

Inferred read-only
search_races

Find races.

Inferred read-only
get_race

Everything about one race: its values, its editions, and for every value the page it was read from and the verbatim quote.

Inferred read-only
read_source

Read a public web page the way this server reads it when it checks a quote: its visible text and its links.

Inferred read-only
propose_correction

Send a value for one field of one race, read from a web page — a correction or a value the index is missing.

Potential side effects
propose_race

Send a US ultramarathon the index does not have yet.

Potential side effects
report_problem

Report something a single value cannot fix: a cancelled or discontinued race, two rows for the same race, a race filed under the wrong distance.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ultrapedia]
url = "https://ultrapedia.run/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "ultrapedia": {
      "type": "http",
      "url": "https://ultrapedia.run/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: ultrapedia
Remote MCP URL: https://ultrapedia.run/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ultrapedia": {
      "url": "https://ultrapedia.run/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "ultrapedia": {
      "type": "http",
      "url": "https://ultrapedia.run/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "ultrapedia",
  "transport": "streamable-http",
  "url": "https://ultrapedia.run/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.