Is the Ryla MCP server down?

mcp-registry/ai.ryla/ryla · v1.0.0

healthy
Last checked 2026-10-25 01:14 UTC · handshake 365ms

As of 2026-10-25 01:14 UTC, the Ryla MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 18 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.9%
checks observed
4,665
outages (90d)
18
tools
17

Generate AI influencer photos, face swaps, and character sheets with a consistent face.

Install Ryla MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http ryla-mcp-server https://mcp.ryla.ai/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "ryla-mcp-server": {
      "type": "http",
      "url": "https://mcp.ryla.ai/mcp"
    }
  }
}

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

Agent-readiness: B (84/100)

B (84/100): 0 error(s), 1 warning(s) across 17 tool(s); ~4,632 tokens of tool definitions.
Scores higher than 43% of 15,666 MCP servers Glimind has audited.
Its tool list costs an agent ~4,632 tokens per session — more than 60% of servers.
84 → 84 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability72

What to fix (3)

17 of 17 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. How to fix →

Tools: ryla_account_credits_balance, ryla_account_gallery_list, ryla_character_reference_images, ryla_generate_avatar_video, ryla_generate_base_image and 12 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 7 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fai.ryla%2Fryla/fixes

ryla_account_gallery_list 1 change
{
  "name": "ryla_account_gallery_list",
  "description": "List the authenticated user's most recent generated images/jobs.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 50,
        "minimum": 1,
        "description": "Max number of items to return (default 20, max 50)"
      },
      "detail": {
        "enum": [
          "slim",
          "full"
        ],
        "type": "string",
        "default": "slim",
        "description": "slim (default): status, output URLs and the inputs you set. full: raw job rows incl. internal dispatch fields (very large)."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
ryla_generation_status 1 change
{
  "name": "ryla_generation_status",
  "description": "Check the status of a generation job by its jobId.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "jobId"
    ],
    "properties": {
      "jobId": {
        "type": "string",
        "description": "The jobId returned by a ryla_generate_* tool call"
      },
      "detail": {
        "enum": [
          "slim",
          "full"
        ],
        "type": "string",
        "default": "slim",
        "description": "slim (default): status, output URLs and the inputs you set. full: the raw job row incl. internal dispatch fields (large; for debugging)."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
ryla_list_characters 1 change
{
  "name": "ryla_list_characters",
  "description": "List the authenticated user's existing characters (AI influencers) so you can pick a characterId for the other generation tools. `loraReady` tells you whether `useLora: true` has a trained LoRA to use. There is no tool to CREATE a character -- that happens in the RYLA app at app.ryla.ai.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/ai.ryla/ryla"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.ryla/ryla"}) 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%2Fai.ryla%2Fryla.svg)](https://glimind.com/server/mcp-registry%2Fai.ryla%2Fryla?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fai.ryla%2Fryla?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.ryla%2Fryla.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.ryla%2Fryla.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.ryla%2Fryla?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:b6ec2bf6f3826b85…, first seen 2026-10-22, included at leaf 47054 of 62,746. Version history · verify what your client received.

Tools (17)

Compare: most reliable finance servers · most reliable media servers · most reliable ml servers · most reliable other servers · most reliable devops 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 Ryla MCP server down right now?

As of 2026-10-25 01:14 UTC, the Ryla MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 18 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Ryla MCP server provide?

Ryla MCP server advertises 17 tools, including ryla_account_credits_balance, ryla_account_gallery_list, ryla_character_reference_images, ryla_generate_avatar_video, ryla_generate_base_image.

How do I install Ryla MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.ryla.ai/mcp

Is the Ryla MCP server safe to connect to an AI agent?

Glimind scanned all 17 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 Ryla 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.

Feedback
Help us improve