Parse a User-Agent: browser, OS, device, plus bot, search crawler, AI crawler and AI agent flags.
Connect Remote server
claude mcp add --transport http uaparse https://uaparse.mike-tusa.workers.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"uaparse": {
"url": "https://uaparse.mike-tusa.workers.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"uaparse": {
"type": "http",
"url": "https://uaparse.mike-tusa.workers.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://uaparse.mike-tusa.workers.dev/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 1 found in our last check
parse_user_agentParse one User-Agent string. Returns browser, engine, OS, device type and CPU (ua-parser-js 1.0.41), and whether it is a known bot, search crawler, AI crawler (with its AI purpose) or an AI agent acting for a user (is_ai_agent, ai_agent_kind fetch | browsing), plus the bot name,…
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Optional. 'Bearer up_live_…' (free API key, issued by email request) for higher limits. Works without a key. |
Details
| Endpoint | https://uaparse.mike-tusa.workers.dev/mcp (Streamable HTTP) |
| First published | 1 Nov 2026 |
| Last updated | 1 Nov 2026 |
| Registry name | dev.workers.mike-tusa.uaparse/uaparse |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
