Add Scavio MCP component (web-data)

[scavio-ai]

Adds Scavio to components/mcps/web-data/.

Scavio is a unified web data API: one key returns structured JSON from Google search (SERP, News, Maps, Shopping, Trends, Flights, Hotels, AI Mode), YouTube, Amazon, Walmart, eBay, Target, TikTok, TikTok Shop, Instagram, LinkedIn, X, Reddit, Zillow, Redfin, Indeed, Glassdoor, SEC EDGAR and more, plus an extract endpoint that turns any URL into Markdown. 191 tools across 32 platforms.

• Published on npm as @scavio/mcp-server (v0.13.1), stdio transport, no build step
• Also in the official MCP registry as io.github.scavio-ai/scavio-mcp
• Free tier on signup, no credit card, so the component is testable without payment

One file added, matching the shape of the neighbouring apify.json and brightdata.json. JSON validated.

---

Summary by cubic

Adds a new Scavio MCP component for web data so users can fetch structured results from major platforms and extract any URL via a single API key.

• Area: components (cli-tool/components/); adds cli-tool/components/mcps/web-data/scavio.json.
• Invokes external runtime via npx with @scavio/mcp-server (unpinned); reviewers should confirm trust/versioning.
• Requires new env var: SCAVIO_API_KEY.
• New component added; regenerate docs/components.json if the catalog needs to include it.

^{Written for commit 19a0d2a. Summary will update on new commits.}

[github-actions]

👋 Thanks for contributing, @scavio-ai!

This PR touches cli-tool/components/** and has been marked review-pending.

What happens next

1. 🤖 Automated security audit runs and posts results on this PR.
2. 👀 Maintainer review — a human reviewer validates the component with the component-reviewer agent (format, naming, security, clarity).
3. ✅ Merge — once approved, your PR is merged to main.
4. 📦 Catalog regeneration — the component catalog is rebuilt automatically.
5. 🚀 Live on aitmpl.com — your component appears on the website after deploy.

While you wait

• Check the Security Audit comment below for any issues to fix.
• Make sure your component follows the contribution guide.

This is an automated message. No action is required from you right now — a maintainer will review soon.

[greptile-apps]

Greptile Summary

Adds a Scavio web-data MCP descriptor that launches the npm server through npx and supplies a placeholder API key.

• Registers Scavio under the web-data MCP category.
• Configures stdio startup through @scavio/mcp-server.
• Omits regeneration of the public component catalog artifacts.

Confidence Score: 4/5

The catalog synchronization must be completed before merging so the newly added Scavio component is visible on the public component surfaces.

The MCP descriptor itself follows the expected structure, but adding only the canonical source file leaves the tracked documentation, dashboard, and search catalogs without the new component.

Files Needing Attention: cli-tool/components/mcps/web-data/scavio.json and generated component catalog artifacts

Important Files Changed

Filename	Overview
cli-tool/components/mcps/web-data/scavio.json	The descriptor follows the expected MCP configuration shape, but its generated documentation and dashboard catalog entries are missing.

_{Reviews (1): Last reviewed commit: "add scavio mcp component (web-data)" | Re-trigger Greptile}

[greptile-apps]

Public catalogs omit Scavio

When users browse or search the generated component catalogs, this new canonical MCP descriptor has no corresponding generated entries, causing Scavio to remain absent from the documentation and dashboard listings even though the installer source exists.

Knowledge Base Used: Components Catalog (cli-tool/components)

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}

[scavio-ai]

On the catalog-regeneration note — I left the generated artifacts out deliberately, because that appears to be this repo's convention rather than an omission. Happy to be corrected if not.

Two recently merged third-party MCP additions each touched exactly one file, the component JSON:

• feat: add 5dive MCP server (devtools) #811 feat: add 5dive MCP server (devtools) → cli-tool/components/mcps/devtools/5dive-mcp.json
• Add HumanPen MCP under productivity #796 Add HumanPen MCP under productivity → cli-tool/components/mcps/productivity/humanpen.json

Both components are now present in docs/components.json, dashboard/public/components.json and dashboard/public/search-index.json, so the catalogs are clearly regenerated after merge rather than by the contributor.

I also checked whether I could just run it: scripts/generate_components_json.py rebuilds the entire catalog set, shells out to an npm security audit in cli-tool/, and reads env vars via dotenv. Running it here would produce a repo-wide diff touching every component and would likely embed values from my environment — worse for review than the one-line addition.

So this PR stays a single file, matching #811 and #796. If you would rather contributors regenerate, say the word and I'll add the artifacts.

The component itself is unchanged: web-data/scavio.json, stdio via npx -y @scavio/mcp-server (v0.13.1 on npm), placeholder API key, same shape as the neighbouring apify.json and brightdata.json.