← Index

Securealy

com.securealy/mcpv0.1.6Databases

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

The current version, v0.1.6, was published to the official MCP registry on 2026-10-14. It is distributed as securealy-mcp on npm, filed under Databases by this index, and declares 12 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Securealy in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-11-13 19:02 UTC
screened 2026-10-14tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“Tool grades URLs, scans repos, checks Supabase, Stripe, Vercel.”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.

That verdict was true at screening time (snapshot 2026-10-19).

Contracts can change after screening, with no version bump. The gate pins Securealy’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for Securealy](https://mcpindex.ai/server/com-securealy-mcp) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/com-securealy-mcp">Independent trust record for Securealy</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/com-securealy-mcp)](https://mcpindex.ai/server/com-securealy-mcp)
HTML
<a href="https://mcpindex.ai/server/com-securealy-mcp"><img src="https://mcpindex.ai/api/v1/badge/com-securealy-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
SUPABASE_URL

Optional. Your Supabase project URL, read by check_rls. Sent only to that project.

SUPABASE_SERVICE_KEY
secret

Optional. Service role key for check_rls. Sent only to your Supabase project, never printed.

SUPABASE_MGMT_TOKEN
secret

Optional. Supabase management token for check_rls and the auth config check. Sent only to the Supabase management API.

SUPABASE_PROJECT_REF

Optional. Supabase project ref, used with SUPABASE_MGMT_TOKEN.

STRIPE_SECRET_KEY
secret

Optional. Stripe secret key for check_stripe. Sent only to api.stripe.com, never printed.

VERCEL_TOKEN
secret

Optional. Project-scoped Vercel token for check_vercel_env. Sent only to api.vercel.com, never printed.

VERCEL_PROJECT_ID

Optional. Vercel project id for check_vercel_env.

SECUREALY_VERCEL_DECRYPT

Optional. Set to 1 to let check_vercel_env fetch decrypted variable values from api.vercel.com for the trailing-newline and live-key checks. Without it only names and targets are read and those checks are reported as skipped.

SECUREALY_SUPABASE_HOST_OVERRIDE

Optional. Set to 1 to let check_rls send the service key to a self-hosted Supabase URL. Without it the key is sent only to an https URL on a Supabase-hosted domain.

SECUREALY_SCAN_ROOTS

Optional. Folders, separated by the OS path delimiter, that scan_repo may read in addition to the server's working directory. Anything outside is refused.

SECUREALY_NO_HISTORY

Optional. Set to 1 to stop the server appending each run (grade, score, counts, failing check ids; never evidence) to .securealy/history.json in its working directory.

SECUREALY_TELEMETRY

Optional, off by default. Set to 1 to send an anonymous aggregate of each run (command, grade, counts, stack kind, failing check ids; no URL, host or evidence) to securealy.com.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Databases