Add anakin plugin

[bytes-as]

Adds Anakin — a web data platform for AI agents — as a third-party plugin.

What it provides

The plugin bundles the @anakin-io/mcp server with five skills:

• scrape / map / crawl — any URL to clean markdown or AI-extracted JSON, with optional stealth-browser rendering
• search / agentic_search — web search, and multi-source deep research that scrapes its own citations
• wire_* — pre-built, vetted actions across hundreds of popular sites, returning structured data without hand-written selectors
• monitor_* — scheduled change detection with webhook or email alerts
• browser_task / session_* — natural-language automation in a real cloud browser, with saved login sessions

The skills exist because the tool schemas alone don't convey when to prefer one over another — most notably that Wire has read actions needing no auth, which agents otherwise skip.

Checklist

• source pins a full 40-character lowercase commit SHA
• Public repository owned by Anakin-Inc, Apache-2.0
• keywords and domains scoped to the brand, not generic terms
• category set to development
• No duplicate entry in the catalog
• python3 scripts/generate-plugin-index.py run and committed
• python3 scripts/validate-catalog.py passes — Catalog OK

Notes

The generated index resolves the stdio MCP server and all five skills at the pinned SHA.

The server requires an ANAKIN_API_KEY environment variable (free tier available, no card). The plugin intentionally ships no env block: clients that don't expand ${VAR} would pass the literal through, and the server would then start and advertise every tool while all calls fail. Without one, a missing key stops the server immediately with a message naming the variable and where to get it.

The MCP server version is pinned exactly rather than tracking @latest, so the reviewed SHA cannot execute unreviewed code.

[bytes-as]

Bumping this — it's been open since 2026-07-21 with no review yet, and I traced why it likely isn't showing as ready:

Branch was stale. It hadn't picked up main since 2026-08-18 (~2 weeks of daily SHA bumps + new plugin additions behind). Just merged current main in — no conflicts, diff is still just the single anakin entry in marketplace.json + plugin-index.json.

Re-validated against latest main:

$ python3 scripts/validate-catalog.py
Catalog OK (.grok-plugin/marketplace.json)

$ python3 scripts/generate-plugin-index.py --check
Plugin index OK (.grok-plugin/plugin-index.json)

The Validate catalog required check has never actually run — it's sitting at action_required (not failed, just never executed) on every push, including this one: https://github.com/xai-org/plugin-marketplace/actions/runs/33612702067. That looks like GitHub withholding workflow runs for an outside-contributor fork PR, which needs a maintainer to hit "Approve and run workflow" in the Actions tab — not something I can do from here.

Socket Security and Semgrep are both green. Happy to make any changes if there's something specific blocking merge — just haven't had eyes on it yet. Thanks!

[bytes-as]

@ykeremy could you take a look when you get a chance? Looks like every recent plugin addition (Tavily, MongoDB Atlas, TinyFish, browser-use, pstack) went through your review, and this one seems to have fallen through the cracks — the required Validate catalog check is also stuck at action_required, so it'd need an approved run to go green. Thanks!

[bytes-as]

Following up again, ~7 weeks in now — sorry for the repeat ping, but it has been a bit too long.

I compared against the plugin PRs that have merged recently (6 in just the last week, all through @ykeremy — nice pace!) and every single one of them has a validate check that actually ran and passed. Ours doesn't have it at all — still just Socket Security + Semgrep, no validate entry, meaning the workflow run has never been approved to start. Since it's never run, I'd guess this PR isn't surfacing as "ready" wherever you triage from, which would explain why it's been skipped even while others move quickly.

@ykeremy — could you approve the pending workflow run for this PR in the Actions tab when you get a chance? That looks like the one concrete thing standing between this and a normal review. Happy to push an empty commit or anything else that helps if that's not it.