MCP Search and Fetch Preflight

WHY THIS EXISTS

Operational proof for AI-era sites and agents.

Design and audit a read-only MCP search/fetch connector with schemas, result ids, source URLs, sample responses, rate guards, abuse evals, and JSON contract receipt. The useful output is a visible table plus a receipt that names input, checks, limits, and next action.

• Separates search and fetch into narrow read-only tools with stable ids.
• Checks source URL, snippet, citation, auth, rate, and abuse-eval readiness.
• Exports a contract JSON that can become implementation documentation or eval input.

Boundary: Not a guarantee of MCP compliance, production security review, legal terms, or a substitute for testing the real server.