Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"localseodata": {
"url": "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
42 local SEO tools for AI assistants. SERP tracking, reviews, keywords, audits, and more.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in marketing / ai-ml
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
An open-source AI agent that brings the power of Gemini directly into your terminal.
Just a Better Chatbot. Powered by Agent & MCP & Workflows.
MCP Security Weekly
Get CVE alerts and security updates for io.github.localseodata/mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Model Context Protocol server for Local SEO Data. Gives AI assistants access to 42 local SEO tools -- SERP tracking, review monitoring, keyword research, AI visibility scoring, geogrid scans, and more.
One-time setup, then ask questions in plain English and your assistant calls the right endpoints automatically.
YOUR_API_KEY below with your key (starts with sk_live_)claude mcp add localseodata --transport http "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY" --scope user
The --scope user flag makes it available across all your projects. Restart Claude Code after adding.
Add to your config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"localseodata": {
"url": "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY"
}
}
}
Restart Claude Desktop after saving.
Add to .cursor/mcp.json in your project root, or ~/.cursor/mcp.json for global access:
{
"mcpServers": {
"localseodata": {
"url": "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY"
}
}
}
Add to .vscode/mcp.json in your project:
{
"servers": {
"localseodata": {
"type": "streamable-http",
"url": "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY"
}
}
}
Open Cline settings > MCP Servers > Add Remote Server:
https://mcp.localseodata.com/mcp?key=YOUR_API_KEYAdd to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"localseodata": {
"serverUrl": "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY"
}
}
}
| Category | Tools |
|---|---|
| SERP Data | local_pack, organic_serp, local_finder, maps, local_services_ads |
| AI/LLM Optimization | ai_overview, ai_mode, ai_mentions, ai_visibility, ai_compare, ai_keyword_data, ai_top_sources, ai_top_pages |
| Business Data | business_profile, google_reviews, qa, business_listings, multi_platform_reviews |
| Keyword Research | search_volume, keyword_suggestions, keywords_for_site, related_keywords, keyword_trends |
| Audits | local_audit, citation_audit, reputation_audit, page_audit, profile_health |
| Competitive Intel | competitor_gap, competitor_ads, brand_mentions, backlink_gap, backlink_summary |
| Reports | review_velocity, local_authority, keyword_opportunities |
| Geogrid | geogrid_scan |
| Locations | location_search |
| Utility | ping, get_balance |
Once connected, just ask naturally:
Your API key is passed as a URL query parameter (?key=YOUR_API_KEY). This works with every MCP client without needing custom header configuration. Keys can be created or revoked anytime in the API Keys dashboard.
MCP calls consume credits from your Local SEO Data account, same as REST API calls. Most endpoints cost 1 credit ($0.005). Monitor usage in your dashboard.
See [localseoda