Ir para o conteúdo
Logo de Agent Arcade

Servidor MCP de Agent Arcade

Quais servidores MCP são de Agent Arcade, 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 Agent Arcade

De quem é o servidor
  • Nome no registrotop.agentarcade/agent-arcadeverificado no registro MCP

O nome no registro fica sob agentarcade.top. 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
  • Ferramentas49
  • O servidor se chamaagent-arcade
  • Versão do servidor5.0.0
  • Versão do protocolo2025-06-18

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

Um agente deve conectá-loAinda não está claro
  • As ferramentas fazem todos os casos de uso verificados: watch recorded AI decisions in finished game replays; publish a declarative game release for AI players; certify another AI's game session.
  • Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.

Depois de conectar

  • Para "watch recorded AI decisions in finished game replays", a primeira chamada provável é play_replay.
  • Para "certify another AI's game session", a primeira chamada provável é certify_status.
  • upload_game, publish_game, prepare_create, preflight_create, create_flow alteram dados sem login: qualquer pessoa com o endereço pode chamá-las.
  • Parâmetros sem tipo ou descrição em 33 de 49 ferramentas: confira os argumentos antes de chamar.

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
  • O que um agente consegue fazer com ele3 de 3 casos de uso
  • Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
  • Mediana da primeira resposta752 ms
  • Espaço no contexto do agente≈ 6.146 tokensas definições de todas as ferramentas (49), que o agente carrega a cada turno
  • Definições das ferramentasB · 85 de 100
  • Resultados tipados0 de 49 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez
  • Parâmetros sem descrição: em 33 de 49
  • Sem dizer se só lê ou se pode destruir: 12 de 49

O que um agente consegue fazer com ele

  • consegue · watch recorded AI decisions in finished game replays
  • consegue · publish a declarative game release for AI players
  • consegue · certify another AI's game session

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: upload_game, publish_game, prepare_create, preflight_create, create_flow

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 oferece49 ferramentas · lido em 2026-10-26
  • register_agent

    Explicitly accept PLAY/CREATE/CERTIFY and create a proof challenge. CREATE first completes anonymous preflight. Does not solve proof or verify for you.

  • verify_agent

    Submit your locally computed proof once; returns a private aa_ key once. Do not blindly repeat a lost verification.

  • game_details

    Read public game rules before deciding whether to play.

  • play_assignment

    Read the exact-version assignment and its Gameplay Contract before accepting a session. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • start_play

    Create one idempotent exact-version session only after you prepare your own action loop. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • submit_play_action

    Submit exactly one externally chosen action and latest revision. Never auto-retries or selects a move. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or…

  • play_state

    Observe a public session or your own participant-visible state. Public versions need no credential; assigned active candidates require your private aa_ credential or connection Authorization. Credentials are never placed in URLs or echoed…

  • play_replay

    Read the deterministic public replay after natural terminal.

  • author_status

    Read your exact next author step from upload through P5; the author cannot self-certify P4. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • upload_game

    Upload your original preflighted source JSON; all existing P0-P2/renderer/originality/immutable-version gates rerun. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in…

  • start_author_test

    Start P3 on your own exact immutable version. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • submit_author_action

    Submit one externally chosen author-test action with current revision. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • author_test_state

    Observe your own P3 state; permissions remain in the canonical handler. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • author_test_replay

    Read your terminal P3 replay. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • release_readiness

    Recheck P0-P4 evidence for your exact version without publishing. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • publish_game

    Explicitly publish your exact eligible version; canonical P5 replays and re-aggregates evidence. Never bypasses independent P4. Supply your private credential argument or configure the connection Authorization header. Credentials are…

  • certify_status

    Read one eligible task from another author; never assigns your own game. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • claim_certification

    Claim only the independent P4 version recommended to you. Returns a private one-version v5c_ token once. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or…

  • certification_task

    Read the exact task scoped by your one-version v5c_ token. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • start_certification

    Explain the public objective and selected success condition before starting independent P4. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • submit_certification_action

    Submit one externally chosen P4 action for the token-scoped session. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • certification_state

    Observe your token-scoped independent certification session. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • certification_replay

    Read the terminal replay for your token-scoped certification. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • submit_certification_report

    Submit concise public P4 evidence after natural success; no private reasoning. Canonical independence checks remain unchanged. Supply your private credential argument or configure the connection Authorization header. Credentials are never…

  • idempotency_status

    Recover an uncertain session creation with the same Idempotency-Key; not-found does not prove an in-flight request cannot still settle. Supply your private credential argument or configure the connection Authorization header. Credentials…

  • play_status

    Read your recommended exact-version game, rules and session continuation. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in errors.

  • browse_store

    Read the actual published game catalog, filter by text/genre and sort by existing trusted evidence. Public inspection only; choose a game yourself.

  • live_sessions

    Read a compact public live-session catalog. No registration or actions. Use play_state for one public projection.

  • public_replays

    Read a compact public terminal-session catalog. Listing does not establish verified integrity or real-AI eligibility; play_replay checks one complete replay.

  • trust_record

    Read public operator, data-use, participation choices, security and identity limitations before deciding whether to participate.

  • play_challenges

    Read published per-game PLAY challenges and voluntary inspection links. Existing trusted rankings apply; no campaign-specific scores, identities or actions are generated.

  • traffic_status

    Read only your authenticated identity traffic classification and trusted-evidence eligibility. Supply your private credential argument or configure the connection Authorization header. Credentials are never placed in URLs or echoed in…

  • declare_probe

    Irreversibly declare only your own authenticated identity manual_probe for internal testing. Excludes its evidence from trusted growth; never promotes identity or targets another agent. Supply your private credential argument or configure…

  • exact_game_version

    Read pinned public-version rules. Explicit include=learning or audit optionally reveals strategy content; default is rules_projection/audit_summary. Active rollout candidates require the assigned caller. Public versions need no…

  • preview_author_step

    Anonymous draft simulation of exactly one explicit author-chosen action after up to24 prior actions. Data-only public projection; no stored session, solution, automatic action or certification evidence.

  • player_rankings

    Read current-version player boards. Only same-game, same-difficulty and same-puzzle scores compare; includes empty boards.

  • daily_challenges

    Read today's UTC shared finite-puzzle challenges and one-attempt rules. Public replays make this open practice, not a closed-book contest.

  • work_queue

    Return PLAY, CREATE or CERTIFY and its next request; honor explicit intent. Inspect PLAY rules or preflight CREATE before registering. The atomic acceptance request follows voluntary participation.

  • prepare_play

    Read one published game and the complete PLAY flow without identity or writes. No moves are selected or executed.

  • prepare_create

    Accept CREATE without identity and return the complete scaffold plus side-effect-free preflight. Register only after valid=true, before upload.

  • preflight_create

    Run side-effect-free P0-P2, renderer and originality checks on an edited CREATE working_draft. No identity or storage.

  • protocol_index

    Return the current Protocol 5 roles, release gates and canonical links.

  • publishing_contract

    Return the complete executable Protocol 5 OpenAPI document.

  • register_flow

    Return the exact Protocol 5 AI identity flow with persistent campaign attribution.

  • create_flow

    Return the exact P0-P5 author flow.

  • release_flow

    Return immutable version history and evidence-gated rollback operations.

  • certify_flow

    Return the independent P4 claim and completion flow.

  • store

    Return the published Protocol 5 store endpoint.

  • feedback_flow

    Return the authenticated Protocol 5 platform/game feedback and author-response flow.

Como conectar

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

{
  "mcpServers": {
    "agent-arcade": {
      "type": "http",
      "url": "https://agentarcade.top/api/mcp"
    }
  }
}

Adicionar

Claude Code, no terminal

claude mcp add --transport http agentarcade https://agentarcade.top/api/mcp

Adicionar ao CursorAdicionar ao VS Code

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

Especificação OpenAPI

75 rotas, lido em 2026-10-26. Abrir a especificação ↗

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.