provecart_agent_profile — ProveCart MCP Tool
provecart_agent_profile
(provecart agent profile) is one of 18 tools on the
ProveCart
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call provecart_agent_profile from your client
- Claude Code ProveCart provecart_agent_profile run in your project directory
- Claude Desktop ProveCart provecart_agent_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ProveCart provecart_agent_profile ~/.cursor/mcp.json
- VS Code ProveCart provecart_agent_profile .vscode/mcp.json
- Zed ProveCart provecart_agent_profile ~/.config/zed/settings.json
- Windsurf ProveCart provecart_agent_profile ~/.codeium/windsurf/mcp_config.json
- Cline ProveCart provecart_agent_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ProveCart provecart_agent_profile ~/.gemini/settings.json
- Grok ProveCart provecart_agent_profile .mcp.json (in your project root)
- ChatGPT ProveCart provecart_agent_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai ProveCart provecart_agent_profile Settings → Connectors → Add custom connector
- LangChain ProveCart provecart_agent_profile pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http provecart https://api.provecart.com/mcp
Other tools on this server
- provecart_check_order
- provecart_check_booking
- provecart_check_reservation
- provecart_agent_register
- provecart_agent_selftest
- provecart_scoreboard
- provecart_certification_info
- provecart_agent_signup
- agent_arrive
- provecart_agent_exam_start
- provecart_agent_exam_answer
- provecart_agent_visit
- provecart_agent_leave
- provecart_agent_claim
- provecart_agent_name
- provecart_agent_board_read
- provecart_agent_board_post
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.