health-history — Kryptonian Labs XRPL APIs MCP Resource
health-history
is one of 24 resources on the
Kryptonian Labs XRPL APIs
MCP server. Connect the server and your client can attach it as context.
by client
How to attach health-history from your client
- Claude Code Kryptonian Labs XRPL APIs Resource/health-history run in your project directory
- Claude Desktop Kryptonian Labs XRPL APIs Resource/health-history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Kryptonian Labs XRPL APIs Resource/health-history ~/.cursor/mcp.json
- VS Code Kryptonian Labs XRPL APIs Resource/health-history .vscode/mcp.json
- Zed Kryptonian Labs XRPL APIs Resource/health-history ~/.config/zed/settings.json
- Windsurf Kryptonian Labs XRPL APIs Resource/health-history ~/.codeium/windsurf/mcp_config.json
- Cline Kryptonian Labs XRPL APIs Resource/health-history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Kryptonian Labs XRPL APIs Resource/health-history ~/.gemini/settings.json
- Grok Kryptonian Labs XRPL APIs Resource/health-history .mcp.json (in your project root)
- ChatGPT Kryptonian Labs XRPL APIs Resource/health-history Settings → Connectors → Advanced → Developer mode
- Claude.ai Kryptonian Labs XRPL APIs Resource/health-history Settings → Connectors → Add custom connector
- LangChain Kryptonian Labs XRPL APIs Resource/health-history pip install langchain-mcp-adapters
Other resources on this server
- index
- fee
- ledger-latest
- health
- network-health
- orderbook
- slippage
- amm
- account-summary
- pro
- guides/freshness
- guides/currencies-and-amounts
- guides/rate-limits
- guides/errors
- guides/choosing-a-tool
- guides/mcp-quickstart
- errors/invalid-parameters
- errors/bad-request
- errors/not-found
- errors/unknown-route
- errors/rate-limited
- errors/internal-error
- errors/upstream-unavailable
Kryptonian Labs XRPL APIs also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 6 October 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.