Oya Browser
REMOTE · OYABROWSER.COM
Real Chrome for coding agents over MCP: browse, replay playbooks, human takeover, HIPAA & BAA.
Available components
Last scanned (2 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Browser Automation
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1880 tokens (~58/item across 32 items; 32 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 32 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 21 Nov 2026 · Probed https://oyabrowser.com/mcp/pool
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=oyabrowser.com | CN=YE2,O=Let's Encrypt,C=US | 19 Nov 2026 | 17 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5d2b770995740b5723f9aacf686917f2b59 |
| SANs: *.oyabrowser.com, oyabrowser.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of oyabrowser.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| oyabrowser.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://oyabrowser.com/.well-known/oauth-protected-resource/mcp/pool"
Bearer resource_metadata="https://oyabrowser.com/.well-known/oauth-protected-resource/mcp/pool" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Protected resource metadata
| Document | https://oyabrowser.com/.well-known/oauth-protected-resource/mcp/pool |
|---|---|
| Retrieved | Yes |
| Resource | https://oyabrowser.com/mcp/pool |
| Authorisation server | https://oyabrowser.com/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://oyabrowser.com/mcp/pool | Verified | 200 | |
| http (plaintext) | http://oyabrowser.com/mcp/pool | HTTPS enforced | 308 | https://oyabrowser.com/mcp/pool |
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 →
analyze_page Analyze Page ~144
Analyze the current page. Returns its content and every interactive element with an id to use with click/type tools. Ids stay valid until the next analysis or a navigation, so one analysis covers a whole form; each analysis numbers the page afresh. plus page facts (url, title, viewport, scroll, and when they apply: panelScroll, modal, covered, truncated) and each element's state (off-screen, disabled, checked, a field's hint). format picks how it is written: toon (default; one table of blocks, fewer tokens), markdown or jsonl.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | How the page is written; the server default when left out |
No output schema declared.
No examples provided.
click Click Element ~36
Click an interactive element by its ID number (from analyze_page results).
| Name | Type | Req | Description |
|---|---|---|---|
| element_id | number | yes | The element ID number from analyze_page |
No output schema declared.
No examples provided.
click_coordinates Click at Coordinates ~64
Click at specific x,y pixel coordinates on the page. Use when you know the exact position (e.g. from a screenshot).
| Name | Type | Req | Description |
|---|---|---|---|
| x | number | yes | X coordinate in pixels from the left edge |
| y | number | yes | Y coordinate in pixels from the top edge |
No output schema declared.
No examples provided.
complete_mfa Complete MFA ~50
Fill and submit a one-time code (MFA / 2FA) the page asks for, from the persona's authenticator, email or SMS. Call it on a code prompt after signing in.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
double_click Double Click ~68
Double-click an element by ID or at specific x,y coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| element_id | number | – | Element ID to double-click (from analyze_page) |
| x | number | – | X coordinate (used if no element_id) |
| y | number | – | Y coordinate (used if no element_id) |
No output schema declared.
No examples provided.
drag Drag ~70
Drag from one point to another. Useful for sliders, drag-and-drop, or selecting text.
| Name | Type | Req | Description |
|---|---|---|---|
| from_x | number | yes | Start X coordinate |
| from_y | number | yes | Start Y coordinate |
| to_x | number | yes | End X coordinate |
| to_y | number | yes | End Y coordinate |
No output schema declared.
No examples provided.
find Find Elements ~65
Find the elements that match a description ("search box", "add to cart", "next page"), best first, with ids click and type accept. Much shorter than analyze_page when you know what you are looking for.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The words the element is known by |
No output schema declared.
No examples provided.
go_back Go Back ~32
Go back one page in the tab's history, like the browser's back button, and wait for it to load.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
go_forward Go Forward ~24
Go forward one page in the tab's history and wait for it to load.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
handle_dialog Answer Dialog ~58
Answer a native browser dialog (confirm or prompt) blocking the page. Alerts are answered automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| accept | boolean | yes | true clicks OK, false clicks Cancel |
| prompt_text | string | – | Text to enter, for a prompt dialog only |
No output schema declared.
No examples provided.
hover Hover Element ~45
Move the mouse onto an element, for menus, tooltips and previews that open on hover. Tells you what appeared.
| Name | Type | Req | Description |
|---|---|---|---|
| element_id | number | yes | Element ID from analyze_page |
No output schema declared.
No examples provided.
keyboard_type Type on Keyboard ~36
Type text using the keyboard without targeting a specific element. Types into whatever is currently focused.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to type |
No output schema declared.
No examples provided.
list_playbooks List Playbooks ~30
List the playbooks saved on this key: recorded flows that replay without a model, with their variables.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_saved_logins List Saved Logins ~53
List the sites this browser's persona has a saved login for, with the username, never the password. Call it before a sign-in to know whether sign_in can fill the form and which account it will use.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mouse_move Move Mouse ~55
Move the mouse cursor to specific x,y coordinates without clicking. Useful for triggering hover states, tooltips, or dropdown menus.
| Name | Type | Req | Description |
|---|---|---|---|
| x | number | yes | X coordinate in pixels |
| y | number | yes | Y coordinate in pixels |
No output schema declared.
No examples provided.
navigate Navigate ~26
Navigate the browser to a URL.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to navigate to |
No output schema declared.
No examples provided.
pool_status Pool Status ~15
Show pool size and connected browsers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
press_key Press Key ~78
Press a safe navigation key. Allowed: Enter, Escape, Tab, ArrowDown, ArrowUp, ArrowLeft, ArrowRight, Backspace, Delete, Space, Home, End, PageUp, PageDown. Do NOT use for F-keys, Meta, Control, Alt, or Shift.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Key to press |
No output schema declared.
No examples provided.
reload Reload Page ~27
Reload the page and wait for it to load. For a page stuck loading or showing stale data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_playbook Run Playbook ~80
Replay a saved playbook on this browser with the given variables. Much faster and cheaper than doing the task step by step; a step that no longer fits the page is finished by the agent.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The playbook, from list_playbooks |
| variables | object | – | Values for its variables; its defaults fill the rest |
No output schema declared.
No examples provided.
run_script Run Page Script ~141
Run JavaScript that READS the page and returns data, for what analyze_page does not show well: every row of a long table, attributes, counts, text across many elements. The body of an async function: `return` the value (JSON-serialisable, cut at 8000 chars). It runs where the page cannot see it and must not change anything: no clicks, typing, requests or navigation; act with the element tools, which replay. Example: return [...document.querySelectorAll('table tr')].map(r => r.innerText);
| Name | Type | Req | Description |
|---|---|---|---|
| script | string | yes | The function body; `return` what you want to read |
No output schema declared.
No examples provided.
run_task Run Task ~83
Hand a whole task to Oya's own browser agent on this browser and get its report back (DONE: or FAILED:). Uses this key's configured model; the run can be saved as a playbook afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Values the task uses, referred to as {{name}} |
| task | string | yes | What to do, in plain words |
No output schema declared.
No examples provided.
screenshot Take Screenshot ~19
Capture a screenshot of the visible browser tab as an image.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scroll Scroll Page ~37
Scroll the page up or down.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Pixels to scroll (default 500) |
| direction | string | yes | Scroll direction |
No output schema declared.
No examples provided.
select_option Select Option ~69
Choose an option in a native dropdown (a select element from analyze_page) by the option text you see. Accepts {{placeholders}} and filters.
| Name | Type | Req | Description |
|---|---|---|---|
| element_id | number | yes | The select element ID from analyze_page |
| option | string | yes | The visible text of the option to choose |
No output schema declared.
No examples provided.
sign_in Sign In ~45
Sign in on the current page with the credentials stored for this site in the browser's persona. You never see them. Call it on a login form you were not given values for.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
solve_captcha Solve CAPTCHA ~46
Solve a CAPTCHA (reCAPTCHA, hCaptcha, Turnstile) on the current page with the configured solver. Call it when a CAPTCHA blocks you, then analyze_page again.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_browser Start Browser ~97
Start a new browser on this key and make it the one every other tool drives. Uses the key's configured provider unless one is given. It costs a session until stop_browser.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| persona | string | – | Persona id, 'auto' (least recently used under its concurrency cap) or 'default' |
| provider | string | – | – |
| url | string | – | Navigate here once the browser is ready |
No output schema declared.
No examples provided.
stop_browser Stop Browser ~33
Stop a browser and release its session. Defaults to the browser the tools are driving.
| Name | Type | Req | Description |
|---|---|---|---|
| browser_id | string | – | – |
No output schema declared.
No examples provided.
type Type Text ~72
Type text into an input element by its ID number (from analyze_page results). Clears existing content first. Typing keeps every id valid: fill the next field straight away, without analyzing again.
| Name | Type | Req | Description |
|---|---|---|---|
| element_id | number | yes | The element ID number from analyze_page |
| text | string | yes | The text to type |
No output schema declared.
No examples provided.
wait Wait for Element ~50
Wait for an element matching a CSS selector to appear on the page.
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | CSS selector to wait for |
| timeout | number | – | Max wait time in ms (default 10000) |
No output schema declared.
No examples provided.
wait_for Wait for Page ~132
Wait until the page is ready: some text shows, the url contains something, and/or the network has gone quiet. With no text or url it waits for the network to settle. Use it after an action that loads results in the background, rather than analyzing again and again.
| Name | Type | Req | Description |
|---|---|---|---|
| network_idle | boolean | – | Also wait for no new requests for a moment |
| text | string | – | Text that must appear on the page |
| timeout | number | – | Max wait in ms (default 10000, at most 20000) |
| url | string | – | Part of the url the page must reach |
No output schema declared.
No examples provided.
How do I install the Oya Browser MCP server?
Oya Browser is a hosted endpoint at https://oyabrowser.com/mcp/pool, 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 · oyabrowser.com
claude mcp add --transport http oyadotai-oya-browser 'https://oyabrowser.com/mcp/pool'
What is the Oya Browser MCP server?
Oya Browser is an MCP server listed in the public MCP registry as io.github.OyadotAI/oya-browser. Real Chrome for coding agents over MCP: browse, replay playbooks, human takeover, HIPAA & BAA. This page covers its hosted endpoint (https://oyabrowser.com/mcp/pool).
Is the Oya Browser MCP server safe to use?
Oya Browser scores 84 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 Oya Browser MCP server expose?
Oya Browser exposes 32 tools: select_option, run_script, wait_for, find, hover, and 27 more. Their descriptions and schemas cost roughly 1,880 tokens of context every time the server is loaded.
Does the Oya Browser MCP server require authentication?
Yes. Oya Browser asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Oya Browser MCP server still maintained?
Oya Browser is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Oya Browser MCP server?
VerifyMCP ran 13 checks on Oya Browser, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.