LogSentinel

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Anthropic logs audit filter and cybersecurity threat analyzer.

VerifiedSSEWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that audits Anthropic logs and analyzes cybersecurity threats, with a paid premium settlement option.

What you can do
  • Audit Anthropic logs and filter them for review.
  • Analyze logs for cybersecurity threats.
  • Access a premium settlement tier that requires a payment signature header.
  • No individual tools are documented, so the exact operations are not described in the supplied material.
When to use it
Consider it when you want an assistant to review Anthropic log data for security auditing or threat analysis, and you are willing to use a hosted third-party endpoint.
Requirements
A remote SSE endpoint at a hosted URL; no local package or runtime is needed. No authentication is declared, but the premium settlement feature requires a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature.
Before you install
The premium tier asks for a payment-signature header, which is a cryptographic authorization for a transfer; treat it as spending authority and only supply it if you accept the payment. Log data sent to this third-party hosted endpoint leaves your environment, and no tool list or documentation is provided to confirm what it does with that data.

Installation

In SourceWeft

  1. Open LogSentinel in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. 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.Evozim%2Flogsentinel/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": {
    "logsentinel": {
      "type": "sse",
      "url": "https://logsentinel-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 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 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.

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