WebMCP Registry site · v0.18.35
Use Considus with your agent.
Considus (considus.com) registers 6 WebMCP tools. Considus 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 considus.com, last live-checked by the registry at 2026-09-21T21:23:40.739Z. Run ghostget webmcp sites.get --input '{"domain":"considus.com"}' --json for the current schema; the listing can drift between checks.
Use Considus 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":"considus.com"}' --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
Considus publishes 6 tools on considus.com; 0 declare readOnlyHint.
| Tool | What it does | Callable through Ghostget |
|---|---|---|
get_install_prerequisites_and_commands | Returns the prerequisites and the exact install commands for one Considus MCP server, for macOS, Linux and Windows, quoted from the project README. It also explains how the MCP client configuration is produced, which is by a setup script on | Listed for discovery; the registry allows read-only calls only |
get_journal_post | Returns one Considus journal post as text, given its slug. Slugs come from search_journal. A long post is shortened and the canonical URL is always included, so the full text can be fetched or cited from there. | Listed for discovery; the registry allows read-only calls only |
get_mcp_server_overview | Returns what one Considus MCP server does, what it needs in order to run, what it deliberately does not do, and its licence and URLs. Use this when a user is deciding whether a server fits their situation. If they have already decided and w | Listed for discovery; the registry allows read-only calls only |
list_mcp_servers | Lists every MCP server Considus publishes, with each one's purpose, licence, version, repository URL and documentation URL. Call this when a user asks what Considus makes or which MCP servers it offers, and call it before the other server t | Listed for discovery; the registry allows read-only calls only |
search_considus_docs | Searches the Considus documentation: both MCP servers' full documentation, plus the about, FAQ, support and Catchlight pages. Returns matching sections with their heading, a short excerpt and the page URL. Use this for a specific question a | Listed for discovery; the registry allows read-only calls only |
search_journal | Searches the Considus journal, which is the studio's writing on privacy, craft and building software slowly. Returns matching posts with title, publication date, a short excerpt and the URL. Use this when a user asks what Considus thinks ab | 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 Considus changes its tools. - No account needed. These calls are credential-free registry reads. For tools that need a session on considus.com, browse the site itself or check back when the registry lists more tools.