Hosted MCP server/Development

UAParse MCP server

Hosted at uaparse.mike-tusa.workers.dev·Streamable HTTP

UAParse parses a User-Agent string into browser, engine, OS, device type, and CPU, and flags known bots, search crawlers, AI crawlers, and AI agents that identify themselves in the User-Agent. It provides one read-only tool, parse_user_agent, with no API key needed for light use. Matches are by User-Agent only and can be spoofed. Authentication is not required, and the transport is HTTP. Documentation is available at https://uaparse.mike-tusa.workers.dev/docs. It is categorized as Development.

uaparse.mike-tusa.workers.dev Streamable HTTP No authentication Server not checked yet Reviewed 2026-11-04
About

Where it fits

Developers who need to parse User-Agent strings and flag known bots, search crawlers, AI crawlers, and AI agents with UAParse over HTTP.

  • Parse a User-Agent into browser, engine, OS, device type, and CPU.
  • Flag known bots and search crawlers in a User-Agent.
  • Identify AI crawlers and AI agents that identify themselves.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds UAParse as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http uaparse https://uaparse.mike-tusa.workers.dev/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://uaparse.mike-tusa.workers.dev/mcp
Host
uaparse.mike-tusa.workers.dev · /mcp
Transport
Streamable HTTP
Authentication
No authentication
Server name
uaparse
Listing type
Community or directory listing

The installer uses the server name uaparse. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that uaparse appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Parse a User-Agent into browser, engine, OS, device type, and CPU. Check the result before you give the server more access.

  3. 3
    Check permissions.

    The provider documents no credential for this endpoint, so there is no scope or token to review. Remove the server when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The server connects but no tools appear. Confirm the URL and transport, then restart the client.
  • The first tool call times out. Try a smaller request and check the provider's status or rate limits.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

UAParse documentationhttps://uaparse.mike-tusa.workers.dev/docsGitHub repositoryhttps://github.com/faisalman/ua-parser-js