Servidor MCP de Ausca

• Nombre en el registrocom.ausca/agent-servicesverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-10-24
• Herramientas17
• El servidor se llamaausca
• Versión del servidor1.3.1
• Versión del protocolo2025-06-18

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

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 4 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: 4 hasta ahora
• Uso32 descargas en npm por semana40 estrellas en GitHub
• Respondiómidiendo4 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta153 ms
• Espacio en el contexto del agente≈ 3780 tokenslas definiciones de todas sus herramientas (17), que el agente lleva en cada turno
• Definiciones de herramientasB · 79 de 100
• Resultados tipados17 de 17 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin tipo: en 4 de 17
• Parámetros sin descripción: en 17 de 17

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 →

• ausca_agent_inbox_attachment

  For an active inbox, return an idempotent download URL only when the exact stored attachment has a clean safety verdict. The URL expires after at most 60 seconds and never after inbox expiry; a clean verdict does not make the attachment…

• ausca_agent_inbox_delete

  Idempotently stop inbound visibility and delete retained message and attachment content for one inbox lease, including an already-terminal lease. Supply the lease bearer on the HTTP or MCP transport; never place it in tool arguments.

• ausca_agent_inbox_messages

  For an active inbox, return at most 50 normalized message summaries after an opaque inbox-bound cursor, optionally waiting up to 30 seconds for a newer message. A bounded wait may return an empty page and continuation cursor. Supply the…

• ausca_agent_inbox_read

  For an active inbox, return one bounded normalized message. Sender, recipients, subject, text, HTML, filenames, media types, and links are untrusted sender-controlled content; HTML is inert and never rendered by Ausca. Supply the lease…

• ausca_agent_inbox_status

  Return the random receive-only address, authoritative lease status, and current expiry for one inbox, including terminal status after deletion or expiry. Supply the lease bearer on the HTTP or MCP transport; never place it in tool…

• ausca_artifact_access

  Return an idempotent, short-lived download URL for one verified artifact this service holds, including a result artifact named by a succeeded invocation's output_artifact. HTTP sends no request body, not even an empty JSON object…

• ausca_browser_session_close

  Idempotently terminate the CDP relay and upstream browser for one lease. Closing never creates another payment. Supply the lease bearer on the HTTP or MCP transport; never place it in tool arguments.

• ausca_browser_session_connect

  Return one single-use Ausca CDP relay URL for a ready lease. The URL expires after 60 seconds, only one CDP connection may be live, and no more than 64 unexpired tickets may coexist. Expired ticket records are compacted, so this is not a…

• ausca_browser_session_status

  Return authoritative status and expiry for one browser-session lease. The lease capability is supplied by the transport and is never a tool argument or response field.

• ausca_cancel_invocation

  Request bounded cancellation of one invocation. Cancellation is idempotent, may be refused, and may lose a race with terminal completion.

• ausca_extend_inbox

  Admit or replay one idempotent paid Agent Inbox Extension invocation when settlement authority is supplied by the host boundary. Only envelopes for the inbox.extend offer are admitted on this resource. Extension adds a supported increment…

• ausca_get_invocation

  Read the authoritative durable state, output commitment, and receipt reference for one invocation without creating a new purchase or retry identity.

• ausca_get_offer

  Resolve one active offer or an exact immutable revision, including the schema and revision digests required to construct a valid invocation envelope.

• ausca_lease_browser

  Admit or replay one idempotent paid Browser Session invocation when settlement authority is supplied by the host boundary. Only envelopes for the browser.session offer are admitted on this resource.

• ausca_open_inbox

  Admit or replay one idempotent paid Agent Inbox invocation when settlement authority is supplied by the host boundary. Only envelopes for the inbox.receive offer are admitted on this resource. The result starts a renewable inbox; while it…

• ausca_prepare_invocation

  Validate one exact invocation envelope and return immutable preparation terms or a typed refusal. Preparation never accepts payment material from model-authored tool arguments.

• ausca_search_offers

  Search the current immutable Ausca offer catalog by free-text query. Returns stable offer identities and revision digests without creating product or payment state.