Runitonai MCP server
online · 100% uptimeio.github.StructLabs-io/runitonai-mcp·v0.2.0Read-only MCP connector serving the Run It on AI book; index and Implementation Blocks are free.
0 stars
Reviews
Write oneNobody has reviewed Runitonai yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Runitonai tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 201ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityauth enforced (unknown)9/15
- Maintenancelast push 55 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How Runitonai compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 55 ms
- faster than 92% of 30,031 servers
Install Runitonai in Claude Code, Cursor or VS Code
claude mcp add --transport http runitonai-mcp https://mcp.runitonai.com/mcp
What the publisher says
From the Runitonai repository's README, as published. We do not edit it. Read it on GitHub
Run It on AI — the companion server, in full
This repository is the complete source code of the server that powers the Run It on AI reading companion at mcp.runitonai.com. If you bought the book and connected your AI to it, this is everything that runs on our side.
We publish it so you do not have to take our word for anything. The server is a few hundred lines of TypeScript. You (or your AI — paste any file into it and ask) can read exactly what it does and, just as importantly, what it cannot do.
The short version
What reaches our server when you use the companion:
- The name of the tool your AI called (for example "fetch chapter 3").
- The chapter or exercise it asked for.
- Your access code — the license key printed on your Gumroad receipt.
What never reaches us, because there is no code here that could receive, store, or forward it:
No tool, no endpoint, no code path accepts one.
- Your conversations with your AI.
- Your files, documents, or anything on your machine.
- Your name.
- Your email. Search this repository for an email field: there is none.
AI, on your side.
- The picture your AI forms of you while you work. That stays inside your
Who talks to whom: when you add the companion as a Claude connector, your machine never contacts our server directly — Anthropic's cloud brokers the connection. On ChatGPT, OpenAI's cloud does. We see tool calls, not you.
How access works
Your credential is the license key on your Gumroad receipt (a code like XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX). It identifies a purchase, not a person. The server checks it against Gumroad, caches a hash of it for a day, and rate-limits it. Refunded or disabled keys stop working. See src/license.ts — the whole mechanism is one file.
Only chapter text needs the key. The companion's operating instructions (activate) and every Implementation Block — the book's working exercises — are served without any credential at all; the exercises are also published right here in implementation-blocks/.
Connect it
Claude (web or desktop) — the easy path. Settings -> Connectors -> Add custom connector, then paste:
https://mcp.runitonai.com/mcpStart a chat with: Activate Run It on AI — my access code is .
ChatGPT. Use the "Run It on AI Companion" GPT (link in the book), or build your own: create a Custom GPT and import https://mcp.runitonai.com/openapi.yaml as an Action.
Claude Code (terminal users).
claude mcp add --transport http runitonai-book https://mcp.runitonai.com/mcpCodex. In ~/.codex/config.toml:
[mcp_servers.runitonai_book]
url = "https://mcp.runitonai.com/mcp"What is in this repo
Two data files ship as placeholders: src/data/chapters.json (the book's chapter text) and src/data/skill.json (the companion's operating instructions). Both are generated from the book manuscript at deploy time. The book's prose is the product, so it is not in the public repo — but the code that serves it is all here, and the Implementation Blocks (the working exercises) are published in full in implementation-blocks/.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Runitonai: common questions
- Is Runitonai MCP server safe?
- Mostly: it is graded B (83/100). Read the Runitonai safety report
- How do I install Runitonai?
- It runs remotely at mcp.runitonai.com. 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 Runitonai need an API key?
- Yes. The endpoint refuses requests without credentials; the publisher's docs say how to get them.
- Is Runitonai maintained?
- The last commit was 96 days ago (2026-07-31). The latest release is v0.2.0.
- Is Runitonai up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Runitonai compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 55 ms (faster than 92% of 30,031 servers). Full comparison.