Autonomy — canonical service discovery

io.github.SleepyJPPublished by GitHub account SleepyJPv2.0.0Updated Oct 25, 2026

Read-only Autonomy capability, schema, status and pricing discovery. Paid execution remains paused.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingFinance

Overview

AI-generated overview

A read-only remote MCP server for discovering Autonomy service capabilities, schemas, status and pricing readiness; paid execution stays paused.

What you can do
List canonical Autonomy service capabilities with availability, schemas and price readiness, and check registry version and commercial status. Search for capabilities such as blockchain state, balances or token data, with unknown networks or unverified budgets returning no matches. Inspect a single service by ID, including status, input/output schema and payment readiness. All discovery is read-only; payment and execution remain safety-paused, and catalog entries may be marked LEGACY or BLOCKED rather than sellable.
When to use it
Use it when an assistant needs to find out which Autonomy services exist, what inputs and outputs they expect, and whether they are available or priced, before deciding how to proceed. It suits read-only reconnaissance of the catalog rather than actually buying or running services.
Requirements
A remote streamable HTTP endpoint at the provider's API host; no packages, environment variables or headers are declared. Network access to the endpoint is needed. No authentication is declared.
Before you install
The catalog is informational only: payment and execution are paused, so nothing here can be purchased or run. Entries may be LEGACY or BLOCKED and are not sellable, and registry status does not reflect upstream provider health. Treat availability and pricing fields as readiness signals, not guarantees.

Installation

In SourceWeft

  1. Open Autonomy — canonical service discovery in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.SleepyJP%2Fautonomy-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "autonomy-canonical-service-discovery": {
      "type": "http",
      "url": "https://api.theautonomy.ai/mcp"
    }
  }
}

Tools

4

autonomy_services

List canonical Autonomy service capabilities, actual availability, schemas and price readiness. Read-only canonical Autonomy discovery. Payment and execution remain safety-paused; catalog entries can be LEGACY or BLOCKED, not sellable.

Takes no parameters.

autonomy_discover

Find capabilities when an agent needs blockchain state, balances, token data or other cataloged infrastructure. Unknown capability/network and unverified budget requests return no eligible matches. Read-only canonical Autonomy discovery. Payment and execution remain safety-paused; catalog entries can be LEGACY or BLOCKED, not sellable.

Parametersassetquerystatusnetworkcapabilitysellable_onlymax_atomic_amount

autonomy_service

Inspect one canonical service by ID, including status, input/output schema and payment readiness. Read-only canonical Autonomy discovery. Payment and execution remain safety-paused; catalog entries can be LEGACY or BLOCKED, not sellable.

Parametersservice_idrequired

autonomy_registry_status

Inspect registry version, honest commercial status and transport capabilities. This does not claim upstream provider health.

Takes no parameters.

Version history

1
  1. v2.0.0LatestSep 17, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.