Skip to content

Cameron Rye Portfolio MCP Server

dev.rye/portfoliorye.devstreamable-httpv1.3.0Scanned

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

12 tools: 1 do something that can't be undone, 1 change things and 10 only read.

Tools: 0 delete, 1 irreversible, 1 write, 10 read.
  • Reads private data · 1
  • Reads text others write · 5
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the Cameron Rye Portfolio MCP Server can do

The Cameron Rye Portfolio MCP Server is published by rye.dev, a domain the MCP Registry verified. It has 12 tools. It can do things that cannot be undone, such as sending, paying or publishing (submit_contact) and create or change data (1 tool: subscribe_newsletter), but cannot delete data. 10 tools only read.

1 tool reads private data (get_reading); 5 tools bring in text other people can write (list_posts, search_posts, search_site and 2 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Can't be undone 1Claude Code: ask
  • submit_contactSend Cameron a message through the site contact form.No findings

    Why it is in this group

    • The name "submit_contact" says "submit": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    Send Cameron a message through the site contact form. Subject to the same validation and per-IP rate limits as the contact form itself.
Changes things 1Claude Code: ask
  • subscribe_newsletterSubscribe an email address to the newsletter.No findings

    Why it is in this group

    • The name "subscribe_newsletter" says "subscribe": a word for a change.
    Description, as the server wrote it
    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.
Only reads 10Show 10 read-only tools
  • get_aboutReturn a short bio about Cameron Rye, the portfolio owner.No findings

    Why it is in this group

    • The name "get_about" says "get": a word for reading.
    Description, as the server wrote it
    Return a short bio about Cameron Rye, the portfolio owner.
  • get_nowReturn what Cameron is currently working on, learning, building, reading, and up to in life — the live /now page sections.No findings

    Why it is in this group

    • The name "get_now" says "get": a word for reading.
    Description, as the server wrote it
    Return what Cameron is currently working on, learning, building, reading, and up to in life — the live /now page sections.
  • get_postReturn the full markdown body and frontmatter of a post by slug.Reads text others writeNo findings

    Why it is in this group

    • The name "get_post" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_post" says "get" and "post": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "return" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Return the full markdown body and frontmatter of a post by slug.
  • get_projectReturn the full markdown body and frontmatter of a project by slug.No findings

    Why it is in this group

    • The name "get_project" says "get": a word for reading.
    Description, as the server wrote it
    Return the full markdown body and frontmatter of a project by slug.
  • get_pulseReturn 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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_pulse" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.
  • get_readingReturn Cameron's reading list — books currently reading, finished, or abandoned, with notes.Reads private dataNo findings

    Why it is in this group

    • The name "get_reading" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    Description, as the server wrote it
    Return Cameron's reading list — books currently reading, finished, or abandoned, with notes. Filter by status if given.
  • list_postsReturn up to N most recent published blog posts.Reads text others writeNo findings

    Why it is in this group

    • The name "list_posts" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe name "list_posts" says "list" and "post": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "return" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Return up to N most recent published blog posts.
  • list_projectsReturn all portfolio projects with their slug, title, and short description.No findings

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.
    Description, as the server wrote it
    Return all portfolio projects with their slug, title, and short description.
  • search_postsCase-insensitive substring match across title, description, and tags.Reads text others writeNo findings

    Why it is in this group

    • The name "search_posts" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe name "search_posts" says "search" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Case-insensitive substring match across title, description, and tags. Returns up to 10 matches.
  • search_siteSemantic (vector similarity) search across blog posts and projects — the same Cloudflare Vectorize retrieval the Ask chatbot uses, without the LLM call.Reads text others writeNo findings

    Why it is in this group

    • The name "search_site" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://rye.dev/.well-known/oauth-protected-resource
Authorization servers
https://rye.dev
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://rye.dev/mcp: tools/list returned 12 tools to an anonymous client, including submit_contact (irreversible), subscribe_newsletter (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.3.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http portfolio https://rye.dev/mcp
claude mcp add --transport http portfolio https://rye.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__portfolio__list_posts",
      "mcp__portfolio__search_posts",
      "mcp__portfolio__search_site",
      "mcp__portfolio__get_post",
      "mcp__portfolio__list_projects",
      "mcp__portfolio__get_project",
      "mcp__portfolio__get_about",
      "mcp__portfolio__get_now",
      "mcp__portfolio__get_reading",
      "mcp__portfolio__get_pulse"
    ],
    "ask": [
      "mcp__portfolio__submit_contact",
      "mcp__portfolio__subscribe_newsletter"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as portfolio. Review it before you use it.

Capability tags behind 6 rules
  • mcp__portfolio__list_posts untrusted-input
  • mcp__portfolio__search_posts untrusted-input
  • mcp__portfolio__search_site untrusted-input
  • mcp__portfolio__get_post untrusted-input
  • mcp__portfolio__get_reading private-data
  • mcp__portfolio__get_pulse untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.rye/portfolio/verify?hash=92a54a7ea2a54cc784fa871dcc7bba976312032bc1bed5ffa4f328af4958ce38" | jq -e '.changed == false'

Pinned hash 92a54a7ea2a5, from Nov 11, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.rye/portfolio/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.rye/portfolio
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.rye/portfolio.svg)](https://radar.anlyon.com/servers/dev.rye/portfolio)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.

Cameron Rye Portfolio MCP Server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Cameron Rye Portfolio MCP Server safe?

No scan can promise that. What its definitions show: 12 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Cameron Rye Portfolio MCP Server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Cameron Rye Portfolio MCP Server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: submit_contact.

What tools does the Cameron Rye Portfolio MCP Server have?

12 tools: 1 irreversible, 1 write, 10 read. submit_contact, subscribe_newsletter, list_posts, search_posts, search_site, get_post, list_projects, get_project and 4 more.

Does the Cameron Rye Portfolio MCP Server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Cameron Rye Portfolio MCP Server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Cameron Rye Portfolio MCP Server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.