MCP tools reference

Core, compatibility, and meta tool tables with tiers and auth profiles for the managed Thirdfy MCP endpoint.

This page is the integrator map for the managed Thirdfy MCP endpoint at https://mcp.thirdfy.com.

The live tool list is always authoritative:

curl -s https://mcp.thirdfy.com/tools

Use POST https://mcp.thirdfy.com/tool/<toolName> or streamable HTTP POST /mcp from your agent host. See Connect.

Core tools (default)

ToolCategory
getActionsCatalogDiscovery
getAgentActionsDiscovery
getProviderActionsDiscovery
getChainCapabilitiesDiscovery
getNonEvmCapabilitiesDiscovery
getThirdfyHelpOnboarding
describeOnboardingPathOnboarding
startEmailOnboardingOnboarding
completeEmailOnboardingOnboarding
getWalletProfileOnboarding
agentRegisterOnboarding
bootstrapSelfIdentityOnboarding
getSelfReadinessOnboarding
executeIntentExecution
getIntentStatusExecution
buildTxExecution
walletExecuteExecution
walletSignExecution
walletSubmitExecution
agentRunExecution
agentWalletBootstrapWallets
delegationCreateDelegation
delegationActivateDelegation
delegationStatusDelegation
delegationRevokeDelegation
delegationInspectDelegation
delegationBalanceDelegation
delegationRedeemDelegation
managedWalletInitManaged wallet
managedWalletGrantManaged wallet
managedWalletStatusManaged wallet
getAgentDataSummaryTracking
getAgentPortfolioSummaryTracking
getAgentLeaderboardTracking
getAgentTrackActionsTracking
getAgentTrackEventsTracking
trackAgentActionTracking

Chapter guides: Discovery · Execution · Delegation · Onboarding · Tracking

Compatibility tools

Compatibility tools are hidden on the managed endpoint by default. New integrations should use core tools only.

If your deployment exposes compat tools, see Compatibility tools for the legacy alias and V1 protocol read warnings.

Meta tools

ToolPurpose
healthLiveness
listToolsTool enumeration

Auth profiles (summary)

Each tool declares an authProfile and acceptedCredentialModes in the live manifest (GET /tools):

ProfileMeaning
transportPublic or transport-level only
agent_executionRequires agent_api_key or bootstrap where allowed
owner_interactiveOwner session or wallet proof
mixedDepends on tool inputs

Details: Authentication

Evaluation checklist

  • Can the agent discover earn actions with getProviderActions { provider: "earn" } without the trading-named alias?
  • Does it call agentWalletBootstrap with requireFundingCheck before walletExecute on collateralized lanes?
  • Does it use executeIntent for fan-out and walletExecute for a single agent wallet?
  • Does it reject self for off-chain venue orders?