Sentrysurface

io.github.sentrysurfacePublished by GitHub account sentrysurfacev1.0.0Updated Oct 24, 2026

Cybersecurity MCP server for URL scanning, threat intelligence, and domain reputation.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote cybersecurity MCP server that lets an assistant scan URLs, look up threat intelligence and check domain reputation.

What you can do
Scan URLs for security threats and suspicious content using the server's scanning capability, as described in the registry entry. Retrieve threat intelligence to give context on known risks. Check the reputation of a domain before an assistant or user relies on it. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to vet a link, domain or website before a user opens or trusts it, or when adding a quick reputation and threat check to a security-oriented workflow.
Requirements
A remote streamable HTTP endpoint at api.sentrysurface.io. An API key is sent in the Authorization header as a Bearer token using a ptnet_mcp_ key. Network access is required.
Before you install
The server requires an API key in the Authorization header, so treat that key as a secret and avoid exposing it in logs or shared configuration. URLs and domains submitted for scanning are sent to a third-party service. No tools are listed, so verify what data is transmitted and whether any usage limits or costs apply before relying on it.

Installation

In SourceWeft

  1. Open Sentrysurface in the dashboard and add it to a workspace.
  2. 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.github.sentrysurface%2Fsentrysurface/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": {
    "sentrysurface": {
      "type": "http",
      "url": "https://api.sentrysurface.io/mcp/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 listedRequired15 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.