mcpbeat Sign in

User Agent Parser API MCP Server

by br0ski777 Your server? Claim it
not responding

User Agent Parser API is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 2 Sep 2026.

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

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 91 checks
1
Tools
read from the server
8 ms
Response time
average over 24h
0
Stars
last commit 2 Sep 2026

User Agent Parser API does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add user-agent-parser --transport sse https://user-agent-parser.api.klymax402.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://user-agent-parser.api.klymax402.com/mcp
~/.codex/config.toml
[mcp_servers.user-agent-parser]
url = "https://user-agent-parser.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "user-agent-parser": {
      "url": "https://user-agent-parser.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "user-agent-parser": {
      "type": "sse",
      "url": "https://user-agent-parser.api.klymax402.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

utility
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. 1. browser -- name and version (e.g. "Chrome 120.0") 2. os -- operating system name and version (e.g. "Windows 11") 3. device -- type (desktop, mobile, tablet), vendor, and model 4. engine -- rendering engine (Blink, Gecko, WebKit) 5. isBot -- boolean indicating if the UA belongs to a crawler/bot 6. botName -- name of the bot if detected (e.g. "Googlebot") Example output: {"browser":{"name":"Chrome","version":"120.0"},"os":{"name":"Windows","version":"11"},"device":{"type":"desktop","vendor":null,"model":null},"engine":"Blink","isBot":false,"botName":null} Use this FOR analytics pipelines that need to classify traffic by device or browser, detecting bot traffic in access logs, or adapting content based on client capabilities. Do NOT use for HTTP header analysis -- use utility_parse_http_headers instead. Do NOT use for web scraping -- use web_scrape_to_markdown instead. Do NOT use for SEO auditing -- use seo_audit_page instead.

Endpoints

URLTransportStateLatencyChecked
https://user-agent-parser.api.klymax402.com/mcp sse answering 8 ms 9 min ago

Alternatives to User Agent Parser API

same job, measured the same way
UAParse
by workers-mike-tusa-uaparse

Parse a User-Agent: browser, OS, device, plus bot, search crawler, AI crawler and AI agent flags.

1 tools answering
A
Agent Browser
by scriptmasterlabs

Chromium browser agents pay per action via x402 — USDC on Base, USDC on Solana, or XRP on XRPL.

6 tools answering
Useragent MCP
by mrfentmen

Parse user-agent strings into browser, engine, OS and device, and flag crawlers - fully local.

113 installs/wk local only
Anchor Browser
by anchorbrowser

Cloud browsers for AI agents: get past bot detection, sign in with MFA, run web tasks at scale.

answering
Uplink
by uplink

Automate a real, logged-in browser on your own device — no stored credentials, no bot detection.

70 installs/wk local only
x402-screenshot-mcp
by 6mickswagger9

x402 paid API for AI agents. USDC on Base. CDP facilitator.

358 installs/wk local only
Zendriver MCP
by bituq

Undetectable browser automation for LLM agents, spoken over MCP.

156 installs/wk local only
CloakMCP
by overtimepog

Stealth browser MCP server — anti-detection Chromium with snapshot-first agent interface

197 installs/wk local only

User Agent Parser API — questions

Answers built from our own checks of this server.

What can User Agent Parser API do?
It exposes 1 tools, read directly from the server on our last check. Among them: utility_parse_user_agent. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is User Agent Parser API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 8 ms. The bar chart above shows every period we have measured.
The registry lists User Agent Parser API as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect User Agent Parser API?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does User Agent Parser API need an API key?
No. User Agent Parser API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
Is User Agent Parser API open source?
The code is open source: it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at user-agent-parser.api.klymax402.com, which runs on its operator's own terms.