Spicrawl

Browser (CDP) connect URL

spicrawl_browser_connect_url

Coming soon: remote browsers are not available yet, so minting fails; do not rely on this tool. For scripted page interaction today use actions on spicrawl_scrape. Mints a single-use connect URL for Spicrawl's remote browser (GET /v1/browser, a DevTools Protocol (CDP) WebSocket) so YOUR code can drive it with any CDP client, using the URL as the browser WebSocket endpoint. It calls POST /v1/browser/token and returns a ws:// or wss:// URL carrying a short-lived token, never the API key: the URL works ONCE, within 60 seconds, and only with the options given here (editing them in the URL is refused), so call this right before connecting and again for every new session. Prefer sending the key as an Authorization header when the client supports headers on the WebSocket upgrade: then connect to the plain /v1/browser URL with 'Authorization: Bearer ' and no token is needed. The endpoint exists only when the deployment was installed with --with-cdp, and the key must carry the browser scope; otherwise minting fails (404 or 403). Parameter errors are reported when minting.

Input Schema

TableJSON Schema

Name	Required	Description
`proxy`	No	Your own proxy, as http://user:pass@host:port. Replaces our pool, so proxy_country, proxy_region and sticky_key cannot be combined with it. Kept out of the returned URL.
`engine`	No	Rendering tier of the remote browser: `browser` (full browser, full protocol; the default) or `js` (lighter JavaScript rendering with a smaller protocol surface). A tier your plan does not include is refused.
`sticky_key`	No	Keep one exit IP for the session under this key (2-64 letters, digits, hyphens). Omit to rotate (the default).
`session_ttl`	No	Session lifetime in seconds, 60-900. Default 180.
`proxy_region`	No	Broader exit region/pool name; 'global' means no constraint. Mutually exclusive with proxy_country.
`proxy_country`	No	Exit country, ISO-3166 alpha-2 lowercase (e.g. 'de'). Mutually exclusive with proxy_region.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	ws:// or wss:// connect URL carrying a single-use token (never the API key); use it as the CDP browser WebSocket endpoint.
`notes`	No	Usage notes for the connect URL.
`expires_at`	No	When the token expires, RFC 3339 UTC (60 s after minting).
`single_use`	Yes	Always true: the URL works for one connection.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "expires_at": {
+      "description": "When the token expires, RFC 3339 UTC (60 s after minting).",
+      "type": "string"
+    },
+    "notes": {
+      "description": "Usage notes for the connect URL.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "single_use": {
+      "description": "Always true: the URL works for one connection.",
+      "type": "boolean"
+    },
+    "url": {
+      "description": "ws:// or wss:// connect URL carrying a single-use token (never the API key); use it as the CDP browser WebSocket endpoint.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "single_use"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedOct 13, 2026

changedInput schema / properties / engine / description

Previous value: -"Browser engine. Default: the deployment's default (chromium). 'obscura' cannot run headful."New value: +"Rendering tier of the remote browser: `browser` (full browser, full protocol; the default) or `js` (lighter JavaScript rendering with a smaller protocol surface). A tier your plan does not include is refused."

changedInput schema / properties / engine / enum

Previous value: -[
-  "chromium",
-  "obscura"
-]New value: +[
+  "browser",
+  "js"
+]

removedInput schema / properties / headless

Removed value: -{
-  "description": "false = headful browser with a display (desktop-sized screen). Omit for the deployment default.",
-  "type": "boolean"
-}

First observedOct 1, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Despite annotations covering safety hints, the description adds substantial behavior beyond them: single-use URL, 60-second window, options locked into the token (URL edits refused), token never exposes the API key, endpoint requires --with-cdp, key needs `browser` scope, and 404/403 failure modes. This is unusually rich disclosure for a token-minting tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the critical 'coming soon, do not rely' warning, which is the most important thing an agent can read. The body is dense and every clause carries operational detail, though it is long and could be tightened slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't explain return values, and it still covers auth, scope requirements, deployment prerequisite, token lifetime, single-use constraint, and failure codes. Nothing an agent needs to call or avoid this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all six parameters including enums, patterns, ranges, and mutual exclusions. The description only echoes this at a high level ('only with the options given here') without adding syntax or semantics beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Mints a single-use connect URL for Spicrawl's remote browser'), names the underlying endpoint, and distinguishes itself from the sibling alternative ('use `actions` on spicrawl_scrape'). An agent immediately knows what it does and that it is currently non-functional.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when NOT to use it ('Coming soon... do not rely on this tool') and routes to the working alternative for scripted page interaction today. It also gives the timing rule (call right before connecting, again per session) and the Authorization-header variant.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Spicrawl tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?