MCP servers · Google Site Verification · connector · GPT action
Connect ChatGPT to Google Site Verification
One line gives ChatGPT your Google Site Verification account as tools: 3 endpoints, verify ownership, more, called with your own connection. No key in the prompt, a receipt for every call, revoke ChatGPT's access alone any time.
Three steps
- Create a free 0n3 account and connect Google Site Verification. Paste a key or sign in; it lands in your vault, encrypted.
- Install 0n3 into ChatGPT. A custom connector in Developer mode, or an Action on a custom GPT from the OpenAPI spec.
- Ask ChatGPT: whoami. Then: "Verify in Google Site Verification".
Custom connector (needs Developer mode)
- Settings → Connectors (or Apps) → Advanced → Developer mode on
- Create → name 0n3 · MCP server URL https://0n3.app/mcp · Authentication: OAuth
- Finish the sign-in with your 0n account
- Enable the connector in a chat and ask: "whoami"
ChatGPT connectors cannot send a static header, so 0n3 signs you in through its OAuth door (dynamic client registration is on).
The line above carries a placeholder; 0n3.app/install mints a real key named for ChatGPT and fills it in.
What ChatGPT can then do in Google Site Verification
Verify ownership · Issue a DNS/meta/file token and claim the domain1
Verify
POST /webResourceMore · Everything else this app exposes.2
Get a token
POST /tokenList owned
GET /webResourceGoogle Site Verification in other AI clients
Claude Code + Google Site VerificationMCP server + skillClaude (desktop & claude.ai) + Google Site VerificationconnectorCodex CLI + Google Site VerificationMCP serverGemini CLI + Google Site VerificationMCP serverCursor + Google Site VerificationMCP serverVS Code (Copilot) + Google Site VerificationMCP serverWindsurf + Google Site VerificationMCP server