Hi HN, solo dev here. Built this because I kept copy-pasting AI-generated URLs out of Claude into a checker tool and back. The MCP integration removes that step — you stay in the chat, ask "validate these 500 URLs", get answers in-line.
The trickiest part was the OAuth + MCP server. Claude.ai uses lazy-auth (calls `tools/list` before authentication), which most MCP examples don't show. Required rethinking which endpoints need auth and which just describe what the connector exposes.
Both REST and MCP are available; free tier covers casual use. Happy to answer questions about the architecture, the OAuth flow, or how the MCP install ended up being a roughly 30-second flow vs. the API-key dance.
The trickiest part was the OAuth + MCP server. Claude.ai uses lazy-auth (calls `tools/list` before authentication), which most MCP examples don't show. Required rethinking which endpoints need auth and which just describe what the connector exposes.
Both REST and MCP are available; free tier covers casual use. Happy to answer questions about the architecture, the OAuth flow, or how the MCP install ended up being a roughly 30-second flow vs. the API-key dance.