SCRIPTMASTERLABS — GhostKey MCP
REMOTE · GHOSTKEY-MCP.ONRENDER.COM
Remote MCP for compliant pay-per-use agent capabilities with x402 execution.
Available components
Last scanned (1 hour ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Browser Automation
Recent critical change
Authorization (1 Nov 2026). See the changelog before you install this server.
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (ghostkey_session_action). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 657 tokens (~65/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 −2
- Authorization: unverified → fail ▼ critical
- Stability: 0.10 → unverified ▼ security
- New tool “ghostkey_session_action”, which the server declares destructive security
- New tool “ghostkey_session_revoke”, which the server declares destructive security
- Tool “ghostkey_catalog” rewrote its description, which is the text the model reads security
- Tool “ghostkey_policy” rewrote its description, which is the text the model reads security
- Tool “ghostkey_status” rewrote its description, which is the text the model reads security
- Schema quality: 37 → 65 ▼ functional
- Schema quality: good → fair functional
- Destructive annotations: pass → 100 functional
- Server version: 0.1.1 → 0.3.1 functional
- New tool “ghostkey_device_pairing_create” functional
- New tool “ghostkey_device_pairing_status” functional
- New tool “ghostkey_session_create” functional
- New tool “ghostkey_session_status” functional
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 0.1.1 functional
- 2 Sept 26 61
First indexed and scored.
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 5 Nov 2026 · Probed https://ghostkey-mcp.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ghostkey-mcp.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ghostkey-mcp.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://ghostkey-mcp.onrender.com/mcp | HTTPS enforced | 301 | https://ghostkey-mcp.onrender.com/mcp |
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 →
ghostkey_catalog ~30
List the capabilities actually exposed by this GhostKey MCP server and identify staged families without pretending they are callable.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ghostkey_device_pairing_create ~60
Create a one-time trusted-device enrollment capability. Requires GhostKey persistent trusted-device storage to be configured. The browser generates its own non-exportable P-256 private key; only the public key is uploaded.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | – |
No output schema declared.
No examples provided.
ghostkey_device_pairing_status ~59
Resolve a one-time trusted-device pairing after the browser has enrolled. Requires the original pairing ID and pairing code and is available only until that pairing capability expires.
| Name | Type | Req | Description |
|---|---|---|---|
| pairing_code | string | yes | – |
| pairing_id | string | yes | – |
No output schema declared.
No examples provided.
ghostkey_policy ~32
Return GhostKey's operating, payment, upstream-rights, browser-session, and trusted-device policy for autonomous agents.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ghostkey_quote ~54
Explain how to obtain authoritative pricing for a GhostKey/SML paid capability. Pricing and settlement destination come from the fresh live HTTP 402 challenge, never a copied wallet or stale fixed price.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | – |
No output schema declared.
No examples provided.
ghostkey_session_action ~132
Relay one authorized browser action into the user's already-authenticated browser. Actions: navigate, inspect, click, input, select, read, wait. Password/hidden fields and off-allowlist navigation are denied. API and bridge documentation: https://ghostkey-mcp.onrender.com/session-bridge/README.txt.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| agent_token | string | yes | – |
| attribute | string | – | – |
| selector | string | – | – |
| session_id | string | yes | – |
| text | string | – | – |
| timeout_ms | integer | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
ghostkey_session_create ~167
PAID tool ($0.10 USDC via x402 v2, Base). Create a short-lived, origin-scoped browser delegation session. Send the x402 PAYMENT-SIGNATURE header on the /mcp request; without payment the call returns the live x402 challenge (HTTP 402, amount 100000 = $0.10 USDC, network eip155:8453). Actions inside a minted session are unmetered. Optionally target a previously enrolled trusted device using its private 256-bit routing capability so its extension can claim the session automatically. The user still handles login/CAPTCHA and any new browser-origin permission themselves.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_origins | array | yes | – |
| trusted_device_id | string | – | – |
| ttl_seconds | integer | – | – |
No output schema declared.
No examples provided.
ghostkey_session_revoke ~40
Immediately revoke a GhostKey browser delegation session and cancel queued work.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | yes | – |
| session_id | string | yes | – |
No output schema declared.
No examples provided.
ghostkey_session_status ~48
Check whether a scoped GhostKey browser session is alive and whether its user-controlled browser bridge has a fresh heartbeat.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | yes | – |
| session_id | string | yes | – |
No output schema declared.
No examples provided.
ghostkey_status ~35
Report GhostKey server status and check whether configured ScriptMasterLabs authorities are reachable. Unknown stays unknown; no health result is fabricated.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the SCRIPTMASTERLABS — GhostKey MCP server?
SCRIPTMASTERLABS — GhostKey MCP is a hosted endpoint at https://ghostkey-mcp.onrender.com/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 · ghostkey-mcp.onrender.com
claude mcp add --transport http com-scriptmasterlabs-ghostkey 'https://ghostkey-mcp.onrender.com/mcp'
What is the SCRIPTMASTERLABS — GhostKey MCP server?
SCRIPTMASTERLABS — GhostKey MCP is listed in the public MCP registry as com.scriptmasterlabs/ghostkey. Remote MCP for compliant pay-per-use agent capabilities with x402 execution. This page covers its hosted endpoint (https://ghostkey-mcp.onrender.com/mcp).
Is the SCRIPTMASTERLABS — GhostKey MCP server safe to use?
SCRIPTMASTERLABS — GhostKey MCP scores 61 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 SCRIPTMASTERLABS — GhostKey MCP server expose?
SCRIPTMASTERLABS — GhostKey MCP exposes 10 tools: ghostkey_status, ghostkey_catalog, ghostkey_quote, ghostkey_policy, ghostkey_device_pairing_create, and 5 more. Their descriptions and schemas cost roughly 657 tokens of context every time the server is loaded.
Does the SCRIPTMASTERLABS — GhostKey MCP server require authentication?
No. We connected to SCRIPTMASTERLABS — GhostKey MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SCRIPTMASTERLABS — GhostKey MCP server still maintained?
SCRIPTMASTERLABS — GhostKey MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.