Ghostdom

io.github.walkojas-boopPublished by GitHub account walkojas-boopv1.0.0Updated Oct 24, 2026

Headless-browser-as-JSON with memorymarket cache economics. Real Chromium, crypto settlement.

VerifiedStreamable HTTPWeb executableBrowser AutomationFinance

Overview

AI-generated overview

A remote MCP endpoint that exposes a headless Chromium browser as JSON, with a cache layer described as having memory-market economics and crypto settlement.

What you can do
The registry description says it provides a headless browser as JSON, backed by real Chromium, and mentions a memory-market cache with crypto settlement. No tool list, parameters, or usage documentation is provided, so the exact operations an assistant could call are not specified. It is offered as a remote streamable HTTP endpoint rather than a local package.
When to use it
Consider it only if you specifically want a hosted headless-browser service reachable over MCP and are willing to evaluate it without published tool documentation. For most browser-automation needs, a server with a documented tool list is easier to assess.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the provider's endpoint. The manifest declares no authentication, no environment variables, and no headers, and no packages are listed. Network access to the endpoint is required.
Before you install
The description mentions crypto settlement, which suggests payments or spending may be involved, but no pricing, wallet, or payment details are documented. No authentication is declared, so it is unclear who can use the endpoint or what it logs. Because no tool list is published, what the browser does with pages, credentials, or data cannot be verified before connecting.

Installation

In SourceWeft

  1. Open Ghostdom in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.walkojas-boop%2Fghostdom/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "ghostdom": {
      "type": "http",
      "url": "https://ghostdom.jason-12c.workers.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft read this server and it lists no tools.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.