Seal Security

io.sealsecurityPublished by sealsecurity.ioOfficial publisherv0.1.149Updated Nov 8, 2026

Vulnerability management: scan projects, search sealed packages, manage sealing rules and reports.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Seal Security remote MCP server that lets an assistant scan projects for vulnerabilities and manage sealed packages, sealing rules and reports.

What you can do
  • Scan projects for vulnerabilities
  • Search sealed packages
  • Manage sealing rules
  • Manage and review reports
When to use it
Useful when you want an assistant to check a project's dependency vulnerabilities or work with Seal Security's sealed package replacements and sealing rules without leaving the chat.
Requirements
Remote streamable HTTP endpoint at mcp.sealsecurity.io; OAuth authentication is required. No environment variables or headers are declared.
Before you install
Access is tied to a Seal Security account via OAuth, so the assistant acts with your account's permissions. The server can change sealing rules and reports, so review write actions before approving them; no further details on data handling are provided.

Installation

In SourceWeft

  1. Open Seal Security in the dashboard and add it to a workspace.
  2. Connect the required 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/io.sealsecurity%2Fmcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "seal-security": {
      "type": "http",
      "url": "https://mcp.sealsecurity.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

17
  1. v0.1.147Nov 4, 2026
  2. v0.1.145Nov 4, 2026
  3. v0.1.143Nov 3, 2026
  4. v0.1.142Oct 29, 2026
  5. v0.1.136Oct 26, 2026
  6. v0.1.134Oct 25, 2026
  7. v0.1.133Oct 21, 2026
  8. v0.1.131Oct 21, 2026
  9. v0.1.130Oct 19, 2026
  10. v0.1.128Oct 15, 2026
  11. v0.1.127Oct 14, 2026
  12. v0.1.126Oct 14, 2026
  13. v0.1.125Oct 6, 2026
  14. v0.1.124Sep 29, 2026
  15. v0.1.123Sep 29, 2026
  16. v0.1.122Sep 20, 2026
  17. v0.1.121Sep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

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