mcpField
U
User Agent Parser X402

User Agent Parser X402

Remote
github.comAI & Agents0Updated 8w ago

About User Agent Parser X402

User Agent Parser X402 is an MCP server and pay-per-call API for turning user-agent strings into structured browser, OS, device, engine, and bot information. It is aimed at AI agents and analytics workflows, with x402 payments using USDC on Base and no API key or signup.

Key features

  1. 01Parses user-agent strings
  2. 02Returns browser, OS, and device details
  3. 03Identifies engine and bot status
  4. 04Pay-per-call through x402

Use cases

  1. 01Classifying traffic in analytics pipelines
  2. 02Detecting bots in access logs
  3. 03Adapting content to client capabilities

MCP support

The remote MCP endpoint exposes `utility_parse_user_agent`, which accepts a user-agent string and returns structured client details.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://user-agent-parser.api.klymax402.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

User Agent Parser API

MCP Server x402 License: MIT

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"
    }
  }
}

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 body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
utility_parse_user_agentPOST/api/parse$0.003Parse 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

NameTypeRequiredDescription
userAgentstringyesThe 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.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.