automation-preflight
TinyOps Studio publishes NO MCP server for the Automation Preflight API. This file is a candidate tool surface derived from the published OpenAPI operations — a design proposal, not a provider artifact. No MCPServer pointer is wired in apis.yml, because there is no server to point at.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Descriptor
Candidate descriptor · transport http
Tools
analyze_page_readiness— Fetch a public URL and return bounded integration-readiness evidence: reachability, robots policy, page structure, forms, integration links, security headers, and a deterministic readiness score.build_acceptance_pack— Build an implementation-ready automation acceptance pack for a public URL: preflight evidence plus launch gates, acceptance tests, and a prioritized remediation backlog.check_service_health— Check that the preflight service is up and report its build version.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.