UAParse
REMOTE · UAPARSE.MIKE-TUSA.WORKERS.DEV
Parse a User-Agent: browser, OS, device, plus bot, search crawler, AI crawler and AI agent flags.
Available components
Last scanned (22 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.3.2 → 0.5.1 functional
- 14 Oct 26 +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.
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://uaparse.mike-tusa.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mike-tusa.workers.dev | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f05aa95d8943eeed0e4e86dd1f6f1e02 |
| SANs: mike-tusa.workers.dev, *.mike-tusa.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of uaparse.mike-tusa.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://uaparse.mike-tusa.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://uaparse.mike-tusa.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
parse_user_agent Parse a User-Agent (browser, OS, device, bot / AI crawler / AI agent) ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_raw | boolean | – | Also return the full POST /v1/parse JSON in structuredContent.raw. Larger output. |
| ua | string | yes | The User-Agent string to parse, exactly as sent in the User-Agent header. |
| Name | Type | Req | Description |
|---|---|---|---|
| bot | object | – | Present when is_bot is true. Fields that are unknown are omitted. |
| browser | object | yes | – |
| cached | boolean | – | – |
| cpu | object | yes | – |
| device | object | yes | – |
| engine | object | yes | – |
| is_ai_agent | boolean | yes | true only for User-Agents the operator documents as acting live for an individual user |
| is_ai_crawler | boolean | yes | – |
| is_bot | boolean | yes | – |
| is_search_crawler | boolean | yes | – |
| list_version | string | yes | – |
| os | object | yes | – |
| parser | string | – | – |
| raw | object | – | Full POST /v1/parse response (only when include_raw is true) |
| summary | string | yes | One-line plain-English verdict |
| tier | string | – | – |
| ua | string | yes | The parsed User-Agent (clipped to 300 characters; see ua_length) |
| ua_length | integer | yes | – |
| version | string | yes | – |
No examples provided.
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.
remote · uaparse.mike-tusa.workers.dev
claude mcp add --transport http dev-workers-mike-tusa-uaparse-uaparse 'https://uaparse.mike-tusa.workers.dev/mcp'
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.