Skip to content

Routine Run: write a routine MCP server

com.routinerun/routine-writerroutinerun.comstreamable-httpv1.0.2Scanned

Write a step-by-step routine and get a link that opens it in Routine Run on iPhone. No sign-in.

3 tools: 2 change things and 1 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 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 Routine Run: write a routine MCP server can do

The Routine Run: write a routine MCP server is published by routinerun.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: how_to_write_a_routine and routine_link), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

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

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 8, 2026, version 1.0.2.

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.

3 tools

Changes things 2Claude Code: ask
  • how_to_write_a_routineThe JSON form Routine Run reads a routine in: every field and every action a step can take.1 finding

    Why it is in this group

    • The name "how_to_write_a_routine" says "write": 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 "how_to_write_a_routine" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "how_to_write_a_routine" says "write": a word for a change.

      What this check looks for
    Description, as the server wrote it
    The JSON form Routine Run reads a routine in: every field and every action a step can take. Use it when writing a routine for routine_link, start_new_run or propose_new_routine.

    Annotations the server declares

    • title: How to write a routine
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • find_starter_routineSearches the routines the app ships — mornings, focus, on call, chores and more — by words in their name or description.No findings

    Why it is in this group

    • The name "find_starter_routine" says "find": a word for reading.
    Description, as the server wrote it
    Searches the routines the app ships — mornings, focus, on call, chores and more — by words in their name or description. Each comes with its steps and a link that adds it in the app.

    Annotations the server declares

    • title: Find a ready routine
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 private-data or untrusted-input or outbound.

Reads private data0
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, 18:46 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
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.routinerun.com/.well-known/oauth-protected-resource/mcp/public
Authorization servers
https://api.routinerun.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

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

    Matched text

    https://api.routinerun.com/mcp/public: tools/list returned 3 tools to an anonymous client, including how_to_write_a_routine (write), routine_link (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "how_to_write_a_routine" says "write": a word for a change.

    What this check looks for
  • The server marks "routine_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "routine_link" says "link": 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 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http routine-writer https://api.routinerun.com/mcp/public
claude mcp add --transport http routine-writer https://api.routinerun.com/mcp/public

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__routine-writer__find_starter_routine"
    ],
    "ask": [
      "mcp__routine-writer__how_to_write_a_routine",
      "mcp__routine-writer__routine_link"
    ],
    "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 routine-writer. Review it before you use it.

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.routinerun/routine-writer/verify?hash=bf5397917178b035ddcd2b02b8096a2b4cc1f0bb7d363657a8888012c450ccd4" | jq -e '.changed == false'

Pinned hash bf5397917178, from Nov 8, 2026, 23:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.routinerun/routine-writer/changes.xml

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

Badge

Anlyon Radar badge for com.routinerun/routine-writer
[![Anlyon Radar](https://radar.anlyon.com/badge/com.routinerun/routine-writer.svg)](https://radar.anlyon.com/servers/com.routinerun/routine-writer)

Source: MCP Registry · repository. Synced Oct 23, 2026, 23:17 UTC.

Routine Run: write a routine MCP server: questions and answers

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

Is the Routine Run: write a routine MCP server safe?

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

Can the Routine Run: write a routine MCP server delete data?

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

Can the Routine Run: write a routine 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 Routine Run: write a routine MCP server have?

3 tools: 2 write, 1 read. how_to_write_a_routine, routine_link and find_starter_routine.

Does the Routine Run: write a routine MCP server need sign-in or OAuth?

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

Does the Routine Run: write a routine MCP server send data to outside services?

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

Has the Routine Run: write a routine MCP server changed its tools?

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