me.ceki/mcp-server
REMOTE · API.CEKI.ME · SCANNED SEP 22
Hire specialists by the hour — search, schedule, and pay via MCP protocol.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 52 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 5450 tokens (~100/item across 54 items; 52 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete-schedule" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 54 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the me.ceki/mcp-server server?
me.ceki/mcp-server is a hosted endpoint at https://api.ceki.me/mcp/agent, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.ceki.me
claude mcp add --transport http me-ceki-mcp-server 'https://api.ceki.me/mcp/agent'
{
"mcpServers": {
"me-ceki-mcp-server": {
"url": "https://api.ceki.me/mcp/agent"
}
}
} {
"servers": {
"me-ceki-mcp-server": {
"type": "http",
"url": "https://api.ceki.me/mcp/agent"
}
}
} [mcp_servers.me-ceki-mcp-server] url = "https://api.ceki.me/mcp/agent"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"me-ceki-mcp-server": {
"type": "remote",
"url": "https://api.ceki.me/mcp/agent",
"enabled": true
}
}
} openclaw mcp add me-ceki-mcp-server --url 'https://api.ceki.me/mcp/agent' --transport streamable-http
mcp_servers:
me-ceki-mcp-server:
url: "https://api.ceki.me/mcp/agent" {
"McpServers": {
"me-ceki-mcp-server": {
"Transport": "http",
"Url": "https://api.ceki.me/mcp/agent"
}
}
} assistant mcp add me-ceki-mcp-server -t streamable-http -u 'https://api.ceki.me/mcp/agent'
{
"mcpServers": {
"me-ceki-mcp-server": {
"type": "http",
"url": "https://api.ceki.me/mcp/agent"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 52 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- New tool “delete-event” functional
- 19 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Sept 26 0
- Schema quality: fail → pass ▲ functional
- New tool “delete-correction” functional
- 1 Sept 26 +33
- Injection markers: unverified → pass ▲ security
- Stability: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 50 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: pass → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: fair → good functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 31 Aug 26 −33
- Tool safety: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: fail → pass ▲ functional
- Schema quality: good → fair functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://api.ceki.me/mcp/agent
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ceki.me | CN=WE1,O=Google Trust Services,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 32e4bf1ed111b71213169efcd8b97d6c |
| SANs: ceki.me, *.ceki.me | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.ceki.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| ceki.me. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.ceki.me/mcp/agent | Verified | 200 | |
| http (plaintext) | http://api.ceki.me/mcp/agent | HTTPS enforced | 301 | https://api.ceki.me/mcp/agent |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
verify-email Verify Email ~58
[Public] Mandatory: confirm email with the 6-digit code to activate the agent (or transition to pending_deposit if balance < required).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 6-digit verification code |
| string | yes | Agent email |
No output schema declared.
No examples provided.
vote-correction Vote Correction ~65
[Auth Required] Vote (approve/reject) on one or more proposed corrections of an event.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | yes | Event ID |
| ids | array | yes | Correction IDs to vote on |
| vote | boolean | yes | true=approve, false=reject |
No output schema declared.
No examples provided.
What is the me.ceki/mcp-server server?
me.ceki/mcp-server is listed in the public MCP registry as me.ceki/mcp-server. Hire specialists by the hour, search, schedule, and pay via MCP protocol. This page covers its hosted endpoint (https://api.ceki.me/mcp/agent).
Is the me.ceki/mcp-server server safe to use?
me.ceki/mcp-server scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the me.ceki/mcp-server server expose?
me.ceki/mcp-server exposes 52 tools: register-agent, verify-email, resend-verification, regenerate-key, search-specialists, and 47 more. Their descriptions and schemas cost roughly 5,390 tokens of context every time the server is loaded.
Does the me.ceki/mcp-server server require authentication?
No. We connected to me.ceki/mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the me.ceki/mcp-server server still maintained?
me.ceki/mcp-server is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.