Securealy

com.securealyPublished by securealy.comv0.1.6Updated Oct 25, 2026

Grade a URL as an attacker and a customer would see it; scan a repo; check Supabase, Stripe, Vercel.

Overview

AI-generated overview

Securealy is a local MCP server that grades a URL from attacker and customer perspectives and checks a repo, Supabase, Stripe and Vercel configurations.

What you can do
Grade a URL as an attacker and as a customer would see it, producing a grade, score and failing check ids for a run. Scan a repository, reading the working directory plus any extra folders listed in SECUREALY_SCAN_ROOTS. Check Supabase row-level security and auth configuration using a management token, project ref, URL and service key. Check Stripe configuration with a secret key. Check Vercel environment variables, optionally fetching decrypted values. Optionally append a run summary to a local history file and send anonymous aggregate telemetry.
When to use it
Useful when you want an assistant to audit a deployed site or repository for security and configuration problems, or to verify Supabase, Stripe and Vercel settings before or after a release.
Requirements
Runs locally over stdio via npx from the npm package securealy-mcp, so Node.js is needed. Optional credentials: STRIPE_SECRET_KEY, SUPABASE_MGMT_TOKEN, SUPABASE_SERVICE_KEY, VERCEL_TOKEN, plus SUPABASE_PROJECT_REF, SUPABASE_URL and VERCEL_PROJECT_ID. Network access to the relevant provider APIs is required for those checks.
Before you install
Several optional variables hold sensitive credentials: STRIPE_SECRET_KEY, SUPABASE_MGMT_TOKEN, SUPABASE_SERVICE_KEY and VERCEL_TOKEN. SECUREALY_VERCEL_DECRYPT set to 1 fetches decrypted Vercel variable values, and SECUREALY_SUPABASE_HOST_OVERRIDE set to 1 allows the Supabase service key to be sent to a self-hosted URL. SECUREALY_TELEMETRY set to 1 sends anonymous run aggregates to securealy.com. Runs are written to a local history file unless SECUREALY_NO_HISTORY is set to 1.

Installation

In SourceWeft

  1. Open Securealy in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.6LatestOct 15, 2026
  2. v0.1.4Oct 14, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.