# Ryan Lindsey (remote · mcp.ryanlindsey.me)

Ryan Lindsey's professional corpus, exposed as MCP tools.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `mcp.ryanlindsey.me`: 66/100 (this document), [markdown](https://verifymcp.io/servers/me-ryanlindsey-ryanlindsey-me/mcp.md), [page](https://verifymcp.io/servers/me-ryanlindsey-ryanlindsey-me/mcp)

## Channel facts

- Endpoint: `https://mcp.ryanlindsey.me/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.36.0`

## 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-09-29.

- **Endpoint Security**: 49/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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 is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 605 tokens (~40/item across 15 items; 8 tools + 7 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Ryan Lindsey MCP server?

Ryan Lindsey is a hosted endpoint at https://mcp.ryanlindsey.me/mcp, 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 me-ryanlindsey-ryanlindsey-me 'https://mcp.ryanlindsey.me/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "me-ryanlindsey-ryanlindsey-me": {
      "url": "https://mcp.ryanlindsey.me/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "me-ryanlindsey-ryanlindsey-me": {
      "type": "http",
      "url": "https://mcp.ryanlindsey.me/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.me-ryanlindsey-ryanlindsey-me]
url = "https://mcp.ryanlindsey.me/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "me-ryanlindsey-ryanlindsey-me": {
      "type": "remote",
      "url": "https://mcp.ryanlindsey.me/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add me-ryanlindsey-ryanlindsey-me --url 'https://mcp.ryanlindsey.me/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  me-ryanlindsey-ryanlindsey-me:
    url: "https://mcp.ryanlindsey.me/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "me-ryanlindsey-ryanlindsey-me": {
      "Transport": "http",
      "Url": "https://mcp.ryanlindsey.me/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add me-ryanlindsey-ryanlindsey-me -t streamable-http -u 'https://mcp.ryanlindsey.me/mcp'
```

### Other

```json
{
  "mcpServers": {
    "me-ryanlindsey-ryanlindsey-me": {
      "type": "http",
      "url": "https://mcp.ryanlindsey.me/mcp"
    }
  }
}
```

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-09-29 (score 66, +1)

- [functional] Server version: 1.48.2 → 1.49.1

### 2026-09-28 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 65, 0)

- [functional] Server version: 1.45.1 → 1.46.0

### 2026-09-26 (score 65, +1)

- [functional] New resource “chaining-skills-across-plugins”
- [functional] Server version: 1.44.1 → 1.45.1

### 2026-09-25 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 64, +1)

- [functional] Server version: 1.41.0 → 1.41.4

### 2026-09-23 (score 63, +1)

- [functional] New resource “choosing-a-workflow-over-a-queue”
- [functional] Server version: 1.38.0 → 1.41.0

### 2026-09-22 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.36.0 → 1.38.0

## MCP tools (8)

### `get_contact` (~19 tokens)

Contact details

How to reach Ryan Lindsey, and his working timezone.

### `get_resume` (~53 tokens)

Résumé

Ryan Lindsey's résumé: JSON Resume data, the published markdown document, or a short prose summary.

Input parameters:

- `format` (string): json = JSON Resume schema; markdown = the published document; summary = a short prose read.

### `list_case_studies` (~20 tokens)

List case studies

Published case studies with their metadata and citation URLs.

### `get_case_study` (~36 tokens)

Get a case study

The full markdown of one published case study, by slug.

Input parameters:

- `slug` (string, required): The slug from list_case_studies.

### `list_writing` (~18 tokens)

List writing

Published posts with their descriptions and citation URLs.

### `get_post` (~32 tokens)

Get a post

The full markdown of one published post, by slug.

Input parameters:

- `slug` (string, required): The slug from list_writing.

### `search_writing` (~82 tokens)

Search the writing

Semantic search across the published posts, case studies and résumé. Each result is a passage, the URL it is published at, and an "exact" flag saying whether the excerpt is the passage that matched.

Input parameters:

- `limit` (integer): How many passages to return. Defaults to 5.
- `query` (string, required): What to look for, in natural language.

### `request_private_access` (~23 tokens)

Request private access

Explains the private access tier and how to request a scoped token.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/me-ryanlindsey-ryanlindsey-me/mcp#diagnostics

## Score history

- 2026-09-29: 66
- 2026-09-28: 65
- 2026-09-27: 65
- 2026-09-26: 65
- 2026-09-25: 64
- 2026-09-24: 64
- 2026-09-23: 63
- 2026-09-22: 62
- 2026-09-21: 62

## Common questions

### What is the Ryan Lindsey MCP server?

Ryan Lindsey is an MCP server listed in the public MCP registry as me.ryanlindsey/ryanlindsey-me. Ryan Lindsey's professional corpus, exposed as MCP tools. This page covers its hosted endpoint (https://mcp.ryanlindsey.me/mcp).

### Is the Ryan Lindsey MCP server safe to use?

Ryan Lindsey scores 66 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 Ryan Lindsey MCP server expose?

Ryan Lindsey exposes 8 tools: get_contact, get_resume, list_case_studies, get_case_study, list_writing, and 3 more. Their descriptions and schemas cost roughly 283 tokens of context every time the server is loaded.

### Does the Ryan Lindsey MCP server require authentication?

No. We connected to Ryan Lindsey without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Ryan Lindsey MCP server still maintained?

Ryan Lindsey is still listed as active in the MCP registry. We last reached this channel on 29 September 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://mcp.ryanlindsey.me/mcp
- Repository: https://github.com/ryanlindsey/ryanlindsey.me
- Website: https://ryanlindsey.me/
- Changelog RSS feed: https://verifymcp.io/servers/me-ryanlindsey-ryanlindsey-me/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/me-ryanlindsey-ryanlindsey-me/mcp.json
- HTML version of this page: https://verifymcp.io/servers/me-ryanlindsey-ryanlindsey-me/mcp