Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LV24 SEO

PYPI · LV24-SEO

Free-first SEO for agents: GSC, Yandex Webmaster/Metrika, Bing, CrUX, PSI, crawl.

Available components

−12 this week 68 Trust /100

Last scanned (11 hours ago)

Scores higher than 61% of PyPI servers

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 4 of 44 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to LevapVeeskela/lv24-seo-optimizer). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 754 tokens (~50/item across 15 items; 12 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.15.3 → 0.15.4 functional
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.15.2 → 0.15.3 functional
  • 18 Nov 26 +1
    • Package version: 0.12.2 → 0.15.2 functional
    • Package version: 0.12.2 → 0.14.1 functional
    • Package version: 0.12.2 → 0.14.0 functional
  • 17 Nov 26 +31
    • Malware scan: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Schema quality: 645 → 754 ▼ functional
    • Schema quality: 645 → 747 ▼ functional
    • Schema quality: 645 → 731 ▼ functional
    • Security disclosure: pass → unverified ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.23 ▲ functional
    • Package version: 0.8.0 → 0.12.2 functional
    • Package version: 0.8.0 → 0.11.0 functional
    • Package version: 0.8.0 → 0.10.0 functional
    • Package version: 0.5.2 → 0.9.0 functional
    • Package version: 0.5.2 → 0.8.0 functional
  • 16 Nov 26 −45
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.17 → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Schema quality: 645 → 731 ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Package version: 0.5.2 → 0.8.0 functional
    • Package version: 0.5.2 → 0.6.0 functional
    • Package version: 0.5.2 → 0.5.3 functional
  • 15 Nov 26 0
    • Package version: 0.5.1 → 0.5.2 functional
  • 14 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.4.0 → 0.5.1 functional
    • Package version: 0.4.0 → 0.5.0 functional
  • 13 Nov 26 +29
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.10 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/lv24-seo@0.15.4

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo LevapVeeskela/lv24-seo-optimizer
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/LevapVeeskela/lv24-seo-optimizer/.github/workflows/release.yml@refs/tags/v0.15.4
Rekor log index 4010466898
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:3e584c102b508940a0fb3f631b4d77ce89764c8899725d7910da4dec77d21d0b

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 44 packages
Packages resolved 44
Stale 3
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~550 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
gsc_search_analytics ~65

Query GSC clicks/impressions/CTR/position by query, page, country or device.

NameTypeReqDescription
dimensions–––
end_datestring––
limitinteger––
propertystring––
start_datestring––

No output schema declared.

No examples provided.

seo_crawl_site ~47

Crawl a site (robots-respecting), return crawl summary and rule violations.

NameTypeReqDescription
include_rules–––
max_urlsinteger––
start_urlstring––

No output schema declared.

No examples provided.

seo_indexing_triage ~39

Group not-indexed URLs by reason and propose the cheapest fix.

NameTypeReqDescription
max_examplesinteger––
urlstring––

No output schema declared.

No examples provided.

seo_log_analysis ~40

Parse one local nginx JSON access log and report bot crawl rollups and wasted share.

NameTypeReqDescription
botstring––
filestringyes–

No output schema declared.

No examples provided.

seo_opportunities ~49

Striking-distance queries, CTR gaps, decayed pages, cannibalisation candidates.

NameTypeReqDescription
daysinteger––
limitinteger––
min_impressionsinteger––

No output schema declared.

No examples provided.

seo_properties ~18

List every site/property visible to the configured tokens.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

seo_recrawl_request ~59

Queue URLs for Yandex recrawl within the daily quota.

NameTypeReqDescription
allow_writeboolean––
confirm_tokenstring––
host_idstring––
plan_hashstring––
urls–––

No output schema declared.

No examples provided.

seo_report_diff ~37

Diff two stored weekly report snapshots (metrics, issues, opportunity churn).

NameTypeReqDescription
basestring––
headstring––

No output schema declared.

No examples provided.

seo_sitemap_submit ~83

Submit a sitemap to GSC or Bing; Bing defaults to <base_url>/sitemap.xml.

NameTypeReqDescription
actionstring––
allow_writeboolean––
confirm_tokenstring––
plan_hashstring––
propertystring––
providerstring––
sitemap_urlstring––

No output schema declared.

No examples provided.

seo_weekly_report ~41

Build the weekly SEO digest (deltas vs last snapshot) for one property.

NameTypeReqDescription
daysinteger––
lag_daysinteger––

No output schema declared.

No examples provided.

yandex_indexing_state ~25

Indexing history, in-search page counts and diagnostics for a host.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

yandex_query_stats ~47

Top Yandex queries for a host with shows, clicks, position.

NameTypeReqDescription
host_idstring––
limitinteger––
order_bystring––

No output schema declared.

No examples provided.

Install

How do I install the LV24 SEO MCP server?

LV24 SEO runs locally as a PyPI package, launched with uvx lv24-seo mcp serve. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · lv24-seo

# add to Claude Code
claude mcp add levapveeskela-lv24-seo -- uvx lv24-seo mcp serve
Common questions

What is the LV24 SEO MCP server?

LV24 SEO is an MCP server listed in the public MCP registry as io.github.LevapVeeskela/lv24-seo. Free-first SEO for agents: GSC, Yandex Webmaster/Metrika, Bing, CrUX, PSI, crawl. This page covers its PyPI package (lv24-seo).

Is the LV24 SEO MCP server safe to use?

LV24 SEO scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the LV24 SEO MCP server expose?

LV24 SEO exposes 12 tools: seo_properties, gsc_search_analytics, yandex_query_stats, yandex_indexing_state, seo_crawl_site, and 7 more. Their descriptions and schemas cost roughly 550 tokens of context every time the server is loaded.

Is the LV24 SEO MCP server still maintained?

LV24 SEO is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the LV24 SEO MCP server under?

LV24 SEO declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the LV24 SEO MCP server?

VerifyMCP ran 15 checks on LV24 SEO, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about LV24 SEO: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.