Home / MCP registry index / com.ausca/agent-services
Ausca
com.ausca/agent-services in the official MCP registry.
Endpoint https://ausca.com/mcp. Source: github.com/auscahq/ausca.
The registry describes it as: Pay-per-call APIs and MCP services for agents, no accounts or keys, with verifiable receipts.
We read its 17 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ausca_agent_inbox_attachment ausca_agent_inbox_delete ausca_agent_inbox_messages ausca_agent_inbox_read ausca_agent_inbox_status ausca_artifact_access ausca_browser_session_close ausca_browser_session_connect ausca_browser_session_status ausca_cancel_invocation ausca_extend_inbox ausca_get_invocation ausca_get_offer ausca_lease_browser ausca_open_inbox ausca_prepare_invocation ausca_search_offers
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-ausca-agent-services)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.