ScanYourSite

app.scanyoursitePublished by scanyoursite.appOfficial publisherv0.1.0Updated Oct 29, 2026

Outside-in audit of a live site: leaked keys, headers, TLS, SPF/DMARC, privacy, SEO, with fixes

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an assistant run an outside-in audit of a live website, covering leaked keys, headers, TLS, SPF/DMARC, privacy and SEO, with fixes.

What you can do
  • Audit a live site from the outside, checking leaked keys, HTTP headers, TLS configuration, SPF/DMARC email records, privacy and SEO.
  • Report findings together with suggested fixes for the issues found.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to check a deployed website's security and configuration posture, or to review email authentication and SEO basics, without setting up scanners yourself.
Requirements
A remote endpoint at scanyoursite.app over streamable HTTP. A free account is needed to create a personal API token, sent as a Bearer token in the Authorization header; the token is shown only once.
Before you install
The server requires a personal API token in the Authorization header, so treat it as a secret. Audits target a live site, so results and any requests go to a third-party service; review what site details you share.

Installation

In SourceWeft

  1. Open ScanYourSite in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.scanyoursite%2Fscanyoursite/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "scanyoursite": {
      "type": "http",
      "url": "https://scanyoursite.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.