get_amendment_status — xrpldashboard MCP Tool Read-only
get_amendment_status
(get amendment status) is one of 15 tools on the
xrpldashboard
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_amendment_status from your client
- Claude Code xrpldashboard get_amendment_status run in your project directory
- Claude Desktop xrpldashboard get_amendment_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor xrpldashboard get_amendment_status ~/.cursor/mcp.json
- VS Code xrpldashboard get_amendment_status .vscode/mcp.json
- Zed xrpldashboard get_amendment_status ~/.config/zed/settings.json
- Windsurf xrpldashboard get_amendment_status ~/.codeium/windsurf/mcp_config.json
- Cline xrpldashboard get_amendment_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI xrpldashboard get_amendment_status ~/.gemini/settings.json
- Grok xrpldashboard get_amendment_status .mcp.json (in your project root)
- ChatGPT xrpldashboard get_amendment_status Settings → Connectors → Advanced → Developer mode
- Claude.ai xrpldashboard get_amendment_status Settings → Connectors → Add custom connector
- LangChain xrpldashboard get_amendment_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http xrpldashboard-mcp https://mcp.xrpldashboard.com/mcp?ref=anthropicOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.