Skip to content
Ausca logo

Ausca MCP server

Which MCP servers are Ausca's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to Ausca

Whose server it is
  • Registry namecom.ausca/agent-servicesverified in the MCP registry

The registry name sits under ausca.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Stateanswerschecked 2026-10-24
  • Tools17
  • Server calls itselfausca
  • Server version1.3.1
  • Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 108 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • For "run remote Chromium browser sessions over CDP", the likely first call is ausca_lease_browser.
  • ausca_cancel_invocation change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 17 of 17 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • Use32 npm downloads a week40 GitHub stars
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer153 ms
  • Space in an agent's context≈ 3,780 tokensthe definitions of all its tools (17), which an agent carries on every turn
  • Tool definitionsB · 79 of 100
  • Typed results17 of 17 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a type: in 4 of 17
  • Parameters without a description: in 17 of 17

What an agent can do with it

  • not sure · extract text from scanned documents and page images
  • not sure · turn audio or video into timed text
  • can do · run remote Chromium browser sessions over CDP

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: ausca_cancel_invocation

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers17 tools · read 2026-10-24
  • 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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "agent-services": {
      "type": "http",
      "url": "https://ausca.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http ausca https://ausca.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://ausca.com/mcp as a custom connector in the settings.

Also shipped through: npm

OpenAPI spec

19 paths, read 2026-10-24. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.