WebMCP Registry site · v0.18.35
Use Sema with your agent.
Sema (sema.run) registers 17 WebMCP tools. Sema lists 17 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 sema.run, last live-checked by the registry at 2026-09-22T21:30:35.781Z. Run ghostget webmcp sites.get --input '{"domain":"sema.run"}' --json for the current schema; the listing can drift between checks.
Use Sema 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 --jsonRead the live tool schema — every registered tool, its input schema, annotations, and the page that publishes it:
ghostget webmcp sites.get --input '{"domain":"sema.run"}' --jsonCall 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 statusRegistered WebMCP tools
Sema publishes 17 tools on sema.run; 0 declare readOnlyHint.
| Tool | What it does | Callable through Ghostget |
|---|---|---|
continue_debugging | Continue the paused Sema debugger and wait for the next breakpoint, finish, or error. | Listed for discovery; the registry allows read-only calls only |
find_examples | Find bundled Sema examples by filename, category, or identifier. Returns identifiers accepted by load_example. | Listed for discovery; the registry allows read-only calls only |
format_editor | Format and replace the current Sema source in the editor. This does not run the code. | Listed for discovery; the registry allows read-only calls only |
get_debug_state | Read debugger status, active line, breakpoints, locals, and stack frames. | Listed for discovery; the registry allows read-only calls only |
list_files | List the immediate children of one virtual filesystem directory. The listing is non-recursive. | Listed for discovery; the registry allows read-only calls only |
load_example | Replace the editor with one bundled Sema example selected by identifier or filename. This does not run the code. | Listed for discovery; the registry allows read-only calls only |
read_editor | Read Sema source from the playground editor. Use this before editing or running unfamiliar code. | Listed for discovery; the registry allows read-only calls only |
read_file | Read a character range from a UTF-8 text file in the playground virtual filesystem. | Listed for discovery; the registry allows read-only calls only |
read_output | Read the current playground output, including values, printed lines, errors, and timing. | Listed for discovery; the registry allows read-only calls only |
run_editor | Run the current Sema source, using the worker runtime when available, and wait for evaluation to finish. | Listed for discovery; the registry allows read-only calls only |
set_breakpoints | Replace all debugger breakpoints with one-based lines, snapping requests to executable source lines. | Listed for discovery; the registry allows read-only calls only |
start_debugging | Start debugging the current Sema source and wait for a pause, finish, or error. | Listed for discovery; the registry allows read-only calls only |
step_debugger | Step the paused Sema debugger into, over, or out, then wait for its next stable state. | Listed for discovery; the registry allows read-only calls only |
stop_debugging | Stop the active Sema debugger and return the playground to its idle state. | Listed for discovery; the registry allows read-only calls only |
stop_run | Cancel the active worker-backed Sema evaluation when one is running. | Listed for discovery; the registry allows read-only calls only |
write_editor | Replace the entire playground editor with Sema source. This does not run the code. | Listed for discovery; the registry allows read-only calls only |
write_file | Create or overwrite a UTF-8 virtual file, creating parent directories as needed. Content is limited to 1 MiB. | 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 Sema changes its tools. - No account needed. These calls are credential-free registry reads. For tools that need a session on sema.run, browse the site itself or check back when the registry lists more tools.