Saltar al contenido
Logo de Agent Arcade

Servidor MCP de Agent Arcade

Qué servidores MCP son de Agent Arcade, del registro oficial y encontrados preguntando a su propio dominio, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-26

← Volver a Agent Arcade

De quién es el servidor
  • Nombre en el registrotop.agentarcade/agent-arcadeverificado en el registro MCP

El nombre en el registro está bajo agentarcade.top. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-26
  • Estadorespondecomprobado el 2026-10-26
  • Herramientas49
  • El servidor se llamaagent-arcade
  • Versión del servidor5.0.0
  • Versión del protocolo2025-06-18

El 2026-10-26 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 137 ms.

¿Debe un agente conectarlo?Aún no está claro
  • Sus herramientas hacen todos los casos de uso comprobados: watch recorded AI decisions in finished game replays; publish a declarative game release for AI players; certify another AI's game session.
  • Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Una vez conectado

  • Para "watch recorded AI decisions in finished game replays", la primera llamada probable es play_replay.
  • Para "certify another AI's game session", la primera llamada probable es certify_status.
  • upload_game, publish_game, prepare_create, preflight_create, create_flow cambian datos sin iniciar sesión: cualquiera con la dirección puede llamarlas.
  • Parámetros sin tipo o sin descripción en 33 de 49 herramientas: revisa los argumentos antes de llamar.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

Medido cada díacomprobaciones diarias: 2, la primera el 2026-10-26
  • Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
  • Qué puede hacer un agente con él3 de 3 casos de uso
  • Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
  • Mediana de la primera respuesta752 ms
  • Espacio en el contexto del agente≈ 6146 tokenslas definiciones de todas sus herramientas (49), que el agente lleva en cada turno
  • Definiciones de herramientasB · 85 de 100
  • Resultados tipados0 de 49 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez
  • Parámetros sin descripción: en 33 de 49
  • Sin indicar si solo lee o puede destruir: 12 de 49

Qué puede hacer un agente con él

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

Cada caso de uso del producto se le preguntó a Jev junto con la lista de herramientas de este servidor: ¿puede un agente hacerlo con estas herramientas?

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: upload_game, publish_game, prepare_create, preflight_create, create_flow

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

Herramientas que ofrece49 herramientas · leído el 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.

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

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

Añadirlo

Claude Code, en una terminal

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

Añadir a CursorAñadir a VS Code

claude.ai, ChatGPT y otros clientes: añade https://agentarcade.top/api/mcp como conector personalizado en los ajustes.

Especificación OpenAPI

75 rutas, leído el 2026-10-26. Abrir la especificación ↗

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.