
Jackpotkeywords Mcp Server
io.github.smythmykePublished by GitHub account smythmykev0.2.0Updated Oct 30, 2026
AI-powered keyword research, SEO audits, and AI-visibility scans via the JackpotKeywords REST API.
Overview
Local MCP server that connects an assistant to the JackpotKeywords REST API for keyword research, SEO audits and AI-visibility scans.
- What you can do
- Run keyword research through the JackpotKeywords API
- Perform SEO audits
- Run AI-visibility scans
- No individual tools are documented in the supplied listing, so exact operations are unclear beyond these API-backed capabilities.
- When to use it
- Useful when you want an assistant to pull keyword ideas, check on-page SEO, or see how a site appears in AI answers, without leaving the chat to use the JackpotKeywords web app.
- Requirements
- Runs locally over stdio, installed from the npm package jackpotkeywords-mcp-server (Node.js). Requires a JackpotKeywords API key supplied in the JACKPOTKEYWORDS_API_KEY environment variable, obtained from the provider's developer page. The API base URL can be overridden with JACKPOTKEYWORDS_API_BASE; network access to the API is needed.
Installation
In SourceWeft
- Open Jackpotkeywords Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.2.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.