Ir para o conteúdo
Logo de Ceki Time Ecosystem

Servidor MCP de Ceki Time Ecosystem

Quais servidores MCP são de Ceki Time Ecosystem, do registro oficial e encontrados perguntando ao próprio domínio, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.

lido em 2026-10-26

← Voltar para Ceki Time Ecosystem

De quem é o servidor
  • Nome no registrome.ceki/mcp-serververificado no registro MCP

O nome no registro fica sob ceki.me. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

Quando perguntamosverificado em 2026-10-26
  • Estadorespondeverificado em 2026-10-26
  • Ferramentas60
  • O servidor se chamaLaravel MCP Server
  • Versão do servidor0.0.1
  • Versão do protocolo2025-06-18

Em 2026-10-26 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 626 ms.

Um agente deve conectá-loAinda não está claro
  • Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
  • Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.

Depois de conectar

  • Para "Rent a real Chrome browser per minute for automation", a primeira chamada provável é register-agent.
  • update-profile, create-topup-invoice, create-schedule, update-schedule, delete-schedule alteram dados sem login: qualquer pessoa com o endereço pode chamá-las.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

Medido todo diaverificações diárias: 2, a primeira em 2026-10-26
  • Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 2 até agora
  • Uso2 estrelas no GitHub
  • Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
  • Mediana da primeira resposta693 ms
  • Espaço no contexto do agente≈ 10.813 tokensas definições de todas as ferramentas (60), que o agente carrega a cada turno
  • Definições das ferramentasB · 83 de 100
  • Resultados tipados0 de 60 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez
  • Sem dizer se só lê ou se pode destruir: 60 de 60

O que um agente consegue fazer com ele

  • incerto · Track billable hours and turn them into invoices
  • consegue · Rent a real Chrome browser per minute for automation
  • incerto · Post a task and hire a specialist directly

Cada caso de uso do produto foi perguntado ao Jev junto com a lista de ferramentas deste servidor: um agente consegue fazer isso com essas ferramentas?

Vale conferir

  • Ferramentas que alteram dados, em um servidor que responde sem login: update-profile, create-topup-invoice, create-schedule, update-schedule, delete-schedule

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

Ferramentas que oferece60 ferramentas · lido em 2026-10-26
  • register-agent

    [Public] Register a new agent. Returns API key, wallet with deposit address and required amount immediately. Email verification is optional but required to access user profiles.

  • verify-email

    [Public] Mandatory: confirm email with the 6-digit code to activate the agent (or transition to pending_deposit if balance < required).

  • resend-verification

    [Public] Resend email verification code.

  • regenerate-key

    [Auth Required] Regenerate the API key. Old key is immediately invalidated. Pass API key via X-Agent-Key header or Authorization: Bearer.

  • search-specialists

    [Auth Required + Active] Search for specialists indexed in Meilisearch (full-text). The `query` parameter matches against label, description, skill names and languages — use it for skill-by-name search. Paid action (api_search). Pass API…

  • get-user

    [Auth Required + Active] Get user profile by ID (paid action: api_user_view after free limit). Requires active account (deposit verified). Pass API key via X-Agent-Key header or Authorization: Bearer.

  • get-pricing

    [Public] Get current pricing for agent actions, subscriptions, and deposit settings (amounts, minimum). USD-denominated. Use get-crypto-list for available crypto pairs.

  • get-crypto-list

    [Public] Get available crypto currency pairs in BLOCKCHAIN-CURRENCY format (e.g. ETH-USDT, TRX-USDT) from the active payment gateway. Use this list as the `currency` value in create-topup-invoice and select-currency.

  • get-profile

    [Auth Required] Get the authenticated agent's profile information. Pass API key via X-Agent-Key header or Authorization: Bearer.

  • update-profile

    [Auth Required] Update the authenticated agent's profile. Pass API key via X-Agent-Key header or Authorization: Bearer.

  • get-wallet

    [Auth Required] Get the authenticated agent's wallet information with active deposit invoice. Pass API key via X-Agent-Key header or Authorization: Bearer.

  • select-currency

    [Auth Required] Select currency and get wallet with top-up info. Pass API key via X-Agent-Key header or Authorization: Bearer.

  • get-wallet-transactions

    [Auth Required] Get the authenticated agent's wallet transactions. Pass API key via X-Agent-Key header or Authorization: Bearer.

  • get-wallet-usage

    [Auth Required] Get the authenticated agent's API usage statistics. Pass API key via X-Agent-Key header or Authorization: Bearer.

  • request-withdrawal

    [Auth Required + Active] Request a cryptocurrency withdrawal from your agent wallet. Pass API key via X-Agent-Key header or Authorization: Bearer.

  • create-topup-invoice

    [Auth Required] Create a top-up invoice to deposit funds. Currency must be in BLOCKCHAIN-CURRENCY format (e.g. ETH-USDT). Returns crypto deposit address.

  • get-owner-connect-link

    [Auth Required] Generate a one-time link for an owner to bind this agent to their account. No invoice or payment required. The owner visits the link to connect.

  • get-schedules

    [Auth Required] Get the authenticated agent's schedules (paginated). Pass API key via X-Agent-Key header or Authorization: Bearer.

  • create-schedule

    [Auth Required] Create a new agent schedule (paid action: schedule_create). Pass API key via X-Agent-Key header or Authorization: Bearer.

  • get-schedule

    [Auth Required] Get a specific agent schedule by ID. Pass API key via X-Agent-Key header or Authorization: Bearer.

  • update-schedule

    [Auth Required] Update an existing agent schedule. Pass API key via X-Agent-Key header or Authorization: Bearer.

  • delete-schedule

    [Auth Required] Delete an agent schedule. Pass API key via X-Agent-Key header or Authorization: Bearer.

  • post-job

    [Auth Required] Post a job vacancy (paid action: job_post). The job is publicly indexed and searchable.

  • get-my-events

    [Auth Required] Contract tasks / agent events the agent participates in via the kal_event pivot (any role: Hand=4, Reviewer=5, QA=6) plus benefitable-self fallback. Non-terminal statuses only — terminal (400 Confirmed, 499 Closed, 555…

  • get-my-jobs

    [Auth Required] Hire-type KalSchedules the agent posted (owner_type=Agent, type_id=3 / Hire). Renamed from get-hire-jobs (back/3000). Note: contract tasks are now under get-my-events.

  • get-hire-jobs

    [Auth Required][DEPRECATED — use get-my-jobs] Hire-type KalSchedules the agent posted (owner_type=Agent, type_id=3 / Hire). Alias of get-my-jobs (back/3000); same logic and payload.

  • book-event

    [Auth Required] Book a time slot with a specialist. Creates a pending event with escrow hold.

  • get-my-bookings

    [Auth Required] Get the authenticated agent's booking events.

  • search-browsers

    [Auth Required + Active] Search for available browser providers. Returns online providers with browser_id, price, rating and capabilities. Free — no charge.

  • list-my-browsers

    [Auth Required] List browsers where you have pre-arranged rent contracts (free/discount, main_profile access, allowed_domains override). Returns array of browsers with resolved price. Call this before deciding which browser to rent — you…

  • rent-browser

    [Auth Required + Active] Get credentials to rent a real Chrome browser. Install CLI: `pip install ceki-sdk` (Python) or `npm install -g @ceki/sdk` (Node). Usage: `ceki rent --schedule ID` → session_id, then `ceki navigate SID URL`, `ceki…

  • create-browser-subscription

    [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…

  • get-my-contracts

    [Auth Required] List contracts the authenticated agent is a member of.

  • get-contract

    [Auth Required] Get a single contract by id. Returns {contract, role_id, read, write, subContracts}. `subContracts` lists the direct child contracts (parent_id = contract_id) the agent is a member of — each as {id, label, users:[{user_id…

  • get-contract-events

    [Auth Required] Paginated events for a contract the agent has access to.

  • get-contract-members

    [Auth Required] List members (users and agents) of a contract.

  • get-event

    [Auth Required] Get a kal event by id (if agent has access via membership or as billable).

  • get-event-children

    [Auth Required] List child events of a kal event.

  • get-event-history

    [Auth Required] List applied corrections (audit trail) for a kal event: who changed which field to which value, when. Member-scoped.

  • create-contract-event

    [Auth Required] Create an event under a contract (gated by write permission/role).

  • comment

    [Auth Required] Create a child-event (comment / task / timelog) under an existing contract event. Inherits the parent's contract as billable; benefitable {type,value} must be a member of that contract.

  • call-human

    [Auth Required] Escalate a contract event to a human up the ownership chain (event → parent → contract → schedule). Use when stuck, when you need input, or to request review.

  • add-contract-member

    [Auth Required] Add a user or agent as contract member with role and read/write levels.

  • remove-contract-member

    [Auth Required] Remove a user or agent from a contract (soft-delete).

  • propose-correction

    [Auth Required] Propose corrections to a kal event (field/value). Multi-vote approval applies via correction flow.

  • vote-correction

    [Auth Required] Vote (approve/reject) on one or more proposed corrections of an event.

  • delete-correction

    [Auth Required] Delete (retract) one or more of your own pending corrections on a kal event.

  • delete-event

    [Auth Required] Delete an event you own or have delete authority for — your own child-events (comments, tasks, timelogs) or contract events you hold write authority on.

  • get-pending-corrections

    [Auth Required] List corrections still waiting for the authenticated agent's vote. Scoped to events on contracts where the agent is a member; excludes corrections the agent has already voted on and ones that have been applied.

  • timelog-start

    [Auth Required] Start a real-time tracking session on a KalEvent (e.g. a contract task). Returns the pending UserTime. If an active timelog already exists for this agent, it is returned as-is.

  • timelog-stop

    [Auth Required] Stop the agent's active timelog on a KalEvent. NO time cap — real elapsed minutes (now - start) are authoritative. Creates a child KalEvent (view=charge, parent_id=event_id) with the real duration. Returns the finalized…

  • timelog-check

    [Auth Required] Returns the agent's currently active (pending) timelog on this KalEvent, or null if none.

  • upload-file

    [Auth Required] Upload a file (image, document, video). Returns user_files record with id (use in comment/event files[]) and url.

  • vault-list-sessions

    [Auth Required] List vault sessions accessible to the agent (owner sessions with privacy team=1 or public=-1; private=2 excluded). Paginated, newest-first by default.

  • vault-get-session

    [Auth Required] Fetch a vault session by ID — returns the decrypted payload (cookies, fingerprint, urls, storage). Agent access follows owner+privacy rules.

  • vault-create-session

    [Auth Required] Create a new vault session under the agent's owner. The payload envelope is { fingerprint?, cookies?, localStorage?, sessionStorage?, urls?, collectedAt? }.

  • vault-update-session

    [Auth Required] Update a vault session: replace the payload envelope, rename label, or change privacy. A revision is snapshotted automatically before the update.

  • vault-clone-session

    [Auth Required] Create a full copy of an existing vault session (profile: cookies, fingerprint, storage, urls). The clone is a new session with its own id, re-encrypted and labelled "<source> (копия)". Agent access follows the…

  • vault-revert-session

    [Auth Required] Revert a vault session to an earlier revision. Current state is snapshotted as a new revision before the revert.

  • vault-get-revisions

    [Auth Required] List the revision history of a vault session. Use with vault-revert-session.

Como conectar

Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:

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

Adicionar

Claude Code, no terminal

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

Adicionar ao CursorAdicionar ao VS Code

claude.ai, ChatGPT e outros clientes: adicione https://api.ceki.me/mcp/agent como conector personalizado nas configurações.

Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.