API Tools
theautonomy.ai
An MCP server for discovering, inspecting, and managing Autonomy service capabilities, including blockchain state, balances, token data, and payment readiness via a canonical registry.
ENDPOINT 1
https://api.theautonomy.ai/mcp
MCP server metadata
- Name
- autonomy-mcp
- Version
- 2.0.1
Read-only canonical Autonomy discovery. Payment and execution remain safety-paused; catalog entries can be LEGACY or BLOCKED, not sellable.
Known tools 4
autonomy_servicesList canonical Autonomy service capabilities, actual availability, schemas and price readiness.
Inferred read-onlyautonomy_discoverFind capabilities when an agent needs blockchain state, balances, token data or other cataloged infrastructure.
Inferred read-onlyautonomy_serviceInspect one canonical service by ID, including status, input/output schema and payment readiness.
Potential side effectsautonomy_registry_statusInspect registry version, honest commercial status and transport capabilities.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.autonomy-mcp]
url = "https://api.theautonomy.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"autonomy-mcp": {
"type": "http",
"url": "https://api.theautonomy.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: autonomy-mcp
Remote MCP URL: https://api.theautonomy.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"autonomy-mcp": {
"url": "https://api.theautonomy.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"autonomy-mcp": {
"type": "http",
"url": "https://api.theautonomy.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "autonomy-mcp",
"transport": "streamable-http",
"url": "https://api.theautonomy.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.