Categories › Web & Browser › Browser automation (click, fill, screenshot)
Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans.
Remote server: your requests and data go to nessgate.com. Claude Code: claude mcp add --transport http nessgate https://nessgate.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
discover_domain — Given a domain, read whatever it publishes at the standard machine-discovery locations (llms.txt, /.well-known/ard.json, /.well-known/agent-connect_domain — Given a domain AND the calling client's capabilities, return HOW the client can connect: one outcome (ready | credentials-required | incomplcheck_readiness — Given a domain, return each connectable resource it publishes with a readiness assessment (ready | credentials-required | incomplete | brokeNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.