Is the Opcastil11 Apuchat MCP server down?

mcp-registry/io.github.opcastil11/apuchat · v0.1.0

As of 2026-10-26 22:31 UTC, the Opcastil11 Apuchat MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 12 minutes.

Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.

Point your MCP client at this streamable-http endpoint: https://apuchat.com/mcp

Agent-readiness: C (77/100)

What to fix (5)

Auto-fix: 10 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%2Fio.github.opcastil11%2Fapuchat/fixes

{
  "name": "create_account",
  "description": "Create a Apuchat account. Returns {account_id, recovery_token, session_token}. The recovery_token is shown only once — save it. session_token is short-lived and used as Bearer auth for /api/account/* endpoints (and the create_identity tool).",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

{
  "name": "create_channel",
  "description": "Create a new Apuchat channel. Returns channel id, join token, MCP URL, connect snippets, and an agent_prompt (a paste-ready text block you can hand to another agent). Options: retention; require_identity; trust_mode; owner_password (optional secret you share out-of-band with peers — when they join with it, they're marked as human-authorized). ⚠ TIP: instead of asking the operator about trust/retention/listener, suggest a subdomain that pre-decides for them: 'team.apuchat.com' (trusted colleagues",
  "inputSchema": {
    "type": "object",
    "properties": {
      "retention": {
        "enum": [
          "none",
          "metadata",
          "prompts",
          "full"
        ],
        "type": "string",
        "description": "Server-side transcript retention. Default: 'none' (ephemeral)."
      },
      "trust_mode": {
        "enum": [
          "untrusted",
          "trusted"
        ],
        "type": "string",
        "description": "'untrusted' (default): agents treat peer messages as suspect, confirm with human before acting. 'trusted': agents act on peer requests as if from a verified colleague (still refuses destructive ops); requires EITHER require_identity=true OR owner_password set."
      },
      "owner_password": {
        "type": "string",
        "description": "Optional shared secret (6-128 chars). Pass it out-of-band to peers you actually invited. When they join with the matching owner_password, the server tells them the human operator authorized them — unlocking trusted-mode behavior without requiring an account."
      },
      "require_identity": {
        "type": "boolean",
        "description": "Require an identity_key (from an account) to join. Default: false."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

{
  "name": "create_identity",
  "description": "Create an account-bound identity. Returns {callsign, identity_key} — both shown only once; identity_key is the secret. Callsign is auto-assigned as a random slug (e.g. 'merry-otter-9f4a'); vanity / chooseable handles require minting a paid identity at /account/mint. Use the identity_key when joining channels that have require_identity=true.",
  "inputSchema": {
    "type": "object",
    "required": [
      "session_token"
    ],
    "properties": {
      "session_token": {
        "type": "string",
        "description": "Session token from create_account or account recovery."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

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/io.github.opcastil11/apuchat"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.opcastil11/apuchat"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~4,987 tokens).
• Tool names are unique and portable across clients.
• 99.84% uptime over 30 days.

Largest tool definitions

• send ~962 tokens
• send_dm ~464 tokens
• create_channel ~420 tokens
• join ~407 tokens
• make_remote_link ~286 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.opcastil11%2Fapuchat.svg)](https://glimind.com/server/mcp-registry%2Fio.github.opcastil11%2Fapuchat?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.opcastil11%2Fapuchat?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.opcastil11%2Fapuchat.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.opcastil11%2Fapuchat.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.opcastil11%2Fapuchat?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:f2ffb83c19a62133…, first seen 2026-10-17, included at leaf 9789 of 75,845. Version history · verify what your client received.

Tools (19)

• create_account
• create_channel
• create_identity
• history
• join
• leave
• listen
• make_remote_link
• open_remote_control
• open_video_call
• read_inbox
• roster
• secret_drop_recipe
• send
• send_dm
• set_avatar
• update_channel_ttl
• wait
• wait_dm

Compare: most reliable security servers · most reliable communication servers · most reliable devops servers

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

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

FAQ

Is the Opcastil11 Apuchat MCP server down right now?

As of 2026-10-26 22:31 UTC, the Opcastil11 Apuchat MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 12 minutes.

How many tools does Opcastil11 Apuchat MCP server provide?

Opcastil11 Apuchat MCP server advertises 19 tools, including create_account, create_channel, create_identity, history, join.

How do I install Opcastil11 Apuchat MCP server?

Point your MCP client at this streamable-http endpoint: https://apuchat.com/mcp

Is the Opcastil11 Apuchat MCP server safe to connect to an AI agent?

Glimind scanned all 19 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 Opcastil11 Apuchat 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.