io.github.Shreyas-Profile/browser-mcp
REMOTE · BROWSER.REGIQ.IN
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Available components
Last scanned (42 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 30 Aug 2026.
Category Browser Automation
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 6 Sept 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 5 Sept 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Sept 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Sept 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Sept 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Aug 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 30 Aug 26 −10
- Endpoint reachability: unreachable → not serving MCP ▼ security
- HSTS header: unverified → fail ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 29 Aug 26 0
- Endpoint reachability: behind authorisation → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. 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 6 Sept 2026 · Probed https://browser.regiq.in/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=regiq.in | CN=YE1,O=Let's Encrypt,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 58256ea8ec13b3e3285458d3a2961f403d4 |
| SANs: *.regiq.in, regiq.in | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 browser.regiq.in. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| in. | present | 10094 | 13 | Verified |
| regiq.in. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://browser.regiq.in/api/mcp | Unreachable | ||
| http (plaintext) | http://browser.regiq.in/api/mcp | HTTPS enforced |
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 →
No tool schema has been captured from this endpoint yet.
How do I install the io.github.Shreyas-Profile/browser-mcp server?
io.github.Shreyas-Profile/browser-mcp is a hosted endpoint at https://browser.regiq.in/api/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 · browser.regiq.in
claude mcp add --transport http shreyas-profile-browser-mcp 'https://browser.regiq.in/api/mcp'
What is the io.github.Shreyas-Profile/browser-mcp server?
io.github.Shreyas-Profile/browser-mcp is listed in the public MCP registry as io.github.Shreyas-Profile/browser-mcp. Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot. This page covers its hosted endpoint (https://browser.regiq.in/api/mcp).
Is the io.github.Shreyas-Profile/browser-mcp server safe to use?
io.github.Shreyas-Profile/browser-mcp scores 0 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.
Does the io.github.Shreyas-Profile/browser-mcp server require authentication?
Its publisher declares no required credentials for io.github.Shreyas-Profile/browser-mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.Shreyas-Profile/browser-mcp server still maintained?
io.github.Shreyas-Profile/browser-mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 30 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.