WebMCP Registry site · v0.18.35
Use MiroShark with your agent.
MiroShark (miroshark.xyz) registers 8 WebMCP tools. MiroShark lists 8 tools but declares none as read-only today, so tools.call cannot invoke them yet. Ask sites.get for the live status before planning a call.
This page mirrors the WebMCP Registry listing for miroshark.xyz, last live-checked by the registry at 2026-09-21T20:47:21.633Z. Run ghostget webmcp sites.get --input '{"domain":"miroshark.xyz"}' --json for the current schema; the listing can drift between checks.
Use MiroShark with my agent
Ghostget's bundled webmcp adapter speaks to the public WebMCP Registry, so an agent always reads this site's current tool schema instead of a stale hard-coded copy. Install v0.18.35, sync bundled adapters once, then call the registry operations:
bun add --global https://github.com/hraness/ghostget/releases/download/v0.18.35/hraness-ghostget-0.18.35.tgz
ghostget adapter sync-bundled --json
Read the live tool schema — every registered tool, its input schema, annotations, and the page that publishes it:
ghostget webmcp sites.get --input '{"domain":"miroshark.xyz"}' --json
Call a read-only tool — the registry refuses anything not declared readOnlyHint and returns the site's answer as untrusted content:
# no read-only-callable tools listed today; sites.get shows the live status
Registered WebMCP tools
MiroShark publishes 8 tools on miroshark.xyz; 0 declare readOnlyHint.
| Tool | What it does | Callable through Ghostget |
|---|---|---|
ask_miroshark | Ask a natural-language question about MiroShark and get ranked, cited resources from its pages (what it is, how to run it, pricing, docs, ecosystem). Same ranking as the public /ask endpoint. | Listed for discovery; the registry allows read-only calls only |
get_ecosystem | The projects and partners building with MiroShark, parsed from the canonical ECOSYSTEM.md. | Listed for discovery; the registry allows read-only calls only |
get_health | MiroShark site readiness: whether the process booted and which feature areas are configured (booleans only, never secret values). | Listed for discovery; the registry allows read-only calls only |
miroshark_overview | What MiroShark is and when to use it. Returns a short description of the swarm-simulation engine and the kinds of questions it answers. | Listed for discovery; the registry allows read-only calls only |
miroshark_resources | Key MiroShark developer resources: machine contract (OpenAPI), integration docs, authentication, MCP server, site map, and socials. | Listed for discovery; the registry allows read-only calls only |
miroshark_run | How to run a MiroShark simulation, including the price and the x402 payment flow. | Listed for discovery; the registry allows read-only calls only |
open_run_panel | Open MiroShark's run panel with a scenario pre-loaded, and take the user there. Use this to act on a user's request to run/simulate something: pass a seed (prompt, url, OR article; prompt wins if several are given) and, optionally, a predic | Listed for discovery; the registry allows read-only calls only |
suggest_scenarios | Turn a vague topic into up to 5 concrete, launchable MiroShark scenarios (title, pitch, ready-to-run prompt, angle). A free pre-flight before paying for a run - use it to help a user go from a fuzzy idea to a seed prompt worth simulating. P | Listed for discovery; the registry allows read-only calls only |
What to expect
- Read-only only. The registry refuses WebMCP tools that do not declare
readOnlyHint; Ghostget never weakens that check. - Untrusted results. Tool output is site content, not instructions — treat it as data.
- Live schemas.
sites.getalways returns the schema the registry saw most recently, so agents adapt when MiroShark changes its tools. - No account needed. These calls are credential-free registry reads. For tools that need a session on miroshark.xyz, browse the site itself or check back when the registry lists more tools.