LeashIndex Get the report

Index / data

SEO Console

io-github-ibrahimhajjaj-seo-console-mcp declares 43 capabilities across 43 tools, with 2 critical issues.

76/100 exposureHigh exposure

Manifest recorded 2026-10-22 from tools/list answered by the npm package seo-console-mcp@0.18.2 (published to npm as seo-console-mcp, listed in the official MCP registry as io.github.ibrahimhajjaj/seo-console-mcp 0.18.2), run in an isolated container with no network access and no credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 43 tools

43 of 43 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 1 of 43 tools

1 tool is classified as irreversible and declares no limit.

high · no-expiry · All 43 tools

43 of 43 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 43 tools

43 of 43 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 10 of 43 tools

10 tools can modify data and declare no limit.

low · uncapped-read · 32 of 43 tools

32 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
search_analyticsread inferred
keyword_ideasread inferred
search_opportunitiesread inferred
compare_search_periodsread inferred
ctr_gapsread inferred
query_cannibalizationread inferred
list_sitemapsread inferred
list_propertiesread inferred
submit_sitemapread inferred
delete_sitemapdelete inferred
inspect_urlwrite assumed
index_coverageread inferred
request_recrawlwrite inferred
indexnow_submitread inferred
pagespeedwrite assumed
seo_auditread inferred
audit_sitewrite assumed
server_versionwrite assumed
wporg_pluginread inferred
play_store_statsread inferred
app_store_listingread inferred
app_store_salesread inferred
play_vitalsread inferred
app_store_discoveryread inferred
app_store_reviewsread inferred
crux_field_dataread inferred
crux_historyread inferred
ads_campaignsread inferred
ads_keywordsread inferred
ads_adsread inferred
ads_ad_copyread inferred
ads_assetsread inferred
ads_queryread inferred
ads_search_termsread inferred
ads_negativesread inferred
ads_changesread inferred
ads_negatives_updatewrite inferred
ads_updatewrite inferred
ads_keyword_createwrite inferred
ads_update_batchwrite inferred
list_snapshotsread inferred
snapshotwrite assumed
compare_snapshotsread inferred
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.