Is the Ceki MCP server down?

mcp-registry/me.ceki/mcp-server · v0.0.1

Also listed as awesome/ceki-me/mcp-server

healthy
Last checked 2026-10-22 09:39 UTC · handshake 704ms

As of 2026-10-22 09:39 UTC, the Ceki MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 42 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
99.7%
checks observed
4,302
outages (90d)
42
tools
60

Hire specialists by the hour — search, schedule, and pay via MCP protocol.

Install Ceki MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http ceki-mcp-server https://api.ceki.me/mcp/agent

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "ceki-mcp-server": {
      "type": "http",
      "url": "https://api.ceki.me/mcp/agent"
    }
  }
}

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

Agent-readiness: C (72/100)

C (72/100): 0 error(s), 5 warning(s) across 60 tool(s); ~11,990 tokens of tool definitions.
Scores higher than 7% of 15,517 MCP servers Glimind has audited.
Its tool list costs an agent ~11,990 tokens per session — more than 85% of servers.
72 → 72 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints3
Token cost75
Client compatibility70
Protocol100
Reliability85
Stability20

What to fix (6)

60 of 60 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: add-contract-member, book-event, call-human, comment, create-browser-subscription and 55 more

60 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

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

Tools: book-event, create-contract-event, create-schedule, create-topup-invoice, delete-correction and 8 more

Handshake + tools/list takes ~1,712 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.

In the last 30 days: 8 tool(s) removed and 1 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 →

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 →

Auto-fix: 48 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%2Fme.ceki%2Fmcp-server/fixes

add-contract-member 1 change 
{
  "name": "add-contract-member",
  "description": "[Auth Required] Add a user or agent as contract member with role and read/write levels.",
  "inputSchema": {
    "type": "object",
    "required": [
      "contract_id",
      "user_id",
      "role_id"
    ],
    "properties": {
      "read": {
        "type": [
          "integer",
          "null"
        ],
        "maximum": 5,
        "minimum": 0,
        "description": "Read level (0-5)"
      },
      "write": {
        "type": [
          "integer",
          "null"
        ],
        "maximum": 5,
        "minimum": 0,
        "description": "Write level (0-5)"
      },
      "role_id": {
        "type": "integer",
        "maximum": 6,
        "minimum": 1,
        "description": "Role: 1=Owner, 2=Editor, 3=Viewer, 4=Client, 5=Hand, 6=Custom"
      },
      "user_id": {
        "type": "integer",
        "minimum": 1,
        "description": "User or Agent id to add"
      },
      "contract_id": {
        "type": "integer",
        "minimum": 1,
        "description": "Contract ID"
      },
      "participable_type": {
        "type": [
          "string",
          "null"
        ],
        "description": "\"user\" (default) or \"agent\""
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Add Contract Member"
}
book-event 1 change 
{
  "name": "book-event",
  "description": "[Auth Required] Book a time slot with a specialist. Creates a pending event with escrow hold.",
  "inputSchema": {
    "type": "object",
    "required": [
      "kal_schedule_id"
    ],
    "properties": {
      "end": {
        "type": [
          "string",
          "null"
        ],
        "description": "End time (HH:MM)"
      },
      "date": {
        "type": [
          "string",
          "null"
        ],
        "format": "date",
        "description": "Booking date (YYYY-MM-DD)"
      },
      "start": {
        "type": [
          "string",
          "null"
        ],
        "description": "Start time (HH:MM)"
      },
      "description": {
        "type": [
          "string",
          "null"
        ],
        "description": "Booking description / notes"
      },
      "kal_schedule_id": {
        "type": "integer",
        "minimum": 1,
        "description": "Schedule ID to book (from search-specialists results)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Book Event"
}
create-browser-subscription 1 change 
{
  "name": "create-browser-subscription",
  "description": "[Auth Required + Active] Subscribe to a CloudBrowser group so you (or your owner) get rent access to that group's real browsers. Call WITHOUT `group_id` to list available groups and their plans/geo options; each subscription picks a `plan_key` (30days/180days/…) and `geo_key` (ru/de/global). Charged from combined balance (agent wallet → owner balance) when funds suffice, otherwise a crypto invoice is created. Returns the subscription + invoice_id when payable by invoice.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "geo_key": {
        "type": [
          "string",
          "null"
        ],
        "description": "Geo key: ru / de / global (from the group geo options). Required when group_id given."
      },
      "group_id": {
        "type": [
          "integer",
          "null"
        ],
        "minimum": 1,
        "description": "Group ID from the available-groups listing (GET without group_id). Optional — omit to list available groups and options."
      },
      "plan_key": {
        "type": [
          "string",
          "null"
        ],
        "description": "Plan key of the group, e.g. 30days / 180days / 360days. Required when group_id given."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Create Browser Subscription"
}

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/me.ceki/mcp-server"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/me.ceki/mcp-server"}) 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%2Fme.ceki%2Fmcp-server.svg)](https://glimind.com/server/mcp-registry%2Fme.ceki%2Fmcp-server?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fme.ceki%2Fmcp-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fme.ceki%2Fmcp-server.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fme.ceki%2Fmcp-server.svg
   :target: https://glimind.com/server/mcp-registry%2Fme.ceki%2Fmcp-server?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:f460dbb878efbc64…, first seen 2026-10-17, included at leaf 1843 of 45,200. Version history · verify what your client received.

Tools (60)

Compare: most reliable security servers · most reliable calendar servers · most reliable communication servers · most reliable browser servers · most reliable productivity 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 Ceki MCP server down right now?

As of 2026-10-22 09:39 UTC, the Ceki MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 42 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Ceki MCP server provide?

Ceki MCP server advertises 60 tools, including add-contract-member, book-event, call-human, comment, create-browser-subscription.

How do I install Ceki MCP server?

Point your MCP client at this streamable-http endpoint: https://api.ceki.me/mcp/agent

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

Glimind scanned all 60 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 Ceki 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