checker_status — Backed: NEAR solvency checks MCP Tool
checker_status
(checker status) is one of 3 tools on the
Backed: NEAR solvency checks
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call checker_status from your client
- Claude Code Backed: NEAR solvency checks checker_status run in your project directory
- Claude Desktop Backed: NEAR solvency checks checker_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Backed: NEAR solvency checks checker_status ~/.cursor/mcp.json
- VS Code Backed: NEAR solvency checks checker_status .vscode/mcp.json
- Zed Backed: NEAR solvency checks checker_status ~/.config/zed/settings.json
- Windsurf Backed: NEAR solvency checks checker_status ~/.codeium/windsurf/mcp_config.json
- Cline Backed: NEAR solvency checks checker_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Backed: NEAR solvency checks checker_status ~/.gemini/settings.json
- Grok Backed: NEAR solvency checks checker_status .mcp.json (in your project root)
- ChatGPT Backed: NEAR solvency checks checker_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Backed: NEAR solvency checks checker_status Settings → Connectors → Add custom connector
- LangChain Backed: NEAR solvency checks checker_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http backed https://backed-near.vercel.app/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 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.