base167_claim_entry_pass — BASE167 MCP Tool
base167_claim_entry_pass
(base167 claim entry pass) is one of 7 tools on the
BASE167
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call base167_claim_entry_pass from your client
- Claude Code BASE167 base167_claim_entry_pass run in your project directory
- Claude Desktop BASE167 base167_claim_entry_pass ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BASE167 base167_claim_entry_pass ~/.cursor/mcp.json
- VS Code BASE167 base167_claim_entry_pass .vscode/mcp.json
- Zed BASE167 base167_claim_entry_pass ~/.config/zed/settings.json
- Windsurf BASE167 base167_claim_entry_pass ~/.codeium/windsurf/mcp_config.json
- Cline BASE167 base167_claim_entry_pass ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BASE167 base167_claim_entry_pass ~/.gemini/settings.json
- Grok BASE167 base167_claim_entry_pass .mcp.json (in your project root)
- ChatGPT BASE167 base167_claim_entry_pass Settings → Connectors → Advanced → Developer mode
- Claude.ai BASE167 base167_claim_entry_pass Settings → Connectors → Add custom connector
- LangChain BASE167 base167_claim_entry_pass pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http base167 https://base167.com/mcpOther 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.