user-agent-parser
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@user-agent-parserParse this user agent string and tell me the browser, OS, and device type"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
User Agent Parser API
Parse 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.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"user-agent-parser": {
"url": "https://user-agent-parser.api.klymax402.com/mcp"
}
}
}Related MCP server: reversesandbox-mcp
Quickstart -- HTTP (x402)
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 bodyAny x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
Tool | Method | Path | Price | Description |
| POST |
| $0.003 | Parse a user agent string into structured data |
utility_parse_user_agent
Use 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 |
| 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).
Example agent prompts
"Parse a user agent string to identify the client's browser, OS, device type, and bot status"
Payment
Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
Network: Base L2 (
eip155:8453)Asset: USDC
Facilitator: Coinbase CDP (primary), PayAI (fallback)
Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
Catalog: https://klymax402.com/llms.txt
Full API reference: https://klymax402.com/llms-full.txt
Live stats: https://klymax402.com/stats
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Pay-per-use tool API for AI agents. Free tier, x402 USDC micropayments, or API key.
Pay-per-use weather, environment, finance, and on-chain intelligence tools for AI agents via x402.
Pay-per-call web scraping for AI agents via x402 on Base USDC. Six tools, no signup.
Pay-per-call data APIs for AI agents. USDC on Base via x402. 33 tools, no signup.
Related MCP Servers
FlicenseNot gradedqualityFmaintenanceProvides 20+ AI agent capabilities like web scraping, PDF parsing, OCR, and more, with pay-per-use micropayments via x402.1-- AlicenseNot gradedqualityDmaintenanceEnables AI agents to pay for x402 pay-per-use services like web search, scraping, and screenshots using a simple API key and USD balance, without managing crypto wallets.1 npmMIT
- AlicenseNot gradedqualityBmaintenanceWebsite intelligence tools for AI agents. Ten pay-per-call tools via x402 micropayments (USDC on Base) — no accounts, no API keys.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to use pay-per-use web scraping, Base blockchain analytics, and PDF text extraction tools, monetized via x402 USDC micropayments.-