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.
userAgentstringParse any user agent string into structured data: browser, OS, device type, engine, and bot detection in one call. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"user-agent-parser": {
"url": "https://user-agent-parser.api.klymax402.com/mcp"
}
}
}
curl -X POST "https://user-agent-parser.api.klymax402.com/api/parse" \
-H "Content-Type: application/json" \
-d '{"userAgent":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
utility_parse_user_agent | POST | /api/parse | $0.001 | Parse a user agent string into structured data |
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.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
userAgent | string | yes | The user agent string to parse |
Example response:
{"browser":{"name":"Chrome","version":"120.0"},"os":{"name":"Windows","version":"11"},"device":{"type":"desktop","vendor":null,"model":null},"engine":"Blink","isBot":false,"botName":null}
When to use: analytics pipelines that need to classify traffic by device or browser, detecting bot traffic in access logs, or adapting content based on client capabilities.
Not for: HTTP header analysis (use utility_parse_http_headers), web scraping (use web_scrape_to_markdown), SEO auditing (use seo_audit_page).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT
therealtimex/browser-use
jae-jae/fetcher-mcp
merajmehrabi/puppeteer-mcp-server
com.thenextgennexus/playwright-mcp-server
saik0s/mcp-browser-use