Add looot third-party MCP plugin (API key header auth)

[walidboulanouar]

looot is a remote MCP server and API with one key and prepaid balance for about 2,500 data endpoints (work email, phone, company enrichment, Google SERP, web pages). This PR adds third_party/looot/ in the same shape as the Hunter and Brevo plugins: mcp.json with an Authorization: Bearer ${LOOOT_API_KEY} header, plugin.json with the LOOOT_API_KEY variable, README, CHANGELOG, LICENSE and logo, plus one entry each in .cursor-plugin/marketplace.json and the README table.

I did not run scripts/validate-plugins.mjs (it needs ajv installed). I checked that both JSON files parse. I work on looot.

---

Note

Low Risk
Manifest and documentation-only addition with no changes to core marketplace logic; auth is user-configured Bearer token to a third-party endpoint.

Overview
Adds the looot third-party integration to the Cursor plugin marketplace so agents can call looot’s hosted MCP for prospecting and enrichment (emails, phones, companies, SERP/web data) via a user-supplied API key and prepaid balance.

New third_party/looot/ follows the standard MCP plugin layout: plugin.json with required LOOOT_API_KEY, mcp.json pointing at https://api.looot.ai/mcp with Authorization: Bearer ${LOOOT_API_KEY}, plus README, CHANGELOG, LICENSE, and logo reference. Marketplace and root README plugin tables each gain a looot entry.

^{Reviewed by Cursor Bugbot for commit 64ad1a0. Bugbot is set up for automated code reviews on this repo. Configure here.}

[walidboulanouar]

Friendly check-in. I merged main into the branch today (the marketplace.json and README rows now sit after tailscale and highlevel), and scripts/validate-plugins.mjs passes. Happy to change any manifest field or the description.