Other · Remote MCP server

Oya Browser

Real Chrome for agents: start a browser, read pages as numbered markdown, click, type, hand off.

Visit Oya Browser's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.OyadotAI/oya-browser
Version
1.0.154
Status
Active
Category
other
Transport
Streamable HTTP
Published
2026-10-03
Updated
2026-10-03
Publisher
OyadotAI (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/OyadotAI) · how
Listed under
Browser automation MCP servers
Website
oyabrowser.com
Repository
github.com/OyadotAI/oya-browser
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://oyabrowser.com/mcp/poolAuthorization (required, secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401
Checked on
2026-10-05

How the live check works

How to connect Oya Browser

Oya Browser is a remote MCP server: there is nothing to install. Its endpoint is https://oyabrowser.com/mcp/pool, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 8,395 →
ServerRunsEndpoint or package
OwnerSpecCited home water treatment answers, part matching and sizing calculators for AI agents.Remote · HTTPLive check: ✓ handshakeownerspec.com
OwnhandWrite in the user's own voice, fitted to the occasion. Learns from the text they actually send.Remote · HTTPLive check: sign-in requiredownhand.dev
OwnlyLocal-first Ownly evidence and repeatable Planner visits with preview-before-commit writes.Local · stdionpm: @ownly-app/mcp
Ownware Catalogue49 self-hosted business apps: prices, SaaS comparisons, guides, quickstarts. Read-only, no key.Remote · HTTPLive check: ✓ handshakeownware.io
Ozon MCP ServerOzon Seller & Performance API, 156 tools; responses trimmed 476k to 64k tokens.Local · stdioPyPI: ozon-mcp-server
p-e relayRead-only access to an append-only corpus of provenance-bearing coordination records.Local · stdioOCI image (Docker): ghcr.io/zaebee/p-e:0.3.2
p-e relay (remote)Remote MCP access to the p-e relay store. Reads are open; writes and waits are signed.Remote · HTTPLive check: ✓ handshakerelay.zae.life
P402Multi-provider AI router with x402 micropayment settlement on Base L2. 1% flat fee.Local · stdionpm: @p402/mcp-server