Sentrint

com.sentrintPublished by sentrint.comOfficial publisherv1.0.0Updated Oct 31, 2026

Code security scanner for founders and small teams: leaked secrets, missing RLS, injection, CVEs

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Sentrint is a remote code security scanner for founders and small teams, surfacing leaked secrets, missing RLS, injection flaws and CVEs to an assistant.

What you can do
  • Scan code for security problems such as leaked secrets, missing row-level security, injection vulnerabilities and known CVEs.
  • Report findings back to the assistant for review and follow-up.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Useful when a small team or solo founder wants an assistant to check a codebase for common security weaknesses without setting up a dedicated security pipeline.
Requirements
A remote MCP endpoint at sentrint.com using streamable HTTP; OAuth authentication is required. No packages, environment variables or headers are declared.
Before you install
The server scans source code, so code and any secrets found in it are sent to a third party. Access is granted through OAuth, so review the scopes requested. No tool list is published, so what it can read or change is not documented.

Installation

In SourceWeft

  1. Open Sentrint 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/com.sentrint%2Fsentrint/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": {
    "sentrint": {
      "type": "http",
      "url": "https://sentrint.com/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

1
  1. v1.0.0LatestOct 31, 2026

Score

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