Ausca MCP Server

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

Local + remotestreamable-httpstdio

What is the Ausca MCP Server?

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

Hosted connection

The registry lists a streamable-http connection at https://ausca.com/mcp.

Packages and local setup

The published npm package is ausca, version 0.1.0. Its declared MCP transport is stdio.

The package declares AUSCA_PRIVATE_KEY: Optional local wallet key for paid tools. Discovery and artifact commit remain keyless.; AUSCA_MAX_PAYMENT_USD: Required positive per-call USD cap whenever AUSCA_PRIVATE_KEY is configured..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.2.6 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
AUSCA_PRIVATE_KEYOptional local wallet key for paid tools. Discovery and artifact commit remain keyless.Optional
AUSCA_MAX_PAYMENT_USDRequired positive per-call USD cap whenever AUSCA_PRIVATE_KEY is configured.Optional