Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cameron Rye Portfolio MCP Server

REMOTE · RYE.DEV · SCANNED SEP 20

Cameron Rye's blog, projects, resume, and live site stats, plus contact and newsletter tools.

Available components

remote · rye.dev 80
0 this week 80 Trust /100
Trust breakdown (7 categories)

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 Security66
  • 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 12 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability84
  • 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 624 tokens (~29/item across 21 items; 12 tools + 9 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (92% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "submit_contact" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the Cameron Rye Portfolio MCP Server server?

Cameron Rye Portfolio MCP Server is a hosted endpoint at https://rye.dev/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 · rye.dev

# add to Claude Code
claude mcp add --transport http dev-rye-portfolio 'https://rye.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-rye-portfolio": {
      "url": "https://rye.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-rye-portfolio": {
      "type": "http",
      "url": "https://rye.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-rye-portfolio]
url = "https://rye.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-rye-portfolio": {
      "type": "remote",
      "url": "https://rye.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-rye-portfolio --url 'https://rye.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-rye-portfolio:
    url: "https://rye.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-rye-portfolio": {
      "Transport": "http",
      "Url": "https://rye.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add dev-rye-portfolio -t streamable-http -u 'https://rye.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "dev-rye-portfolio": {
      "type": "http",
      "url": "https://rye.dev/mcp"
    }
  }
}

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

Changelog

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.

  • 26 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 11 Aug 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
  • 31 Jul 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
  • 30 Jul 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 Jul 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
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Probed https://rye.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rye.dev CN=WE1,O=Google Trust Services,C=US 24 Jun 2026 22 Sept 2026 ECDSA 256 ECDSA-SHA256 cfb43741fe99c0740e83b084c91b157d
SANs: rye.dev
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 rye.dev. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
rye.dev. present 2371 13 Verified
rye.dev. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://rye.dev/mcp Verified 200
http (plaintext) http://rye.dev/mcp HTTPS enforced 301 https://rye.dev/mcp
MCP tools · 12 exposed · ~507 tokens

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 →

Tool Tokens
get_about ~20

Return a short bio about Cameron Rye, the portfolio owner.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_now ~35

Return what Cameron is currently working on, learning, building, reading, and up to in life — the live /now page sections.

Input schema present but exposes no named parameters.

NameTypeReqDescription
sectionsarrayyes–
urlstringyes–

No examples provided.

get_post ~29

Return the full markdown body and frontmatter of a post by slug.

NameTypeReqDescription
slugstringyes–
NameTypeReqDescription
bodystringyes–
frontmatterobjectyes–
slugstringyes–
urlstringyes–

No examples provided.

get_project ~29

Return the full markdown body and frontmatter of a project by slug.

NameTypeReqDescription
slugstringyes–
NameTypeReqDescription
bodystringyes–
frontmatterobjectyes–
slugstringyes–
urlstringyes–

No examples provided.

get_pulse ~60

Return live, PII-free operational stats for rye.dev: recent Core Web Vitals p75s, 30-day pageviews, trailing-30d uptime %, top-reacted pages, and the last deploy. Same data the homepage pulse strip shows.

Input schema present but exposes no named parameters.

NameTypeReqDescription
pulseobjectyes–
urlstringyes–

No examples provided.

get_reading ~40

Return Cameron's reading list — books currently reading, finished, or abandoned, with notes. Filter by status if given.

NameTypeReqDescription
statusstring––
NameTypeReqDescription
booksarrayyes–
urlstringyes–

No examples provided.

list_posts ~25

Return up to N most recent published blog posts.

NameTypeReqDescription
limitinteger––
NameTypeReqDescription
postsarrayyes–

No examples provided.

list_projects ~22

Return all portfolio projects with their slug, title, and short description.

Input schema present but exposes no named parameters.

NameTypeReqDescription
projectsarrayyes–

No examples provided.

search_posts ~35

Case-insensitive substring match across title, description, and tags. Returns up to 10 matches.

NameTypeReqDescription
querystringyes–
NameTypeReqDescription
matchesarrayyes–

No examples provided.

search_site ~94

Semantic (vector similarity) search across blog posts and projects — the same Cloudflare Vectorize retrieval the Ask chatbot uses, without the LLM call. Broader than search_posts (which only does exact substring matching on title/description/tags): finds conceptually related content even when the query words never appear verbatim. Returns scored chunks with deep-link URLs.

NameTypeReqDescription
limitinteger––
querystringyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

submit_contact ~62

Send Cameron a message through the site contact form. Subject to the same validation and per-IP rate limits as the contact form itself.

NameTypeReqDescription
emailstringyes–
messagestringyes–
namestringyes–
subjectstringyes–
NameTypeReqDescription
id–yes–
successbooleanyes–

No examples provided.

subscribe_newsletter ~56

Subscribe an email address to the newsletter. Sends a confirmation email; the subscription only becomes active once confirmed. Same validation and per-IP rate limits as the signup form.

NameTypeReqDescription
emailstringyes–
sourcestring––
NameTypeReqDescription
messagestringyes–
successbooleanyes–

No examples provided.

Common questions

What is the Cameron Rye Portfolio MCP Server server?

Cameron Rye Portfolio MCP Server is listed in the public MCP registry as dev.rye/portfolio. Cameron Rye's blog, projects, resume, and live site stats, plus contact and newsletter tools. This page covers its hosted endpoint (https://rye.dev/mcp).

Is the Cameron Rye Portfolio MCP Server server safe to use?

Cameron Rye Portfolio MCP Server scores 80 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 Cameron Rye Portfolio MCP Server server expose?

Cameron Rye Portfolio MCP Server exposes 12 tools: list_posts, search_posts, search_site, get_post, list_projects, and 7 more. Their descriptions and schemas cost roughly 507 tokens of context every time the server is loaded.

Does the Cameron Rye Portfolio MCP Server server require authentication?

No. We connected to Cameron Rye Portfolio MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Cameron Rye Portfolio MCP Server server still maintained?

Cameron Rye Portfolio MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.