generated: '2026-09-19'
method: derived
source: >-
  Live tools/list from https://legit.gonna.bond/mcp (mcp/gonna-bond-mcp-tools.json, probed 2026-09-19)
  aligned by name and parameter semantics with the operationIds in openapi/gonna-bond-legit-openapi.yml
  (24 operations, fetched the same day from https://legit.gonna.bond/openapi.json).
description: >-
  Binds each LEGIT MCP tool to the REST operation that backs it, so the tool inherits that operation's
  parameters as its real input contract. The MCP schema was NOT gated — every inputSchema below is the one
  the server returned — so the bindings are name-and-semantics matches between two published documents.
surfaces:
  openapi: openapi/gonna-bond-legit-openapi.yml
  graphql: null
  mcp:
    url: https://legit.gonna.bond/mcp
    tools_list: anonymous (HTTP 200, 4 tools with inputSchema)
    protocol_version: '2024-11-05'
crosswalk:
- tool: check_trust
  category: trust
  rest: [check_v1_check__address__get]
  binding: rest
  confidence: high
  note: The tool's single `address` input is the operation's path parameter; the MCP description also accepts an https URL, which the OpenAPI parameter description does not mention.
- tool: compare_merchants
  category: trust
  rest: [compare_v1_compare_get]
  binding: rest
  confidence: high
  note: >-
    MCP takes `addresses` as an array (2-5); REST takes the same 2-5 addresses as one comma-separated
    query string. The REST operation is x402-paid (402 without PAYMENT-SIGNATURE); whether the tool call
    is likewise charged was not tested.
- tool: leaderboard
  category: discovery
  rest: [leaderboard_v1_leaderboard_get]
  binding: rest
  confidence: high
  note: MCP exposes `network` + `limit` (1-50); REST exposes network, view, page, size, q, include_testnet, include_dormant. The tool is a narrowed view of the operation.
mcp_only:
- tool: get_badge_url
  reason: >-
    Wraps GET /v1/badge/{address}.svg, which the provider serves (probed 200, image/svg+xml) and names in
    the agent card and llms.txt, but which is absent from the OpenAPI document. The tool also composes an
    HTML embed snippet server-side.
rest_only:
- capability: trust reports
  operations: [report_v1_report__address__get, batch_check_v1_batch_check_post, deep_check_v1_deep_check_post, history_v1_history_get, receipts_v1_receipts_get, merchant_identity_v1_merchant__address__identity_get]
- capability: routing and discovery
  operations: [route_v1_route_get, trending_v1_trending_get, pulse_v1_pulse_get, networks_v1_networks_get, chain_logos_v1_chain_logos_get]
- capability: settlement arena
  operations: [arena_v1_arena_get, arena_preview_v1_arena_preview_get]
- capability: watch sentinel
  operations: [create_watch_v1_watch_post, watch_status_v1_watches__watch_id__get, watch_events_v1_watches__watch_id__events_get]
- capability: service metadata
  operations: [health_health_get, stats_v1_stats_get, wellknown__well_known_legit_get, referee_report_v1_referee_get, referee_reproduce_script_v1_referee_reproduce_py_get]
coverage:
  tools_named: 4
  tools_bound: 3
  mcp_only: 1
  rest_operations_total: 24
  rest_operations_with_tool: 3