WebMCPify Search · Developer preview

The first of its kind: a live WebMCP capability search and execution engine.

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.

SEARCH / CAPABILITY ENGINEILLUSTRATIVE
INTENTFind red wines under $30 across Shopify Liquid storefronts
Search wine catalogsShopify Liquid · search_catalog
MATCH
Check price & availabilityShopify Liquid · get_product
SUPPORTED CALLGUARD CHECK
selectapproveinvoke
Result returned with source + verification context
From intent to a supported, approved capability call.
Matching capabilities
LIVE CAPABILITY INDEX

Start with an intent—not a website.

Relevant WebMCP capabilities will appear here with schemas, permissions, provenance, freshness, health, and supported invocation paths.

No sample results are shown as real data.

Direct submission

Submit a WebMCP-enabled site

Share a public WebMCP-enabled site for review. This form does not fetch the URL, and an unconfigured submission service returns a clear unavailable message.

Capability search + execution

The layer between intent and the website that can complete it.

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.

01

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.

02

Agent-accessible search

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.

03

Capability calling

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.

04

Freshness you can verify

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

Intent Search Discover Select Call Result

Search carries source, schema, permission, health, and invocation context through the flow. A tool's success response alone is not proof of the outcome.

  1. 01

    Intent

    Express the natural-language intent.

  2. 02

    Search

    Search capabilities across the indexed WebMCP web.

  3. 03

    Discover

    Discover and inspect the relevant capability contract.

  4. 04

    Select

    Select the right website tool and supported invocation path.

  5. 05

    Call

    Call the capability through Guard when supported and approved.

  6. 06

    Result

    Return the result or a grounded AI-generated answer with verification context.

One engine · four working interfaces

The web UI is only one way in.

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.

01

Web Search UI

People can search by intent, inspect complete capability contracts, and request an applicable verified read-only call.

02

Native WebMCP

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.

03

Search through MCP

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.

04

Live website execution

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

Use Search through API or MCP

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.

Capability search
Find indexed tools and inspect their contracts. No API key or live website calls are needed.
Capability summary
AI explains matching indexed tools; it does not fetch current website data.
Live AI summary
With explicit consent, Search calls relevant eligible read-only tools on their actual websites and summarizes the returned data with sources and per-tool outcomes.

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 →

Server URL

https://search.improvisus.tech/mcp

Transport: Streamable HTTP. Choose a remote HTTP server in your client, paste the URL, then connect and list its tools.

  1. 1. Connect your client

    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/mcp

    Run claude mcp get webmcpify-search to inspect the configuration. Inside Claude Code, use /mcp to check the connection and available tools.

    With an AI access key (optional)

    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"
          }
        }
      }
    }

    Claude Code connection guide ↗

    For another MCP client, use its remote server settings with the same URL and transport.

  2. 2. Choose your access

    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_KEY

    Summary 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.

  3. 3. Make your first search

    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.

The four MCP tools and when to use them
search_webmcp_capabilities
Search by intent. Accepts query, limit (default 10, maximum 50), summarize, execute, and optional verification/action filters.
get_webmcp_capability
Inspect an exact tool contract using a capabilityId returned by search.
list_site_webmcp_capabilities
Inspect a site’s indexed inventory using its siteId; this does not call those website tools.
get_webmcp_site
Read site identity, source, freshness, and verification details using its siteId.

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.

See the native WebMCP tools available on this page
search_web_capabilitiesget_capability_detailsget_site_detailslist_site_capabilitiesget_capability_healthsubmit_webmcp_siteinvoke_web_capability

The MCP server works with clients that support Streamable HTTP and, for AI access, custom authorization headers. A dedicated ChatGPT integration remains in development.