# Ausca (remote · ausca.com)

Pay-per-call APIs and MCP services for agents, no accounts or keys, with verifiable receipts.

- Trust score: 72/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `ausca.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-ausca-agent-services/ausca.md), [page](https://verifymcp.io/servers/com-ausca-agent-services/ausca)
- npm · `ausca`: 39/100, [markdown](https://verifymcp.io/servers/com-ausca-agent-services/ausca-2.md), [page](https://verifymcp.io/servers/com-ausca-agent-services/ausca-2)

## Channel facts

- Endpoint: `https://ausca.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (ausca_agent_inbox_delete).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1060 tokens (~75/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability check failed: schema churn in the 21 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 9 additions.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Ausca MCP server?

Ausca is a hosted endpoint at https://ausca.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-ausca-agent-services 'https://ausca.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-ausca-agent-services": {
      "url": "https://ausca.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-ausca-agent-services]
url = "https://ausca.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-ausca-agent-services": {
      "type": "remote",
      "url": "https://ausca.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-ausca-agent-services --url 'https://ausca.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-ausca-agent-services:
    url: "https://ausca.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-ausca-agent-services": {
      "Transport": "http",
      "Url": "https://ausca.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-ausca-agent-services -t streamable-http -u 'https://ausca.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60.

### 2026-09-18 (score 71, −1)

- [security regression] Stability: 0.60 → fail
- [functional regression] “ausca_prepare_invocation” dropped the required parameter “canonicalizer_version”
- [functional] Server version: 1.2.1 → 1.3.0

### 2026-09-17 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 67, +1)

- [security] Tool “ausca_browser_session_connect” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 965 → 1067
- [functional] Server version: 1.2.0 → 1.2.1
- [functional] New tool “ausca_artifact_access”

## MCP tools (14)

### `ausca_agent_inbox_attachment` (~106 tokens)

Mint clean attachment access

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 content trusted. Supply the lease bearer on the HTTP or MCP transport; never place it in tool arguments.

Input parameters:

- `attachment_id` (required)
- `idempotency_key` (required)
- `inbox_id` (required)
- `message_id` (required)

Output parameters:

- `attachment`
- `status`

### `ausca_agent_inbox_delete` (~60 tokens)

Delete an agent-inbox lease

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.

Input parameters:

- `inbox_id` (required)

Output parameters:

- `inbox`
- `status` (string)

### `ausca_agent_inbox_messages` (~91 tokens)

Wait for or list inbound 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 lease bearer on the HTTP or MCP transport; never place it in tool arguments.

Input parameters:

- `after`
- `inbox_id` (required)
- `wait_seconds`

Output parameters:

- `cursor`
- `messages` (array)
- `status`

### `ausca_agent_inbox_read` (~87 tokens)

Read one inbound message

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 bearer on the HTTP or MCP transport; never place it in tool arguments.

Input parameters:

- `inbox_id` (required)
- `message_id` (required)

Output parameters:

- `message`
- `status`

### `ausca_agent_inbox_status` (~62 tokens)

Read agent-inbox lease 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 arguments.

Input parameters:

- `inbox_id` (required)

Output parameters:

- `inbox`
- `status`

### `ausca_artifact_access` (~85 tokens)

Mint artifact download 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. The URL expires after at most 60 seconds. The immutable artifact reference is the only authority; verify downloaded bytes against the returned content digest.

Input parameters:

- `artifact_ref` (required)
- `idempotency_key` (required)

Output parameters:

- `artifact`
- `status`

### `ausca_browser_session_close` (~56 tokens)

Close a browser-session lease

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.

Input parameters:

- `session_id` (required)

Output parameters:

- `session`
- `status` (string)

### `ausca_browser_session_connect` (~114 tokens)

Mint a browser CDP connection

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 lifetime reconnect quota. Supply the lease bearer on the HTTP or MCP transport; never place it in tool arguments. The upstream provider URL and credential are never disclosed.

Input parameters:

- `idempotency_key` (required)
- `session_id` (required)

Output parameters:

- `connection`
- `status`

### `ausca_browser_session_status` (~46 tokens)

Read browser-session lease 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.

Input parameters:

- `session_id` (required)

Output parameters:

- `session`
- `status`

### `ausca_cancel_invocation` (~43 tokens)

Request bounded cancellation

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

Input parameters:

- `invocation_id` (required)

### `ausca_get_invocation` (~41 tokens)

Read authoritative invocation state

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

Input parameters:

- `invocation_id` (required)

### `ausca_get_offer` (~47 tokens)

Resolve an active or pinned offer revision

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

Input parameters:

- `offer_id` (required)
- `revision_digest`

Output parameters:

- `offer`
- `status`

### `ausca_prepare_invocation` (~92 tokens)

Validate invocation input and return binding terms

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

Input parameters:

- `idempotency_key` (string, required)
- `input` (required)
- `input_schema_digest` (required)
- `offer_id` (required)
- `offer_revision` (required)
- `offer_revision_digest` (required)
- `output_schema_digest` (required)
- `parent_binding`

### `ausca_search_offers` (~54 tokens)

Search immutable 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.

Input parameters:

- `cursor`
- `limit`
- `q`

Output parameters:

- `next_cursor`
- `offers` (array)
- `status`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-ausca-agent-services/ausca#diagnostics

## Score history

- 2026-09-20: 72
- 2026-09-19: 71
- 2026-09-18: 71
- 2026-09-17: 72
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 68
- 2026-09-09: 68
- 2026-09-08: 67
- 2026-09-07: 67
- 2026-09-06: 66
- 2026-09-05: 66
- 2026-09-04: 66
- 2026-09-03: 65
- 2026-09-02: 63
- 2026-09-01: 64
- 2026-08-31: 63
- 2026-08-30: 63

## Common questions

### What is the Ausca MCP server?

Ausca is an MCP server listed in the public MCP registry as com.ausca/agent-services. Pay-per-call APIs and MCP services for agents, no accounts or keys, with verifiable receipts. This page covers its hosted endpoint (https://ausca.com/mcp).

### Is the Ausca MCP server safe to use?

Ausca scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Ausca MCP server expose?

Ausca exposes 14 tools: ausca_agent_inbox_attachment, ausca_agent_inbox_delete, ausca_agent_inbox_messages, ausca_agent_inbox_read, ausca_agent_inbox_status, and 9 more. Their descriptions and schemas cost roughly 984 tokens of context every time the server is loaded.

### Does the Ausca MCP server require authentication?

No. We connected to Ausca without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Ausca MCP server still maintained?

Ausca is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://ausca.com/mcp
- Repository: https://github.com/auscahq/ausca
- Website: https://ausca.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-ausca-agent-services/ausca.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ausca-agent-services/ausca.json
- HTML version of this page: https://verifymcp.io/servers/com-ausca-agent-services/ausca