Semantic capability discovery
Natural-language intent maps to relevant WebMCP tools across the indexed web, even when the requester does not know which site provides them.
WebMCPify Search · Developer preview
Search the agentic web by intent. Discover the right WebMCP capability across indexed websites and call it directly when supported—from the web UI, an AI agent, or an MCP client.
Agents shouldn't need to know which website to visit before they know what it can do.
CONNECTED Indexed capability search is connected. AI summaries require verified access; live answers also require your explicit request and a ready Search browser.
Relevant WebMCP capabilities will appear here with schemas, permissions, provenance, freshness, health, and supported invocation paths.
No sample results are shown as real data.Capability search + execution
Improvisus Search begins with the outcome a human or agent wants—not a website they already know. It returns actionable capability contracts, not merely website listings.
Natural-language intent maps to relevant WebMCP tools across the indexed web, even when the requester does not know which site provides them.
The visual Search page is one interface. Agents can use the same engine programmatically through this page’s WebMCP tools or the Search MCP server.
A selected capability can be called when its live invocation path is supported. Search can summarize indexed capability descriptions or combine results from relevant, verified, read-only website calls into a sourced AI answer.
Search reads the latest indexed records. Each capability includes its source, last-discovered and last-tested dates, and verification status. Stale or untested entries remain labeled until updated.
The complete Search loop
Search carries source, schema, permission, health, and invocation context through the flow. A tool's success response alone is not proof of the outcome.
Express the natural-language intent.
Search capabilities across the indexed WebMCP web.
Discover and inspect the relevant capability contract.
Select the right website tool and supported invocation path.
Call the capability through Guard when supported and approved.
Return the result or a grounded AI-generated answer with verification context.
One engine · four working interfaces
Humans can search visually. Agents and MCP clients can search, inspect, select, and request supported calls programmatically. Live website actions stay on the guarded path, where consent and verification can be applied.
People can search by intent, inspect complete capability contracts, and request an applicable verified read-only call.
Use Search in a WebMCP capable Chrome browser with an agent, or through a compatible browser extension. The agent can discover this page’s Search tools and receive structured capability results.
The public Search MCP server exposes capability search, exact contracts, site details, and site inventories. Authorized agents can explicitly request live read-only execution through the search tool.
With verified access and explicit consent, Search calls relevant read-only WebMCP tools on their actual websites and combines the returned data with sources and tool outcomes.
Connect your agent
Add this remote server to your MCP client. No local Search installation or browser extension is required; live website calls run in the Search service’s browser.
AI access through API/MCP requires a requested agent key. Both AI modes are also available in web search when its authorized connection is ready. How summaries and live execution work →
https://search.improvisus.tech/mcpTransport: Streamable HTTP. Choose a remote HTTP server in your client, paste the URL, then connect and list its tools.
With Claude Code installed, run this in your terminal. The user scope makes the connection available across your projects. No Search API key is needed for discovery.
claude mcp add --transport http --scope user webmcpify-search https://search.improvisus.tech/mcpRun claude mcp get webmcpify-search to inspect the configuration. Inside Claude Code, use /mcp to check the connection and available tools.
Once you receive a key, update the server entry in your private ~/.claude.json user configuration. Replace the placeholder with your own key and keep that file private.
{
"mcpServers": {
"webmcpify-search": {
"type": "http",
"url": "https://search.improvisus.tech/mcp",
"headers": {
"Authorization": "Bearer YOUR_AGENT_KEY"
}
}
}
}With OpenAI Codex CLI installed, add the remote server. This uses your local Codex configuration, shared with the IDE extension. No Search API key is needed for discovery.
codex mcp add webmcpify-search --url https://search.improvisus.tech/mcpRun codex mcp list, then start a new Codex session and use /mcp to check the connection and tools. Restart the IDE extension if it was already open.
Once you receive a key, update the existing server entry in ~/.codex/config.toml to read it from an environment variable:
[mcp_servers.webmcpify-search]
url = "https://search.improvisus.tech/mcp"
bearer_token_env_var = "WEBMCPIFY_SEARCH_AGENT_KEY"Replace the placeholder below with your key and start Codex from that terminal. For the IDE extension, make the variable available to the process launching your editor.
export WEBMCPIFY_SEARCH_AGENT_KEY="YOUR_AGENT_KEY"
codexThis is a WebMCPify agent key, not an OpenAI API key. Leave the bearer-token setting out when using anonymous discovery.
For another MCP client, use its remote server settings with the same URL and transport.
Discovery is public. No key is needed to find capabilities or inspect their contracts. For discovery-only searches, explicitly set summarize: false and execute: false.
Request a key for AI capability summaries and live AI answers through the API or MCP. Add this custom header in your client, replacing the placeholder with your own key:
Authorization: Bearer YOUR_AGENT_KEYSummary access needs search:read and search:ai; live answers also need search:execute. Request an agent key if you do not have one.
Both summary modes are also available in web search. Choose Capability summary to explain indexed tools, or Live AI answer to call eligible website tools and summarize their current results. The web app uses its authorized connection when available; you do not need to paste a personal agent key into the page.
Ask your agent: “Use WebMCPify Search to tell me about Improvisus. Discover matching capabilities only; do not generate a summary or call website tools.”
The agent calls search_webmcp_capabilities with:
{
"query": "Tell me about Improvisus",
"limit": 10,
"summarize": false,
"execute": false
}For an indexed AI summary, set summarize: true. For an explicitly requested live answer, set execute: true: Search calls eligible read-only tools on the matching websites and returns a sourced answer plus each tool outcome. Keys and quotas still apply; unrelated or ineligible tools are not executed.
search_webmcp_capabilitiesquery, limit (default 10, maximum 50), summarize, execute, and optional verification/action filters.get_webmcp_capabilitycapabilityId returned by search.list_site_webmcp_capabilitiessiteId; this does not call those website tools.get_webmcp_sitesiteId.Having trouble? Use the full HTTPS URL ending in /mcp. For a 401/403 response, check your key, expiry, scopes, and whether AI was requested. For 429, wait for the limit to reset. A connected MCP client can still discover capabilities when live execution is unavailable.
search_web_capabilitiesget_capability_detailsget_site_detailslist_site_capabilitiesget_capability_healthsubmit_webmcp_siteinvoke_web_capabilityThe MCP server works with clients that support Streamable HTTP and, for AI access, custom authorization headers. A dedicated ChatGPT integration remains in development.