search discovers REST API operations, and execute calls one discovered operation. Together they give an agent access to the live Zero OpenAPI contract without allowing arbitrary HTTP requests.
operation is a Zero MCP field, not a universal MCP field. Its value comes from the OpenAPI operationId and uses snake_case, such as search_vulnerabilities and get_vulnerability.Typical flow
- Call
searchwith the capability or entity you need. - Select an operation from
operations. - Read its parameter, request-body, and response schemas.
- Pass its exact
operationname and valid inputs toexecute.
execute does not accept a URL, HTTP method, credentials, or arbitrary headers. The server resolves those details from OpenAPI and forwards the authentication already associated with the MCP connection.
search
Searches the current API operation catalog. Deprecated and internal system operations are excluded.
Input schema
Output schema
Each operation contains:
Each parameter has
name, in, required, description, and schema. The in value is path, query, or header; header parameters are informational because callers cannot inject arbitrary headers through execute.
An abridged result for a vulnerability search looks like:
execute
Resolves and calls one operation from the catalog. The server validates path parameters, query values, and the JSON body against the operation’s current OpenAPI schemas before sending the request.
Input schema
Search for critical, known-exploited vulnerabilities:
Output schema
Validation and errors
- An unknown
operationfails before any API request is sent. - Missing path parameters or a required body fail schema validation locally.
- Invalid parameter and body values return a validation error describing the rejected field.
- REST API responses with status
400or higher retain their Problem Details body and are marked as MCP errors. - Response bodies larger than 512 KiB are truncated and return
truncated: true.