Is the Rye Portfolio MCP server down?

mcp-registry/dev.rye/portfolio · v1.3.0

healthy
Last checked 2026-10-17 07:31 UTC · handshake 4.6s

As of 2026-10-17 07:31 UTC, the Rye Portfolio MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 16 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
99.9%
checks observed
3,592
outages (90d)
16
tools
12

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

Install Rye Portfolio MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "rye-portfolio-mcp-server": {
      "type": "http",
      "url": "https://rye.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (74/100)

C (74/100): 0 error(s), 4 warning(s) across 12 tool(s); ~1,165 tokens of tool definitions.
Scores higher than 10% of 15,262 MCP servers Glimind has audited.
Its tool list costs an agent ~1,165 tokens per session — more than 25% of servers.
no tool-poisoning patterns
Schemas100
Descriptions43
Safety hints13
Token cost100
Client compatibility100
Protocol100
Reliability85
Stability100

What to fix (4)

12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.

Tools: get_about, get_now, get_post, get_project, get_pulse and 7 more

13 parameter(s) across 8 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.

Tools: get_post, get_project, get_reading, list_posts, search_posts and 3 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.

Tools: submit_contact

Handshake + tools/list takes ~2,485 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Auto-fix: 11 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.rye%2Fportfolio/fixes

get_about 1 change 
{
  "name": "get_about",
  "description": "Return a short bio about Cameron Rye, the portfolio owner.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get author profile"
}
get_now 1 change 
{
  "name": "get_now",
  "description": "Return what Cameron is currently working on, learning, building, reading, and up to in life — the live /now page sections.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get current focus (/now)"
}
get_post 1 change 
{
  "name": "get_post",
  "description": "Return the full markdown body and frontmatter of a post by slug.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "minLength": 1
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get blog post"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.rye/portfolio"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.rye/portfolio"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.rye%2Fportfolio.svg)](https://glimind.com/server/mcp-registry%2Fdev.rye%2Fportfolio?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fdev.rye%2Fportfolio?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.rye%2Fportfolio.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.rye%2Fportfolio.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.rye%2Fportfolio?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c57de946647528bc…, first seen 2026-10-17, included at leaf 13322 of 17,129. Version history · verify what your client received.

Tools (12)

Compare: most reliable knowledge servers · most reliable devops servers · most reliable web servers · most reliable data servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Rye Portfolio MCP server down right now?

As of 2026-10-17 07:31 UTC, the Rye Portfolio MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 16 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Rye Portfolio MCP server provide?

Rye Portfolio MCP server advertises 12 tools, including get_about, get_now, get_post, get_project, get_pulse.

How do I install Rye Portfolio MCP server?

Point your MCP client at this streamable-http endpoint: https://rye.dev/mcp

Is the Rye Portfolio MCP server safe to connect to an AI agent?

Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Rye Portfolio MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.