city.compliance_path — x402 mcp MCP Prompt

city.compliance_path is one of 3 prompts on the x402 mcp MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke city.compliance_path from your client

• Claude Code x402 mcp Prompt/city.compliance_path run in your project directory
• Claude Desktop x402 mcp Prompt/city.compliance_path ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor x402 mcp Prompt/city.compliance_path ~/.cursor/mcp.json
• VS Code x402 mcp Prompt/city.compliance_path .vscode/mcp.json
• Zed x402 mcp Prompt/city.compliance_path ~/.config/zed/settings.json
• Windsurf x402 mcp Prompt/city.compliance_path ~/.codeium/windsurf/mcp_config.json
• Cline x402 mcp Prompt/city.compliance_path ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI x402 mcp Prompt/city.compliance_path ~/.gemini/settings.json
• Grok x402 mcp Prompt/city.compliance_path .mcp.json (in your project root)
• ChatGPT x402 mcp Prompt/city.compliance_path Settings → Connectors → Advanced → Developer mode
• Claude.ai x402 mcp Prompt/city.compliance_path Settings → Connectors → Add custom connector
• LangChain x402 mcp Prompt/city.compliance_path pip install langchain-mcp-adapters

Other prompts on this server

• x402.buy_paid_api
• x402.sell_api

x402 mcp also offers 6 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.