source_status — Pauhu MCP Tool
source_status
(source status) is one of 22 tools on the
Pauhu
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call source_status from your client
- Claude Code Pauhu source_status run in your project directory
- Claude Desktop Pauhu source_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Pauhu source_status ~/.cursor/mcp.json
- VS Code Pauhu source_status .vscode/mcp.json
- Zed Pauhu source_status ~/.config/zed/settings.json
- Windsurf Pauhu source_status ~/.codeium/windsurf/mcp_config.json
- Cline Pauhu source_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Pauhu source_status ~/.gemini/settings.json
- Grok Pauhu source_status .mcp.json (in your project root)
- ChatGPT Pauhu source_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Pauhu source_status Settings → Connectors → Add custom connector
- LangChain Pauhu source_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http data https://api.pauhu.eu/mcpOther tools on this server
- pauhu_products
- pauhu_topup_card
- pauhu_translate
- monitor_register_connector
- monitor_list_connectors
- monitor_delete_connector
- monitor_register_template
- monitor_list_templates
- monitor_delete_template
- pauhu_tm
- pauhu_search
- concept_crosswalk
- source_search
- source_fetch_fragment
- source_verify_bearing
- code_read
- code_list
- code_grep
- code_diff
- library_catalogue
- library_verify
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.