MCP.Market

TheRundown Documentation MCP server

online · 100% uptime
by TheRundown·io.github.TheRundown/documentation·v1.0.1
No reviews yet

Official TheRundown API documentation search. No live data or authenticated Product API calls.

B80/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed TheRundown Documentation MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

TheRundown Documentation MCP tools (3, 2 write)

write = sends, deletes, buys or posts
  • query_docs_filesystem_the_rundown_apiwrite actionFree

    Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the TheRundown API documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything - `head -100 /openapi/tools/chatgpt-actions/openapi.yaml` — read the start of an OpenAPI spec OpenAPI specs for this site are mounted at: `/openapi/tools/chatgpt-actions/openapi.yaml`, `/openapi/openapi.yaml`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication. Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.

  • search_the_rundown_apiFree

    Search across the TheRundown API knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about TheRundown API, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).

  • submit_feedbackwrite actionFree

    Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.

Public scan report

scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it

1 high1 low
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1092ms20/20
  • Tool poisoning3 tool descriptions checked13/15
  • Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
  • Maintenancelast push 22 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Findings (2)

  • highWrite-action tools reachable without authenticationauth.open-write
  • lowUnusually long tool description (over 2,000 characters)poison.long-description
    tool query_docs_filesystem_the_rundown_api: …Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the TheRundown API documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything - `head -100 /openapi/tools/chatgpt-actions/openapi.yaml` — read the start of an OpenAPI spec OpenAPI specs for this site are mounted at: `/openapi/tools/chatgpt-actions/openapi.yaml`, `/openapi/openapi.yaml`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication. Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.…
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How TheRundown Documentation MCP compares

Against every graded E-commerce MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 70% of 2,174 E-commerce servers
Tools
3
the typical E-commerce server has 6
Tools that change things
67%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote E-commerce server answers 100%
Response time
279 ms
faster than 55% of 1,527 E-commerce servers

What its tools let an agent do: 1 read · 2 change

Install TheRundown Documentation MCP in Claude Code, Cursor or VS Code

claude mcp add --transport http documentation https://docs.therundown.io/mcp
Add to Cursor

What the publisher says

From the TheRundown Documentation MCP repository's README, as published. We do not edit it. Read it on GitHub

TheRundown Documentation MCP

This is the official Cursor plugin wrapper for TheRundown's public documentation MCP at https://docs.therundown.io/mcp.

The server searches published API documentation: endpoint contracts, V2 event and market schemas, parameters, market IDs, authentication guidance, plan limits, billing, and integration examples. It is documentation-only. It does not return live odds or scores, access Product API data, or require a customer API key.

Cursor configuration

The plugin supplies this remote MCP configuration:

{
  "mcpServers": {
    "therundown-documentation": {
      "type": "http",
      "url": "https://docs.therundown.io/mcp"
    }
  }
}

This repository supplies Cursor plugin metadata and a standalone mcp.json configuration.

Related official resources

local stdio server that uses a customer-managed API key. It is not a hosted data MCP endpoint.

  • Documentation MCP guide
  • Product API OpenAPI
  • Local Data MCP: a separate,

First conversation

Ask: “Search TheRundown’s documentation for the V2 event and market response hierarchy, then explain which fields identify the event, market, participant, line, price, and price update time. Link to the relevant public documentation.”

Nothing above is checked by us. What we check is on the safety report.

TheRundown Documentation MCP: common questions

Is TheRundown Documentation MCP server safe?
Mostly: it is graded B (80/100). Read the TheRundown Documentation MCP safety report
How do I install TheRundown Documentation MCP?
It runs remotely at docs.therundown.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does TheRundown Documentation MCP need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is TheRundown Documentation MCP maintained?
The last commit was 56 days ago (2026-09-09). The latest release is v1.0.1.
Is TheRundown Documentation MCP up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of TheRundown Documentation MCP?
Servers from other publishers that do the same job: COTAL actions (cotal.ai) MCP server, Apiguru Amazon Data MCP server and PostHog MCP Server.
How does TheRundown Documentation MCP compare with other E-commerce MCP servers?
safety score 80/100 (higher than 70% of 2,174 E-commerce servers); tools 3 (the typical E-commerce server has 6); tools that change things 67% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to TheRundown Documentation MCP

Same job from other publishers: the closest match first, then the best rated.

  • COTAL actions (cotal.ai)
    cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
    B
  • Apiguru Amazon Data
    Live Amazon product, review, search, deal, offer/stock and seller data across 23 marketplaces.
    A
  • PostHog MCP Server
    Official PostHog MCP Server for product analytics, feature flags, experiments, and more.
    A
  • Loki Mode
    Autonomous spec-to-product coding-agent CLI with an MCP server exposing 39 tools over stdio.
    B
  • New-Term Radar
    New AI model, product and repo names as they surface, and the search terms behind them, sized.
    B