User Agent Parser API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

Parse user agents — browser, OS, device, bot detection. x402 micropayment.

The publisher's own server: Parser Club

VerifiedSSEWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Remote MCP endpoint that parses a user agent string into browser, OS, device, engine and bot-detection fields, paid per call via x402.

What you can do
  • Parse a user agent string into structured data: browser name and version, OS, device type, engine, and bot status with bot name.
  • Returns a single JSON object suitable for classifying traffic in analytics pipelines or access logs.
When to use it
Useful when an assistant needs to classify traffic by browser, OS or device, detect bot traffic in access logs, or adapt content to client capabilities, and a paid per-call lookup is acceptable.
Requirements
A remote MCP endpoint reached over SSE; no API key or signup. Calls are paid per request in USDC on Base L2 through the x402 protocol, so an x402-aware client and a funded wallet are needed to complete the payment challenge.
Before you install
Each call costs money ($0.003 per parse) and is settled in USDC on Base L2 through a wallet, so spending is real. Payment is handled by third-party facilitators (Coinbase CDP, PayAI) and the service is part of a larger commercial marketplace; review wallet limits before connecting.

Installation

In SourceWeft

  1. Open User Agent Parser API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fuser-agent-parser/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "user-agent-parser-api": {
      "type": "sse",
      "url": "https://user-agent-parser.api.klymax402.com/mcp"
    }
  }
}

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.):

json
{  "mcpServers": {    "user-agent-parser": {      "url": "https://user-agent-parser.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
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:

json
{"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

Source: README.md at commit 7792551

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Parser integrations