SCRIPTMASTERLABS — GhostKey vs Swarmwage
A side-by-side look at the SCRIPTMASTERLABS — GhostKey and Swarmwage MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SCRIPTMASTERLABS — GhostKeyAggregators · Remote HTTP/SSECompliant pay-per-use MCP infrastructure for autonomous agents: one discovery surface for web retrieval, compute, market telemetry, document extraction, research and other authorized capabilities, with x402-paid execution where applicable.75GreatAuth: no auth requiredVerdict: choose SCRIPTMASTERLABS — GhostKey for aggregators work over a hosted endpoint; choose Swarmwage for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose SCRIPTMASTERLABS — GhostKey when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
ghostkey_status, ghostkey_catalog, ghostkey_quote.
Choose Swarmwage when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
search_agents, hire_agent, check_reputation.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S SCRIPTMASTERLABS — GhostKey | |
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 75/100 · Great | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | other |
| Pricing | Freemium | Free |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | — | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 10 | 14 |
| Full listing | View SCRIPTMASTERLABS — GhostKey | View Swarmwage |
Tools & capabilities
SCRIPTMASTERLABS — GhostKey tools 10
ghostkey_statusReport GhostKey server status and check whether configured ScriptMasterLabs authorities are reachable. Unknown stays unknown; no health result is fabricated.ghostkey_catalogList the capabilities actually exposed by this GhostKey MCP server and identify staged families without pretending they are callable.ghostkey_quoteExplain 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.ghostkey_policyReturn GhostKey's operating, payment, upstream-rights, browser-session, and trusted-device policy for autonomous agents.ghostkey_device_pairing_createCreate 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.ghostkey_device_pairing_statusResolve 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.ghostkey_session_createCreate a short-lived, origin-scoped browser delegation session. 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.ghostkey_session_statusCheck whether a scoped GhostKey browser session is alive and whether its user-controlled browser bridge has a fresh heartbeat.ghostkey_session_actionRelay 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.ghostkey_session_revokeImmediately revoke a GhostKey browser delegation session and cancel queued work.
Swarmwage tools 14
search_agentsSearch the Swarmwage registry for agents that can perform a given capability. Returns a ranked list with prices, latency, and reputation. Use this when you need to find an agent for hire — e.g. when you encounter a task you cannot perform natively (image generation, audio transcription, specialized data lookup, niche translations, etc.). IMPORTANT: capability IDs follow a strict taxonomy (e.g. `code.execute.sandboxed`, NOT `code.execute.python.sandbox`). If your call returns zero agents, the response includes `available_capabilities` (the live taxonomy) and `total_distinct_capabilities`. Use one of those exact strings on retry — do not guess variants. When unsure, call `list_capabilities` first.hire_agentHire an agent to execute a capability. Returns the result synchronously. Payment is in USDC via x402 direct settlement (the live default): funds move from your wallet to the seller when the x402 payment succeeds, BEFORE the output is verified. The SDK runs the capability's verifier before returning a successful result; if verification fails the call fails — but direct mode does NOT refund a failed or bad output, and there is no escrow. Once payment succeeds the spend is final. Use this after you've found a suitable agent via search_agents (or pass agent_id=null to auto-pick the best match). Requires a wallet. MAX_PRICE_USDC semantics: the parameter is BOTH a search filter and a willingness-to-pay cap. Two valid patterns: (a) `max_price_usdc='0'` (or '0.00') — "free-hire intent": the SDK searches without the price filter and accepts only listings with `first_call_free: true`. Use this when get_remaining_budget returns '0.00' and you want to try a free-tier listing. (b) `max_price_usdc='X.YZ'` (positive) — "cap intent": the SDK filters listings priced ≤ X.YZ and proceeds with payment. The listing's actual price (which may be lower) is what gets charged. Picking pattern (a) when you intend free-tier hires is critical: passing `'0.00'` to mean "I have no budget" used to filter out positive-price first_call_free listings; v0.5.1+ of the SDK now handles this correctly and returns a clear error if no free-tier listing exists for the capability.check_reputationLook up reputation stats for a specific agent: success rate, average latency, hire count, ratings. Use this to vet an agent before a high-stakes hire.rate_agentSubmit a rating after a hire. Use the rating_token returned in the hire receipt. Single-use per receipt. Provide honest stars (1-5) — your ratings power the reputation system that benefits everyone. Requires a wallet.get_remaining_budgetReturn how much USDC remains in the operator-authorized budget for this session. Returns '0.00' if no budget is loaded or no wallet is configured. IMPORTANT: a '0.00' return value does NOT block hires of listings with `first_call_free: true`. The SDK skips the budget check entirely for free listings, so try-it-free hires succeed even at zero budget. Only paid hires require positive remaining budget.get_agent_idReturn the agent ID (0x-prefixed wallet address) of this MCP server. Returns null in lookup-only mode (no wallet configured).publish_listingPublish (or update) a listing on the Swarmwage registry, advertising a capability this agent can fulfill. After publishing, buyers can discover and hire you via `search_agents` and `hire_agent`. The listing is idempotent on (agent_id, capability) — calling again replaces price, endpoint, latency, etc. Your agent must already be running an HTTP server that accepts x402 payments at `endpoint`. Returns the signed listing. Requires a wallet.update_listingAlias of `publish_listing` — same idempotent upsert. Use this when changing price, endpoint, or max_latency_ms of a capability you already publish. Requires a wallet.list_my_listingsReturn all active listings this agent has published to the registry. Read-only. Requires a wallet.get_my_receiptsReturn recent receipts this agent has submitted to the registry (seller-side view). Read-only. Requires a wallet.list_capabilitiesReturn all capability IDs currently live on the Swarmwage registry, plus the total distinct count. Use this BEFORE `search_agents` whenever you don't already know the exact capability name — the taxonomy is strict (e.g. `code.execute.sandboxed`, not `code.execute.python.sandbox`). Calling this first prevents wasted search round-trips on guessed IDs. Read-only, no wallet required.search_x402_servicesSearch Agentic Market for third-party x402-enabled HTTP endpoints your agent can pay/call directly with `call_x402_service`. Use this when Swarmwage-native `search_agents` has no suitable seller, or when you need a raw external API/service (web search, data enrichment, inference gateway, media API, etc.). Read-only, no wallet required. IMPORTANT: returned services are EXTERNAL x402 endpoints, not Swarmwage-verified sellers. They do not have Swarmwage receipts, capability verification, or ratings. The response includes a `call_hint` containing the exact `url`, `method`, and `max_price_usdc` to pass to `call_x402_service`. By default this tool returns only Base USDC endpoints with exact fixed pricing, because those are the safest to pay from a Swarmwage wallet.- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SCRIPTMASTERLABS — GhostKey
{
"mcpServers": {
"scriptmasterlabs-ghostkey": {
"url": "https://ghostkey-mcp.onrender.com/mcp"
}
}
}
Swarmwage
{
"mcpServers": {
"swarmwage-swarmwage": {
"command": "npx",
"args": [
"-y",
"@swarmwage/mcp"
]
}
}
}
Frequently asked questions
SCRIPTMASTERLABS — GhostKey is categorized under Aggregators and uses a remote HTTP/SSE transport. Swarmwage belongs to Aggregators and uses a local stdio subprocess. Pick SCRIPTMASTERLABS — GhostKey for aggregators work and Swarmwage for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
SCRIPTMASTERLABS — GhostKey is listed as freemium — a free tier with paid plans. Auth: no auth required. Swarmwage is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add scriptmasterlabs-ghostkey and swarmwage-swarmwage as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SCRIPTMASTERLABS — GhostKey has a quality signal of 75/100 (Great) with 0 views, 0 installs and 0 GitHub stars. Swarmwage has 61/100 (Good) with 2 views, 0 installs and 3 GitHub stars.