Servidor MCP de AIApply

• Direcciónhttps://aiapply.co/mcpno está en el registro oficial: respondió al preguntarle

Ninguna entrada del registro oficial de MCP nombra este servidor. Respondió en aiapply.co cuando el Atlas preguntó en la dirección donde suelen montarse los servidores, así que es del propio proveedor. Los clientes y catálogos que listan servidores a partir del registro no lo muestran.

• Estadorespondecomprobado el 2026-10-26
• Herramientas14
• El servidor se llamaAIApply
• Versión del servidor1.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 279 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

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.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta336 ms
• Espacio en el contexto del agente≈ 3198 tokenslas definiciones de todas sus herramientas (14), que el agente lleva en cada turno
• Definiciones de herramientasA · 99 de 100
• Resultados tipados14 de 14 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 1 de 14

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 →

• search_jobs

  Use this when the user wants current AIApply job listings filtered by role, skills, remote status, or country. Works without an AIApply account: the role is then required, since there is no saved keyword to fall back on. For a signed-in…

• list_review_jobs

  Use this when the connected user wants applications currently waiting for review. Return only job facts and opaque IDs; never submit or change an application. Needs an AIApply account: if the user has not signed in, calling it asks them…

• list_applications

  Use this when the connected user wants recent AIApply application and preparation status. Return role, company, status, match score, timestamp, and canonical listing link without exposing resumes or contact details. Needs an AIApply…

• preview_application

  Use this when the connected user asks what AIApply prepared for one specific application, identified by the job_id returned from list_applications or list_review_jobs. Read the cover letter AIApply wrote, unless it was withheld. This…

• get_auto_apply_preferences

  Use this when the connected user asks about current AIApply job preferences or before suggesting a change. Read target roles, locations, work types, experience, salary, exclusions, daily limit, and application mode without modifying them…

• open_auto_apply_preferences

  Use this when the connected user asks to change their AIApply job preferences — target roles, locations, work types, experience, salary, excluded companies, the daily limit, or how applications are submitted. Nothing here can change them…

• list_unread_mail

  Use this when the connected user asks whether anything new has arrived in their AIApply mailbox, or before telling them about interview invites. Returns unread messages as sender and subject only, with a link to the mailbox. It cannot…

• apply_to_job

  Use this when the connected user wants AIApply to apply to a job they picked from search_jobs. AIApply adds it to their queue already approved, so it does not wait for anyone: it will be applied for and that spends a credit. This is the…

• submit_application

  Use this only when the connected user has asked for one specific job from their review queue to be applied for, identified by the job_id from list_review_jobs. Approving it spends one application credit and cannot be undone: AIApply…

• pause_resume_applications

  Use this when the connected user asks to stop or restart AIApply applying for them. action="pause" stops all automatic applying and is destructive: call it without confirmed, show the user what will stop, ask them, then call again with…

• get_credits_summary

  Use this before queuing or sending work to check the connected user can still pay for it, or when they ask how many applications they have left. Reports the credit balance, whether auto-apply is active, the plan slug and the configured…

• get_setup_status

  Use this when the connected user wants AIApply to apply for them, and again whenever they come back to it: it says what is still missing — their resume, their confirmed job preferences, a plan that includes applying — and next_step names…

• add_resume

  Use this when get_setup_status says next_step is add_resume. Pass exactly one of: resume, the file the user attached, if you can attach files to tool calls; or resume_text, the content of their CV as you can read it, or the work history…

• save_auto_apply_setup

  Use this once the user has seen and confirmed the job titles, location, work mode, job type and experience level AIApply needs: call it with confirmed=true and the values they confirmed, without asking them again. Without confirmed it…