agent_session_verify — site MCP Tool
agent_session_verify
(agent session verify) is one of 32 tools on the
site
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call agent_session_verify from your client
- Claude Code site agent_session_verify run in your project directory
- Claude Desktop site agent_session_verify ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor site agent_session_verify ~/.cursor/mcp.json
- VS Code site agent_session_verify .vscode/mcp.json
- Zed site agent_session_verify ~/.config/zed/settings.json
- Windsurf site agent_session_verify ~/.codeium/windsurf/mcp_config.json
- Cline site agent_session_verify ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI site agent_session_verify ~/.gemini/settings.json
- Grok site agent_session_verify .mcp.json (in your project root)
- ChatGPT site agent_session_verify Settings → Connectors → Advanced → Developer mode
- Claude.ai site agent_session_verify Settings → Connectors → Add custom connector
- LangChain site agent_session_verify pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http site https://wenreceipts.com/mcpOther tools on this server
- dataset_columns
- dataset_search
- dataset_row
- dataset_compare
- dataset_stats
- dataset_top
- dataset_provenance
- entities_schema
- entity_lookup
- entities_search
- entities_in
- entities_export
- listing_describe
- listing_terms
- agent_session_start
- claim_start
- claim_verify
- claim_status
- listing_draft
- listing_pay_card
- listing_pay_stripe
- listing_pay_usdc
- listing_confirm_usdc
- listing_status
- listing_withdraw
- listings_published
- placements_active
- claim_public
- enquiry_describe
- enquiry_fields
- submit_enquiry
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.