Tuvio

dev.tuvioPublished by tuvio.devOfficial publisherv1.0.0Updated Oct 29, 2026

Security scans for AI-built apps: leaked keys, open Supabase RLS, vulnerable packages, live sites.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an assistant run security scans on AI-built apps: leaked keys, open Supabase RLS, vulnerable packages and live sites.

What you can do
  • Run security scans against apps built with AI assistance.
  • Check for leaked or exposed API keys and secrets.
  • Inspect Supabase row-level security settings for open access.
  • Detect vulnerable dependencies in a project.
  • Scan live, deployed sites for security issues.
When to use it
Useful when you build or ship apps with AI assistance and want an assistant to check them for exposed keys, misconfigured Supabase RLS, vulnerable packages or issues on a live site before or after deployment.
Requirements
A remote MCP endpoint at api.tuvio.dev over streamable HTTP. A Tuvio access token is required as a bearer credential in the Authorization header; tokens are created in the Tuvio app settings under connected AIs. Network access to the endpoint is needed.
Before you install
The server requires a Tuvio access token sent in the Authorization header, so treat it as a secret and keep it out of shared logs. Scans may inspect your project's configuration, dependencies and live site, and results are produced by a third-party service, so consider what code and site details you are willing to expose.

Installation

In SourceWeft

  1. Open Tuvio 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/dev.tuvio%2Ftuvio/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": {
    "tuvio": {
      "type": "http",
      "url": "https://api.tuvio.dev/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. v1.0.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.