Ryan Lindsey is a remote MCP server that gives an AI agent 8 tools, among them get_case_study, get_contact, get_post. It answers at https://mcp.ryanlindsey.me/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 23 September 2026; the last check, on 7 November 2026, succeeded.
Ryan Lindsey's professional corpus, exposed as MCP tools.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_case_study | The full markdown of one published case study, by slug. Inputs: slug |
get_contact | How to reach Ryan Lindsey, and his working timezone. |
get_post | The full markdown of one published post, by slug. Inputs: slug |
get_resume | Ryan Lindsey's résumé: JSON Resume data, the published markdown document, or a short prose summary. Inputs: format |
list_case_studies | Published case studies with their metadata and citation URLs. |
list_writing | Published posts with their descriptions and citation URLs. |
request_private_access | Explains the private access tier and how to request a scoped token. |
search_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. Inputs: query, limit |
Every block below points at https://mcp.ryanlindsey.me/mcp. Pick your client and copy.
claude mcp add --transport http ryan-lindsey https://mcp.ryanlindsey.me/mcp
{
"mcpServers": {
"ryan-lindsey": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.ryanlindsey.me/mcp"]
}
}
}{
"mcpServers": {
"ryan-lindsey": {
"url": "https://mcp.ryanlindsey.me/mcp"
}
}
}{
"servers": {
"ryan-lindsey": {
"type": "http",
"url": "https://mcp.ryanlindsey.me/mcp"
}
}
}{
"context_servers": {
"ryan-lindsey": {
"url": "https://mcp.ryanlindsey.me/mcp"
}
}
}{
"mcpServers": {
"ryan-lindsey": {
"serverUrl": "https://mcp.ryanlindsey.me/mcp"
}
}
}{
"mcpServers": {
"ryan-lindsey": {
"url": "https://mcp.ryanlindsey.me/mcp"
}
}
}name: Ryan Lindsey
version: 0.0.1
schema: v1
mcpServers:
- name: Ryan Lindsey
type: streamable-http
url: https://mcp.ryanlindsey.me/mcp{
"mcpServers": {
"ryan-lindsey": {
"httpUrl": "https://mcp.ryanlindsey.me/mcp"
}
}
}{
"mcpServers": {
"ryan-lindsey": {
"type": "http",
"url": "https://mcp.ryanlindsey.me/mcp"
}
}
}{
"mcpServers": {
"ryan-lindsey": {
"url": "https://mcp.ryanlindsey.me/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.ryanlindsey.me%2Fmcp&type=streamable_http&id=ryan-lindsey&name=Ryan%20Lindsey
It answered our last check on 7 November 2026 in 213 ms. Over 4 checks since 23 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by ryanlindsey.me and served from mcp.ryanlindsey.me, the vendor's own domain: https://mcp.ryanlindsey.me/mcp.
8, as returned by the server's own tools/list on 13 November 2026: get_case_study, get_contact, get_post, get_resume, list_case_studies, list_writing, request_private_access, search_writing.
It answered our last check on 7 November 2026 in 213 ms. Over 4 checks since 23 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.ryanlindsey.me/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: me.ryanlindsey. Endpoint host: mcp.ryanlindsey.me. ARD identifier: urn:air:me.ryanlindsey:mcp:ryanlindsey-me.
First indexed 22 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.