# Routine Run: write a routine (remote · api.routinerun.com)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.routinerun.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-routinerun-routine-writer/mcp-public.md), [page](https://verifymcp.io/servers/com-routinerun-routine-writer/mcp-public)

## Channel facts

- Endpoint: `https://api.routinerun.com/mcp/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 346 tokens (~115/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Routine Run: write a routine MCP server?

Routine Run: write a routine is a hosted endpoint at https://api.routinerun.com/mcp/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-routinerun-routine-writer": {
      "url": "https://api.routinerun.com/mcp/public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-routinerun-routine-writer": {
      "type": "http",
      "url": "https://api.routinerun.com/mcp/public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-routinerun-routine-writer]
url = "https://api.routinerun.com/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-routinerun-routine-writer": {
      "type": "remote",
      "url": "https://api.routinerun.com/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-routinerun-routine-writer --url 'https://api.routinerun.com/mcp/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-routinerun-routine-writer:
    url: "https://api.routinerun.com/mcp/public"
```

### Netclaw

```json
{
  "McpServers": {
    "com-routinerun-routine-writer": {
      "Transport": "http",
      "Url": "https://api.routinerun.com/mcp/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-routinerun-routine-writer -t streamable-http -u 'https://api.routinerun.com/mcp/public'
```

### Other

```json
{
  "mcpServers": {
    "com-routinerun-routine-writer": {
      "type": "http",
      "url": "https://api.routinerun.com/mcp/public"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `how_to_write_a_routine` (~51 tokens)

How to write a routine

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.

### `routine_link` (~117 tokens)

Make a link that opens a routine in the app

Checks a routine written in the form how_to_write_a_routine describes and returns a link. Opened on an iPhone with Routine Run, it shows the routine on the app's review screen, where the person saves it or not. Nothing is kept here. Give the person the link and the JSON too, in case the link is opened somewhere else.

Input parameters:

- `routine` (object|string, required): The routine: one JSON object in the form, with "routineRun": 1, a name and its steps. JSON text is read too.

### `find_starter_routine` (~75 tokens)

Find a ready routine

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.

Input parameters:

- `words` (string): What it is for, in a few words. Leave out to list them all.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-routinerun-routine-writer/mcp-public#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 68
- 2026-10-18: 68
- 2026-10-17: 67
- 2026-10-16: 67
- 2026-10-15: 66
- 2026-10-14: 65

## Common questions

### What is the Routine Run: write a routine MCP server?

Routine Run: write a routine is an MCP server listed in the public MCP registry as com.routinerun/routine-writer. Write a step-by-step routine and get a link that opens it in Routine Run on iPhone. No sign-in. This page covers its hosted endpoint (https://api.routinerun.com/mcp/public).

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

Routine Run: write a routine scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Routine Run: write a routine MCP server expose?

Routine Run: write a routine exposes 3 tools: how_to_write_a_routine, routine_link, find_starter_routine. Their descriptions and schemas cost roughly 243 tokens of context every time the server is loaded.

### Does the Routine Run: write a routine MCP server require authentication?

No. We connected to Routine Run: write a routine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Routine Run: write a routine MCP server still maintained?

Routine Run: write a routine is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.routinerun.com/mcp/public
- Repository: https://github.com/routinerun/routinerun
- Website: https://routinerun.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-routinerun-routine-writer/mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-routinerun-routine-writer/mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/com-routinerun-routine-writer/mcp-public