Skip to content

io.github.DataLeadsPRO/seo-audit-content

by DataLeadsPRO · remote · no sign-in to list tools · v1.0.1 · published by GitHub user DataLeadsPRO

Full SEO audits, content analysis, and domain overviews - on-page, technical, and authority metrics

Changes · 3
CompareRegistry entry

3 tools: 3 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http seo-audit-content https://data.dataleads.pro/mcp/seo-audit-content

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 3Claude Code: ask
  • domain_overviewV1 Domain OverviewCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    V1 Domain Overview
  • seo_auditV1 Seo AuditCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    V1 Seo Audit
  • seo_contentV1 Seo ContentCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    V1 Seo Content

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http seo-audit-content https://data.dataleads.pro/mcp/seo-audit-content

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__seo-audit-content__seo_audit",
      "mcp__seo-audit-content__seo_content",
      "mcp__seo-audit-content__domain_overview"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as seo-audit-content. Review it before you use it.

Capability tags behind 3 rules
  • mcp__seo-audit-content__seo_audit outbound
  • mcp__seo-audit-content__seo_content outbound
  • mcp__seo-audit-content__domain_overview outbound