Skip to content

Ricursor MCP server

com.ricursor/ricursorricursor.comstreamable-httpv0.2.0Scanned

Long-term, rotatable project memory and pre-write checks for AI coding agents.

12 tools: 11 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 11 write, 1 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

11 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 Ricursor MCP server can do

The Ricursor MCP server is published by ricursor.com, a domain the MCP Registry verified. It has 12 tools. It can create or change data (11 tools: ricursor_action_check, ricursor_action_consume, ricursor_action_group_check, ricursor_action_group_consume and 7 more), but cannot delete data. 1 tool only reads.

1 tool reads private data (ricursor_snapshot).

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

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 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.

12 tools

Changes things 11Claude Code: ask
  • ricursor_action_checkMetadata-only decision for a JS/TS write or delete.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
    Metadata-only decision for a JS/TS write or delete. Returns allow or block (with reasons to fix) plus a one-use receipt. Never send source.

    Annotations the server declares

    • openWorldHint: false
  • ricursor_action_consumeAtomically consumes a receipt immediately before the broker executes.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
    Atomically consumes a receipt immediately before the broker executes. Fails if anything changed.

    Annotations the server declares

    • openWorldHint: false
  • ricursor_action_group_checkMetadata-only decision for up to 20 related JS/TS writes/deletes judged on their combined end state (moves, renames).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
    Metadata-only decision for up to 20 related JS/TS writes/deletes judged on their combined end state (moves, renames).

    Annotations the server declares

    • openWorldHint: false
  • ricursor_action_group_consumeAll-or-nothing consumption before the broker writes the group.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
    All-or-nothing consumption before the broker writes the group.

    Annotations the server declares

    • openWorldHint: false
  • ricursor_checkStop on block or errors.1 finding

    Why it is in this group

    • The description's first verb is "stop": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "ricursor_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "stop": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Stop on block or errors. Checks tracked versions, exports and accepted import boundaries; never writes code.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ricursor_contextThe verified corrections and recent file changes an agent must respect before it writes code.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The verified corrections and recent file changes an agent must respect before it writes code.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ricursor_correctAfter Ricursor blocks a check, save the one-sentence lesson so every agent on this project gets it.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
    After Ricursor blocks a check, save the one-sentence lesson so every agent on this project gets it. Only accepted for your own blocked action from the last 24 hours.

    Annotations the server declares

    • openWorldHint: false
  • ricursor_handoffSave structured task IDs and versioned rule decisions; never include prompts or source.No findings

    Why it is in this group

    • The description's first verb is "save": a word for a change.
    Description, as the server wrote it
    Save structured task IDs and versioned rule decisions; never include prompts or source.

    Annotations the server declares

    • openWorldHint: false
  • ricursor_reportRecord what an agent spent (usage) and what it changed (state).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
    Record what an agent spent (usage) and what it changed (state).

    Annotations the server declares

    • openWorldHint: false
  • ricursor_snapshotSync locally extracted JS/TS structural metadata only; never transmit source.Reads private dataNo findings

    Why it is in this group

    • The name "ricursor_snapshot" says "snapshot": a word for reading.
    • The description's first verb is "sync": a word for a change.

    What it can reach

    • private-dataThe input names a file (input.files), and the tool reads: it reads files.
    Description, as the server wrote it
    Sync locally extracted JS/TS structural metadata only; never transmit source.

    Annotations the server declares

    • openWorldHint: false
  • ricursor_workspacesThe workspace this key can reach.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The workspace this key can reach.

    Annotations the server declares

    • readOnlyHint: true
Only reads 1Show 1 read-only tool
  • ricursor_ledgerRead scoped metadata and rule versions before switching models.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read scoped metadata and rule versions before switching models. Observe only.

    Annotations the server declares

    • readOnlyHint: true

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 16, 2026, 14:19 UTC, unchanged since Nov 16, 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
11
Protocol version
2025-06-18
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 11 tools that change things (11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.ricursor.com/v1/mcp: tools/list returned 12 tools to an anonymous client, including ricursor_action_check (write), ricursor_action_consume (write), ricursor_action_group_check (write), ricursor_action_group_consume (write), ricursor_correct (write) and 6 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "ricursor_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "stop": a word for a change.

    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 ricursor https://api.ricursor.com/v1/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http ricursor https://api.ricursor.com/v1/mcp --header 'Authorization: <your-authorization>'

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__ricursor__ricursor_ledger"
    ],
    "ask": [
      "mcp__ricursor__ricursor_action_check",
      "mcp__ricursor__ricursor_action_consume",
      "mcp__ricursor__ricursor_action_group_check",
      "mcp__ricursor__ricursor_action_group_consume",
      "mcp__ricursor__ricursor_correct",
      "mcp__ricursor__ricursor_handoff",
      "mcp__ricursor__ricursor_snapshot",
      "mcp__ricursor__ricursor_check",
      "mcp__ricursor__ricursor_workspaces",
      "mcp__ricursor__ricursor_context",
      "mcp__ricursor__ricursor_report"
    ],
    "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 ricursor. Review it before you use it.

Capability tags behind 1 rule
  • mcp__ricursor__ricursor_snapshot 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/com.ricursor/ricursor/verify?hash=7896adb89bda058affaaf33e19ed60e389060ef5baac828965f9e3172a4638e0" | jq -e '.changed == false'

Pinned hash 7896adb89bda, from Nov 15, 2026, 18:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.ricursor/ricursor/changes.xml

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

Badge

Anlyon Radar badge for com.ricursor/ricursor
[![Anlyon Radar](https://radar.anlyon.com/badge/com.ricursor/ricursor.svg)](https://radar.anlyon.com/servers/com.ricursor/ricursor)

Source: MCP Registry. Synced Nov 15, 2026, 18:17 UTC.

Ricursor MCP server: questions and answers

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

Is the Ricursor MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 11 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 Ricursor MCP server delete data?

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

Can the Ricursor 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 Ricursor MCP server have?

12 tools: 11 write, 1 read. ricursor_action_check, ricursor_action_consume, ricursor_action_group_check, ricursor_action_group_consume, ricursor_correct, ricursor_handoff, ricursor_snapshot, ricursor_check and 4 more.

Does the Ricursor MCP server need sign-in or OAuth?

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

Does the Ricursor MCP server send data to outside services?

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

Has the Ricursor MCP server changed its tools?

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