Skip to content

runitonai-mcp server

io.github.StructLabs-io/runitonai-mcpStructLabs-iostreamable-httpv0.2.0Scanned

Read-only MCP connector serving the Run It on AI book; index and Implementation Blocks are free.

11 tools: 4 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 4 write, 7 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the runitonai-mcp server can do

The runitonai-mcp server is published by the GitHub account StructLabs-io. It has 11 tools. It can create or change data (4 tools: activate, report_telemetry, save_session_state and forget_session_history), but cannot delete data. 7 tools only read.

1 tool reads private data (get_implementation_block).

The fixed checks matched 1 finding (tool-shadowing). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Changes things 4Claude Code: ask
  • activateStart here.1 finding

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    Findings

    • Warn

      The description contains "any other tool", wording about other tools or servers.

      Matched text

      description: "..., tool usage). Call this FIRST — before any other tool — when the user says "Activate Run It o..."

      What this check looks for
    Description, as the server wrote it
    Start here. Returns the Run It on AI companion's full operating instructions (engagement modes, routing, voice rules, tool usage). Call this FIRST — before any other tool — when the user says "Activate Run It on AI", mentions the Run It on AI ebook, or asks for help choosing/deploying AI in their business. No authentication.
  • forget_session_historyStub — not implemented in Phase 1.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Stub — not implemented in Phase 1. See tool response 'phase' field.
  • report_telemetryStub — not implemented in Phase 1.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Stub — not implemented in Phase 1. See tool response 'phase' field.
  • save_session_stateStub — not implemented in Phase 1.No findings

    Why it is in this group

    • The name "save_session_state" says "save": a word for a change.
    Description, as the server wrote it
    Stub — not implemented in Phase 1. See tool response 'phase' field.
Only reads 7Show 7 read-only tools
  • find_playbookStub — not implemented in Phase 1.No findings

    Why it is in this group

    • The name "find_playbook" says "find": a word for reading.
    Description, as the server wrote it
    Stub — not implemented in Phase 1. See tool response 'phase' field.
  • find_sectionStub — not implemented in Phase 1.No findings

    Why it is in this group

    • The name "find_section" says "find": a word for reading.
    Description, as the server wrote it
    Stub — not implemented in Phase 1. See tool response 'phase' field.
  • get_implementation_blockFetch a structured Implementation Block (reader_prompt, agent_notes, target_artifact) by chapter and name.Reads private dataNo findings

    Why it is in this group

    • The name "get_implementation_block" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "note": it reads notes.
    Description, as the server wrote it
    Fetch a structured Implementation Block (reader_prompt, agent_notes, target_artifact) by chapter and name. Free to call — no access code needed; the Implementation Blocks are public (they also ship in the open-source server repo).
  • get_playbookStub — not implemented in Phase 1.No findings

    Why it is in this group

    • The name "get_playbook" says "get": a word for reading.
    Description, as the server wrote it
    Stub — not implemented in Phase 1. See tool response 'phase' field.
  • get_session_historyStub — not implemented in Phase 1.No findings

    Why it is in this group

    • The name "get_session_history" says "get": a word for reading.
    Description, as the server wrote it
    Stub — not implemented in Phase 1. See tool response 'phase' field.
  • list_book_indexDiscovery: every valid chapter_id with its title — front matter, all chapters, AND all appendices (e.g.No findings

    Why it is in this group

    • The name "list_book_index" says "list": a word for reading.
    Description, as the server wrote it
    Discovery: every valid chapter_id with its title — front matter, all chapters, AND all appendices (e.g. appendix-b-online-reference) — plus Implementation Block names per chapter. Call this whenever unsure which chapter_id to use. No authentication.
  • lookup_chapterFetch a full chapter or a named section by slug — works for appendices too.No findings

    Why it is in this group

    • The name "lookup_chapter" says "lookup": a word for reading.
    Description, as the server wrote it
    Fetch a full chapter or a named section by slug — works for appendices too. Buyer-gated: pass the reader's access_code (their Gumroad license key). Unsure of the slug? Call list_book_index first.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:00 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.runitonai.com/mcp: tools/list returned 11 tools to an anonymous client, including activate (write), report_telemetry (write), save_session_state (write), forget_session_history (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The description contains "any other tool", wording about other tools or servers.

    Matched text

    description: "..., tool usage). Call this FIRST — before any other tool — when the user says "Activate Run It o..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http runitonai https://mcp.runitonai.com/mcp
claude mcp add --transport http runitonai https://mcp.runitonai.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__runitonai__list_book_index",
      "mcp__runitonai__lookup_chapter",
      "mcp__runitonai__get_implementation_block",
      "mcp__runitonai__find_section",
      "mcp__runitonai__find_playbook",
      "mcp__runitonai__get_playbook",
      "mcp__runitonai__get_session_history"
    ],
    "ask": [
      "mcp__runitonai__activate",
      "mcp__runitonai__report_telemetry",
      "mcp__runitonai__save_session_state",
      "mcp__runitonai__forget_session_history"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as runitonai. Review it before you use it.

Capability tags behind 1 rule
  • mcp__runitonai__get_implementation_block private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.StructLabs-io/runitonai-mcp/verify?hash=8002d50a4ea64d23facab8f48ea31d5fa2a55c433b9fb2a8c144f72185fa8c48" | jq -e '.changed == false'

Pinned hash 8002d50a4ea6, from Nov 16, 2026, 06:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.StructLabs-io/runitonai-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.StructLabs-io/runitonai-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.StructLabs-io/runitonai-mcp.svg)](https://radar.anlyon.com/servers/io.github.StructLabs-io/runitonai-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:21 UTC.

runitonai-mcp server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the runitonai-mcp server safe?

No scan can promise that. What its definitions show: 11 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the runitonai-mcp server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the runitonai-mcp server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the runitonai-mcp server have?

11 tools: 4 write, 7 read. activate, report_telemetry, save_session_state, forget_session_history, list_book_index, lookup_chapter, get_implementation_block, find_section and 3 more.

Does the runitonai-mcp server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the runitonai-mcp server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the runitonai-mcp server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.