← satohub.ai

INDIVIDUAL MCP TOOL

onchain_agent_preflight

USE WHEN you are about to install a package, clone a repo, connect to an MCP endpoint, pay an agent, or trade a token, and you want to know what is on record about it FIRST.

satohub.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://satohub.ai/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for onchain_agent_preflight and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name, description or schema mentions credentials.
  • A tool name or description suggests a financial action.

Parent server

satohub.ai

CONNECT 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.onchain-agent-mcp-server]
url = "https://satohub.ai/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "onchain-agent-mcp-server": {
      "type": "http",
      "url": "https://satohub.ai/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: onchain-agent-mcp-server
Remote MCP URL: https://satohub.ai/api/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": {
    "onchain-agent-mcp-server": {
      "url": "https://satohub.ai/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "onchain-agent-mcp-server": {
      "type": "http",
      "url": "https://satohub.ai/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "onchain-agent-mcp-server",
  "transport": "streamable-http",
  "url": "https://satohub.ai/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • onchain_agent_search_resources — USE WHEN someone asks what to build a crypto or onchain agent with, which tools support a chain or standard, or whether a specific project exists and is maintained.
  • onchain_agent_get_resource — USE WHEN you need to judge one specific project — is it open source, still maintained, who is behind it, what does it support.
  • onchain_agent_get_deploy_spec — USE WHEN you are about to write setup instructions or install something for a user and want steps that were verified rather than copied from a README.
  • onchain_agent_recent_changes — Get recorded changes across the directory — the auditable Listing History.
  • onchain_agent_list_categories — List all resource categories with counts, most populated first.
  • onchain_agent_list_chains — List all blockchains represented in the directory with resource counts, spotlight chains first (Base, Ethereum, Solana, COTI, Injective…).
  • onchain_agent_get_news — USE WHEN asked what is new or what shipped recently in crypto AI agents, and you want dated, source-attributed items rather than undated blog posts.
  • onchain_agent_get_metrics — USE WHEN you need a current, citable figure for the onchain agent ecosystem rather than a number from an article of unknown age.