What it does
The tool utility_parse_user_agent takes a single required userAgent string and returns structured data covering the client's browser, operating system, device type, rendering engine and whether it is a bot. It is exposed both as an MCP tool and as an HTTP POST endpoint at /api/parse, priced at $0.003 per call.
It suits analytics pipelines that classify traffic by device or browser, detecting bot traffic in access logs, and adapting content to client capabilities. The publisher's documentation points elsewhere for HTTP header analysis (utility_parse_http_headers), web scraping (web_scrape_to_markdown) and SEO auditing (seo_audit_page).
To use it over MCP, the server is added to an MCP client's configuration. Over HTTP, calls are paid per request through the x402 protocol in USDC on Base L2, settled by the Coinbase CDP facilitator with PayAI as fallback, and ATXP is also supported. No API key or signup is required.
Limitations and requirements
Each call is paid in USDC on Base L2 through the x402 protocol, so the calling client must be x402-aware and hold a wallet with USDC on Base L2.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
User Agent Parser API
Parse user agents — browser, OS, device, bot detection. x402 micropayment.
v1.1.0As shown on registry.modelcontextprotocol.io when we last read it