harbor_pay_status — MCP Harbor MCP Tool
harbor_pay_status
(harbor pay status) is one of 36 tools on the
MCP Harbor
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call harbor_pay_status from your client
- Claude Code MCP Harbor harbor_pay_status run in your project directory
- Claude Desktop MCP Harbor harbor_pay_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MCP Harbor harbor_pay_status ~/.cursor/mcp.json
- VS Code MCP Harbor harbor_pay_status .vscode/mcp.json
- Zed MCP Harbor harbor_pay_status ~/.config/zed/settings.json
- Windsurf MCP Harbor harbor_pay_status ~/.codeium/windsurf/mcp_config.json
- Cline MCP Harbor harbor_pay_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MCP Harbor harbor_pay_status ~/.gemini/settings.json
- Grok MCP Harbor harbor_pay_status .mcp.json (in your project root)
- ChatGPT MCP Harbor harbor_pay_status Settings → Connectors → Advanced → Developer mode
- Claude.ai MCP Harbor harbor_pay_status Settings → Connectors → Add custom connector
- LangChain MCP Harbor harbor_pay_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http harbor https://rustyonmars.com/harbor-api/mcpOther tools on this server
- harbor_health
- berth_list
- berth_status
- harbor_gate
- berth_register
- berth_hook
- offer_list
- harbor_search
- harbor_interact
- harbor_services
- harbor_packages
- harbor_checkout
- harbor_validate
- harbor_arrive
- offer_run
- harbor_news
- finder_search
- finder_wanted
- finder_harvest
- market_list
- market_post
- market_buy
- exchange_list
- exchange_make
- join_list
- join_share
- swarm_listen
- swarm_say
- swarm_in
- harbor_how
- harbor_federation
- desk_ask
- harbor_yard
- desk_list
- harbor_gifts
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.