Is me.ceki/mcp-server up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.
A stock client connected with no credential and negotiated 2025-11-25. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server says it is | Laravel MCP Server 0.0.1 |
| Answered in | 609 ms |
| Endpoint checked | https://api.ceki.me/mcp/agent |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://api.ceki.me/mcp/agent/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://api.ceki.me with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 52 tools: add-contract-member, book-event, call-human, comment, create-contract-event, create-schedule, create-topup-invoice, delete-correction, delete-event, delete-schedule, get-contract, get-contract-events, get-contract-members, get-crypto-list, get-event, get-event-children, get-event-history, get-hire-jobs, get-my-bookings, get-my-contracts, get-my-events, get-my-jobs, get-owner-connect-link, get-pending-corrections, get-pricing, get-profile, get-schedule, get-schedules, get-user, get-wallet, get-wallet-transactions, get-wallet-usage, list-my-browsers, post-job, propose-correction, regenerate-key, register-agent, remove-contract-member, rent-browser, request-withdrawal, resend-verification, search-browsers, search-specialists, select-currency, timelog-check, timelog-start, timelog-stop, update-profile, update-schedule, upload-file, verify-email, vote-correction.
Its tools changed between 2026-09 and 2026-10:
- Added (1):
delete-event
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | me.ceki/mcp-server |
|---|---|
| Description | Hire specialists by the hour — search, schedule, and pay via MCP protocol. |
| Endpoint | https://api.ceki.me/mcp/agent |
| Publisher repository | https://github.com/Ceki-me/mcp-server |
| Version | 1.0.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt