WebMCP Registry site · v0.18.35
Use turva.dev with your agent.
turva.dev (turva.dev) registers 6 WebMCP tools. turva.dev lists 6 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 turva.dev, last live-checked by the registry at 2026-09-23T03:20:44.791Z. Run ghostget webmcp sites.get --input '{"domain":"turva.dev"}' --json for the current schema; the listing can drift between checks.
Use turva.dev 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":"turva.dev"}' --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
turva.dev publishes 6 tools on turva.dev; 0 declare readOnlyHint.
| Tool | What it does | Callable through Ghostget |
|---|---|---|
get_company | Return the registered business details for turva.dev: trading name, the operator who does the work, the Finnish Business ID, the country and city of registration, and the LinkedIn profile. | Listed for discovery; the registry allows read-only calls only |
get_contact | Return the official contact channels for turva.dev, including email, Signal and LinkedIn. Engagement is async only, so there is no phone number and no meeting booking. | Listed for discovery; the registry allows read-only calls only |
get_page | Return the markdown source of one page on turva.dev, byte for byte the text a person reads on that page. Takes a path on this site, for example /guides/llms-txt or /agent-readiness-audit. Read-only. The path is resolved against this site an | Listed for discovery; the registry allows read-only calls only |
get_services | Return the services offered by turva.dev (Shopify agent storefront check, audit, advisory, implementation, agent operations, MCP server design) as the full services page in markdown, together with fixed prices in EUR for the four priced ser | Listed for discovery; the registry allows read-only calls only |
open_page | Navigate this browser tab to a named page on turva.dev, so the person sees it. Accepts one of the named pages only, never a URL, and it never leaves this site. Use get_page instead when you only need to read the text. | Listed for discovery; the registry allows read-only calls only |
search_content | Search the turva.dev page index for guides, blog posts and pages whose title matches a query, and return each match as a title with the page URL and the markdown URL of the same page. Read-only, and it reads the published llms.txt index rat | 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 turva.dev changes its tools. - No account needed. These calls are credential-free registry reads. For tools that need a session on turva.dev, browse the site itself or check back when the registry lists more tools.