Skip to content
Agentic Scraper

Discovery and submission

The wizard uses POST https://api.agenticscraper.com/api/v1/mcp-market/validations. A successful validation ID and matching source fingerprint are required for submission.

Remote MCP discovery

Send type: "remote_mcp" and an HTTPS url. The service rejects localhost, loopback, private-network DNS results, oversized responses, and non-HTTPS URLs.

Discovery sends MCP initialize with protocol version 2025-06-18, then tools/list. It accepts JSON or the first data: line from a text/event-stream response. Tool names are normalized before they are returned.

OpenAPI discovery

Send type: "openapi" with one of:

  • url for a remotely fetched JSON/YAML specification
  • specText containing JSON or YAML
  • spec containing the parsed document

The adapter derives tools from GET, POST, PUT, PATCH, and DELETE operations. It uses operationId when present and otherwise derives a name from method and path.

For execution, the stored OpenAPI document must contain paths and servers[0].url. The current adapter supports path, query, and header parameters plus an application/json request body.

Create the submission

Send the discovered definition to POST https://api.agenticscraper.com/api/v1/mcp-market/submissions. type and name are required. A remote MCP submission requires remoteMcpUrl; an OpenAPI submission requires openapiSpec or openapiSpecText. Normalization must produce at least one tool.

Choose free, tool_call_fixed, or provider_event before validation. Event-driven submissions must complete a non-monetary verification charge for every configured event before review.