← all claims · /methodology#for-ai-agents
xrpl.methodology_for_ai_agents.mcp_third_party_naming_dispute_url_present
Every MCP tool whose data payload names a third party (issuer attestation, RWA family attribution) carries `dispute_contact_url` in the data payload.
yellow
Public-infrastructure dependent OR no independent cross-check path yet. Free-tier only until Batch B walker migration lands (post-soak, ~2026-08-31) and/or an independent verification walker is wired for this series.
What this claim says
- label
- Every MCP tool whose data payload names a third party (issuer attestation, RWA family attribution) carries `dispute_contact_url` in the data payload.
- page
- /methodology#for-ai-agents
- claim id (yaml)
mcp_third_party_naming_dispute_url_present- behavior
MANUAL_CURATION- Layer 3 source
self-attested-only
Risk note
Third-party-naming discipline (Day 4). Any tool that assigns a name / tier / attribution to an address the site did not originate must expose a first-party correction channel — same rule the /tokens per-row footer link and /rwa page-level footer apply to human readers. If CONTACT_PURPOSES rename drops the `attestation-dispute` key, both the on-page footer and the MCP data-payload URL 404 in the same way, so a single fix closes both surfaces. Adjacent to attestation-dispute-correction-path project memory (16cebf4).
Evidence — code paths that back this claim
- mcp_tools_amm_tokens.py:tool_get_token_attestation (data.dispute_contact_url)
- mcp_tools_amm_tokens.py:tool_get_rwa_families (data.dispute_contact_url)
- mcp_tools_amm_tokens.py:tool_get_rwa_pools (data.dispute_contact_url)
- mcp_tools_amm_tokens.py:DISPUTE_CONTACT_URL
- app.py:CONTACT_PURPOSES (attestation-dispute)