Content Tools

ryanlindsey.me

Provides tools to retrieve Ryan Lindsey's contact details, resume, case studies, and published writing.

1 endpoint8 known toolsFirst detected September 22, 2026Last detected September 22, 2026

ENDPOINT 1

https://mcp.ryanlindsey.me/mcp

No auth detected

MCP server metadata

Name: ryanlindsey-me
Version: 1.38.0

Capabilities

tools.listChangedresources.listChanged

Server instructions

Ryan Lindsey's professional corpus, exposed as MCP tools across audience tiers. get_contact: how to reach Ryan, and his working timezone. get_resume: JSON Resume, published markdown, or a short prose summary. list_case_studies: published case studies with descriptions and citation URLs. get_case_study: full markdown of one case study, by slug. list_writing: published posts with descriptions and citation URLs. get_post: full markdown of one post, by slug. search_writing: semantic search over the corpus; each result is a passage with a real, fetchable citation URL. request_private_access: explains the private tier and how to request a scoped token. Two MCP resources serve the same documents for clients that prefer resource attachment over tool calls: resume://json and writing://{slug}. A private tier exists beyond these public tools, for scoped tokens; call request_private_access to learn how to request one.

Known tools 8

get_contact

How to reach Ryan Lindsey, and his working timezone.

Inferred read-only

get_resume

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

Inferred read-only

list_case_studies

Published case studies with their metadata and citation URLs.

Inferred read-only

get_case_study

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

Inferred read-only

list_writing

Published posts with their descriptions and citation URLs.

Inferred read-only

get_post

The full markdown of one published post, by slug.

Potential side effects

search_writing

Semantic search across the published posts, case studies and résumé.

Inferred read-only

request_private_access

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ryanlindsey-me]
url = "https://mcp.ryanlindsey.me/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: ryanlindsey-me
Remote MCP URL: https://mcp.ryanlindsey.me/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "ryanlindsey-me",
  "transport": "streamable-http",
  "url": "https://mcp.ryanlindsey.me/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.