OpenSEO is an open-source SEO platform for keyword research, rank tracking, competitor analysis, backlink analysis, site audits, and AI visibility work. It connects SEO data to AI agents through an MCP server and reusable agent skills, while allowing users to supply their own DataForSEO API key and self-host the tool. Catalogue add-ons guide agents through OpenSEO's SEO workflows.
Borrowing it
Nothing to install: this file belongs to every-app/open-seo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/every-app/open-seo/main/.agents/skills/verify-local-mcp/SKILL.mdgit clone --depth 1 https://github.com/every-app/open-seoWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/every-app/open-seo/verify-local-mcp)<a href="https://agentmods.dev/skills/every-app/open-seo/verify-local-mcp"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/verify-local-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/every-app/open-seo/verify-local-mcp"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/verify-local-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Excessive Agency · line 48 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Data Exfiltration · line 23 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00089 | $0.01285 |
| Opus 5.5 | $0.00036 | $0.00514 |
| Sonnet 5.5 | $0.00018 | $0.00257 |
| Haiku 4.5 | $0.00009 | $0.00128 |
Grade A, and why
verify-local-mcp scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS http://<url>/mcp \ How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify local MCP
Two layers, in order. The protocol layer proves the server and provider behave; the consumer layer proves an agent that has never seen the code can use the tools well. They catch different bugs — protocol testing found DataForSEO quirks (zoom-dependent empty SERPs), the consumer probe found ergonomics failures (9KB provider rows overflowing client token budgets, fractional inputs rejected upstream with raw provider errors). Do both.
1. Boot
.env.localneedsAUTH_MODE=local_noauthandDATAFORSEO_API_KEY(base64 oflogin:password). Never print the key.- Start
pnpm dev:agentsin the background. The server URL is branch-prefixed:http://<branch-suffix>.open-seo.localhost:1355(the exact URL is printed on boot; logs tee to.logs/dev-server.log). - With
local_noauth,/mcpneeds no token. Vite hot-reloads server code, so fix → re-call without restarting. - After changing a tool's input or output schema, refresh the client's tool discovery (
tools/list) or reconnect the MCP client before calling it again. Clients can cache validators from the previous tool list and reject valid results after the provider call has already incurred a charge.
2. Protocol smoke (cheap, deterministic)
Raw JSON-RPC against /mcp — the layer for asserting exact shapes and driving edge cases (resume taskIds, empty results, invalid inputs):
curl -sS http://<url>/mcp \
-H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
# tools/call: {"method":"tools/call","params":{"name":"<tool>","arguments":{...}}}
- Bootstrap:
list_projects, thencreate_projectif empty — most tools need aprojectId. - Test the happy path AND at least one edge per changed tool: an empty result (obscure query), an invalid identifier, and for queued tools the full lifecycle including resuming with the returned
taskId. - These are real, billed DataForSEO calls (metering itself short-circuits in
local_noauth— billing needs unit tests, not this). Keep depths 10–20.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +1 lines 2b16bda20b01
- 1mo ago First seen · 71 lines · 89 tokens per session scan A d979799d569a
verify-local-mcp is a skill published in the GitHub repository every-app/open-seo (25,345 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 1,285 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
playground
Launches a local WordPress Playground site with The SEO Framework mounted, captures front-end SEO artifacts, and compares before/after plugin states. Use when testing regressions, reproducing bugs, changing meta/sitemap/robots/ schema/oEmbed/admin SEO output, checking WordPress version behavior, plugin conflicts, or…
wp-finalize-run
The check detail of the /wp-finalize run, split out of commands/wp-finalize.md so the command stays a short map — bilingual coverage, theme structure, the WP-CLI runtime validation, the GEO and agent-readiness report, and the three demo-parity layers (static, WP-CLI, measured visual parity). Use when /wp-finalize…
wp-demo-verify-run
The step detail of the /wp-demo-verify run, split out of commands/wp-demo-verify.md so the command stays a short map — Step 2a (the impeccable detector and its gate), Step 2b (the scroll walk, Firefox pass, --no-motion, fractional widths and the exit-code 2 fallback) and Step 3 (reading every finding kind). Use when…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.