Parses user agent strings to extract browser, OS, device type, and bot detection signals, served over SSE with x402 micropayment integration. The repository is sparse on implementation details, but the remote endpoint at user-agent-parser.api.klymax402.com suggests a hosted service model. You'd use this when building analytics pipelines, A/B testing systems, or bot filtering layers where you need structured data from raw user agent headers. The x402 payment layer means you're paying per parse rather than running your own UA-WHM or Browscap setup. Useful if you want to offload parsing logic and don't want to maintain regex patterns as new browsers and devices ship.
Public tool metadata for what this MCP can expose to an agent.
utility_parse_user_agentUse this when you need to parse a user agent string to identify the client's browser, OS, device type, and bot status. Returns fully structured data. 1. browser -- name and version (e.g. "Chrome 120.1 paramsUse this when you need to parse a user agent string to identify the client's browser, OS, device type, and bot status. Returns fully structured data. 1. browser -- name and version (e.g. "Chrome 120.
userAgentstringtherealtimex/browser-use
jae-jae/fetcher-mcp
merajmehrabi/puppeteer-mcp-server
com.thenextgennexus/playwright-mcp-server
saik0s/mcp-browser-use