Ryan Lindsey
REMOTE · MCP.RYANLINDSEY.ME · SCANNED SEP 29
Ryan Lindsey's professional corpus, exposed as MCP tools.
Available components
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. How we score → Why this is hard to score →
Endpoint Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 605 tokens (~40/item across 15 items; 8 tools + 7 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · mcp.ryanlindsey.me
claude mcp add --transport http me-ryanlindsey-ryanlindsey-me 'https://mcp.ryanlindsey.me/mcp'
{
"mcpServers": {
"me-ryanlindsey-ryanlindsey-me": {
"url": "https://mcp.ryanlindsey.me/mcp"
}
}
} {
"servers": {
"me-ryanlindsey-ryanlindsey-me": {
"type": "http",
"url": "https://mcp.ryanlindsey.me/mcp"
}
}
} [mcp_servers.me-ryanlindsey-ryanlindsey-me] url = "https://mcp.ryanlindsey.me/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"me-ryanlindsey-ryanlindsey-me": {
"type": "remote",
"url": "https://mcp.ryanlindsey.me/mcp",
"enabled": true
}
}
} openclaw mcp add me-ryanlindsey-ryanlindsey-me --url 'https://mcp.ryanlindsey.me/mcp' --transport streamable-http
mcp_servers:
me-ryanlindsey-ryanlindsey-me:
url: "https://mcp.ryanlindsey.me/mcp" {
"McpServers": {
"me-ryanlindsey-ryanlindsey-me": {
"Transport": "http",
"Url": "https://mcp.ryanlindsey.me/mcp"
}
}
} assistant mcp add me-ryanlindsey-ryanlindsey-me -t streamable-http -u 'https://mcp.ryanlindsey.me/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 +1
- Server version: 1.48.2 → 1.49.1 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Server version: 1.45.1 → 1.46.0 functional
- 26 Sept 26 +1
- New resource “chaining-skills-across-plugins” functional
- Server version: 1.44.1 → 1.45.1 functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Server version: 1.41.0 → 1.41.4 functional
- 23 Sept 26 +1
- New resource “choosing-a-workflow-over-a-queue” functional
- Server version: 1.38.0 → 1.41.0 functional
- 22 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.36.0 → 1.38.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://mcp.ryanlindsey.me/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ryanlindsey.me | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 76b460e23c20af3f0eb9e36ad755549a |
| SANs: ryanlindsey.me, mcp.ryanlindsey.me, *.mcp.ryanlindsey.me | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.ryanlindsey.me. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| ryanlindsey.me. | present | 2371 | 13 | Verified |
| mcp.ryanlindsey.me. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.ryanlindsey.me/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.ryanlindsey.me/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_case_study Get a case study ~36
The full markdown of one published case study, by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug from list_case_studies. |
No output schema declared.
No examples provided.
get_contact Contact details ~19
How to reach Ryan Lindsey, and his working timezone.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_post Get a post ~32
The full markdown of one published post, by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug from list_writing. |
No output schema declared.
No examples provided.
get_resume Résumé ~53
Ryan Lindsey's résumé: JSON Resume data, the published markdown document, or a short prose summary.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | json = JSON Resume schema; markdown = the published document; summary = a short prose read. |
No output schema declared.
No examples provided.
list_case_studies List case studies ~20
Published case studies with their metadata and citation URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_writing List writing ~18
Published posts with their descriptions and citation URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_private_access Request private access ~23
Explains the private access tier and how to request a scoped token.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_writing Search the writing ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many passages to return. Defaults to 5. |
| query | string | yes | What to look for, in natural language. |
No output schema declared.
No examples provided.
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.