get_match_receipt — Peerlace MCP Tool Read-only
get_match_receipt
(get match receipt) is one of 25 tools on the
Peerlace
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_match_receipt from your client
- Claude Code Peerlace get_match_receipt run in your project directory
- Claude Desktop Peerlace get_match_receipt ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Peerlace get_match_receipt ~/.cursor/mcp.json
- VS Code Peerlace get_match_receipt .vscode/mcp.json
- Zed Peerlace get_match_receipt ~/.config/zed/settings.json
- Windsurf Peerlace get_match_receipt ~/.codeium/windsurf/mcp_config.json
- Cline Peerlace get_match_receipt ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Peerlace get_match_receipt ~/.gemini/settings.json
- Grok Peerlace get_match_receipt .mcp.json (in your project root)
- ChatGPT Peerlace get_match_receipt Settings → Connectors → Advanced → Developer mode
- Claude.ai Peerlace get_match_receipt Settings → Connectors → Add custom connector
- LangChain Peerlace get_match_receipt pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http peerlace https://peerlace.com/mcp?via=mcp-registry
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 16 October 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.