# UAParse (remote · uaparse.mike-tusa.workers.dev)

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

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- remote · `uaparse.mike-tusa.workers.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-mike-tusa-uaparse-uaparse/uaparse.md), [page](https://verifymcp.io/servers/dev-workers-mike-tusa-uaparse-uaparse/uaparse)

## Channel facts

- Endpoint: `https://uaparse.mike-tusa.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-16.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 525 tokens (~525/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the UAParse MCP server?

UAParse is a hosted endpoint at https://uaparse.mike-tusa.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-workers-mike-tusa-uaparse-uaparse 'https://uaparse.mike-tusa.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-mike-tusa-uaparse-uaparse": {
      "url": "https://uaparse.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-mike-tusa-uaparse-uaparse": {
      "type": "http",
      "url": "https://uaparse.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-mike-tusa-uaparse-uaparse]
url = "https://uaparse.mike-tusa.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-mike-tusa-uaparse-uaparse": {
      "type": "remote",
      "url": "https://uaparse.mike-tusa.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-mike-tusa-uaparse-uaparse --url 'https://uaparse.mike-tusa.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-mike-tusa-uaparse-uaparse:
    url: "https://uaparse.mike-tusa.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-mike-tusa-uaparse-uaparse": {
      "Transport": "http",
      "Url": "https://uaparse.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-mike-tusa-uaparse-uaparse -t streamable-http -u 'https://uaparse.mike-tusa.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-mike-tusa-uaparse-uaparse": {
      "type": "http",
      "url": "https://uaparse.mike-tusa.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 69, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.3.2 → 0.5.1

### 2026-10-14 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 68, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-10 (score 67)

First indexed and scored.

## MCP tools (1)

### `parse_user_agent` (~241 tokens)

Parse a User-Agent (browser, OS, device, bot / AI crawler / AI agent)

Parse 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, operator, robots.txt token and operator docs link from a curated list of 151 bots (list 2026-10-08). verified is always false: the User-Agent is self-reported and UAParse does no IP or reverse-DNS checks. Read-only, no network lookups. Same engine and limits as the UAParse JSON API (POST /v1/parse); each call is one lookup. UAParse is independent and not affiliated with Meta, OpenAI, Google, Anthropic, Amazon, Perplexity or Mistral AI.

Input parameters:

- `include_raw` (boolean): Also return the full POST /v1/parse JSON in structuredContent.raw. Larger output.
- `ua` (string, required): The User-Agent string to parse, exactly as sent in the User-Agent header.

Output parameters:

- `bot` (object): Present when is_bot is true. Fields that are unknown are omitted.
- `browser` (object)
- `cached` (boolean)
- `cpu` (object)
- `device` (object)
- `engine` (object)
- `is_ai_agent` (boolean): true only for User-Agents the operator documents as acting live for an individual user
- `is_ai_crawler` (boolean)
- `is_bot` (boolean)
- `is_search_crawler` (boolean)
- `list_version` (string)
- `os` (object)
- `parser` (string)
- `raw` (object): Full POST /v1/parse response (only when include_raw is true)
- `summary` (string): One-line plain-English verdict
- `tier` (string)
- `ua` (string): The parsed User-Agent (clipped to 300 characters; see ua_length)
- `ua_length` (integer)
- `version` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-mike-tusa-uaparse-uaparse/uaparse#diagnostics

## Score history

- 2026-10-16: 69
- 2026-10-15: 69
- 2026-10-14: 69
- 2026-10-13: 68
- 2026-10-12: 68
- 2026-10-10: 67

## Common questions

### What is the UAParse MCP server?

UAParse is an MCP server listed in the public MCP registry as dev.workers.mike-tusa.uaparse/uaparse. Parse a User-Agent: browser, OS, device, plus bot, search crawler, AI crawler and AI agent flags. This page covers its hosted endpoint (https://uaparse.mike-tusa.workers.dev/mcp).

### Is the UAParse MCP server safe to use?

UAParse scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the UAParse MCP server expose?

UAParse exposes 1 tool: parse_user_agent. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.

### Does the UAParse MCP server require authentication?

No. We connected to UAParse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the UAParse MCP server still maintained?

UAParse is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://uaparse.mike-tusa.workers.dev/mcp
- Website: https://uaparse.mike-tusa.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-mike-tusa-uaparse-uaparse/uaparse.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-mike-tusa-uaparse-uaparse/uaparse.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-mike-tusa-uaparse-uaparse/uaparse