@secondlayer/sentinel

MCP server · npm · graded 2026-10-30Source linked

Security monitoring for Stacks (Clarity) smart contracts: CLI, MCP server and TypeScript client. Describe what to watch; get alerts by email, Slack or signed webhook.

No outside reports on file

@secondlayer/sentinel fetches arbitrary web URLs; restrict its folder reach, network access, and credentials before installing.

Based on public adoption and transparency signals as of Oct 30, 2026. Our opinion, not a code audit or security guarantee.

Was this verdict for @secondlayer/sentinel helpful?

What it can access

Local filesNo local folder access notedLOW
Command executionNo shell command runner notedLOW
Network reachFetches arbitrary web URLsREVIEW
CredentialsNo API token requiredLOW
Package sourcenpm (@secondlayer/sentinel)PUBLIC

Inferred from this listing’s public package details and description. Check the project’s source before installing.

Install

npx -y @secondlayer/sentinel

All setup options ↓

Check this skill Watch it in my stack Compare README badge View project

Everything known

We found nothing about this project in the sources we read (last checked 2026-10-30). That does not mean it has no problems.

0 incidents · 0 advisories · 0 news articles · 0 community threads · checked 2026-10-30

Popularity grade: F (from public signals such as stars and downloads, not a code review). Graded 2026-10-30.

Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library. Last checked 2026-10-30.

Check a specific version →

About @secondlayer/sentinel

@secondlayer/sentinel is an MCP server focused on Developer tools and Web & browsing: Security monitoring for Stacks (Clarity) smart contracts: CLI, MCP server and TypeScript client. Describe what to watch; get alerts by email, Slack or signed webhook.

It is published on npm as @secondlayer/sentinel. Based on its public metadata, its operational scope includes: fetches arbitrary web urls.

Setup

These use the package this listing points to. Check the project’s own instructions before running anything.

npm command

npx -y @secondlayer/sentinel

MCP client config

For Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json).

json

{
  "mcpServers": {
    "sentinel": {
      "command": "npx",
      "args": [
        "-y",
        "@secondlayer/sentinel"
      ]
    }
  }
}

Why this grade

FF — Many risk signals

Signal-based grade (0/7 points): no public source code found. This reflects adoption and transparency, not a code review.

Popularity and upkeep

4/100

Listing last refreshed: 2026-10-30

These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.

Risks to watch for

Untrusted web content & prompt injection: Fetches arbitrary web pages or remote endpoints where hidden instructions could manipulate agent behavior. Restrict outbound domains and review tool outputs.
Dependency & version pinning: Distributed via npm (@secondlayer/sentinel). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.

How to lower the risk

Least-privilege permissions

Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.

Network isolation

Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
If your IT team can, limit which websites and services it is allowed to contact.

Monitoring

Check its activity history or logs weekly at first, and look at what it changed or sent.
Turn on alerts for new logins or unusual usage on any account it connects to.

Red flags to watch for

It asks for more access than its job requires, or prompts you to paste passwords.
It suddenly updates with new owners, or starts contacting unfamiliar websites.

Questions

How do I install @secondlayer/sentinel?

Run npx -y @secondlayer/sentinel in your terminal, or add the server entry to your claude_desktop_config.json or .cursor/mcp.json as shown in the Setup section on this page.

Are there security reports about @secondlayer/sentinel?

No reports found for this package in our research (last checked 2026-10-30). @secondlayer/sentinel currently holds Grade F (Many risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.

Is @secondlayer/sentinel actively maintained?

We do not have star or download counts on file for @secondlayer/sentinel yet (listing refreshed 2026-10-30). Check the commit history and open issues before relying on it.

What are alternatives to @secondlayer/sentinel?

You can compare @secondlayer/sentinel side by side with other Slack MCP servers in the Related tools section on this page, or use the Compare tool on AgentArmorHQ.

Maintain or use @secondlayer/sentinel? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.

AgentArmorHQ Risk Grade F for @secondlayer/sentinel

GitHub README Markdown:

markdown

[![AgentArmorHQ Risk Grade for @secondlayer/sentinel](https://agentarmorhq.com/api/badge/secondlayer-sentinel)](https://agentarmorhq.com/skills/secondlayer-sentinel)

HTML embed:

html

<a href="https://agentarmorhq.com/skills/secondlayer-sentinel"><img src="https://agentarmorhq.com/api/badge/secondlayer-sentinel" alt="AgentArmorHQ Risk Grade for @secondlayer/sentinel" height="20" /></a>

Terminal check:

terminal

curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "secondlayer-sentinel"

Share with your security lead

Need sign-off to use @secondlayer/sentinel? Copy this note for Slack, a ticket or a pull request.

### AgentArmorHQ Security Review Memo: @secondlayer/sentinel
- **Listing URL:** https://agentarmorhq.com/skills/secondlayer-sentinel
- **Type:** App connector
- **Risk Grade:** Grade F (Many risk signals)
- **Outside Security Advisories on File:** 0

#### Permission & Blast-Radius Signals
- **Local files:** No local folder access noted
- **Command execution:** No shell command runner noted
- **Network reach:** Fetches arbitrary web URLs
- **Credentials:** No API token required
- **Package source:** npm (@secondlayer/sentinel)

#### Recommended Hardened Setup
- **Command:** `npx -y --ignore-scripts @secondlayer/sentinel`
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.

_Based on public adoption and transparency signals as of Oct 30, 2026. Our opinion, not a code audit or security guarantee._

Key facts

Type: App connector
Install command: npm install @secondlayer/sentinel
Est. context load: ~900 tokens / turn (~5 tool schemas, 0.45% of 200k context)
Last updated: 2026-10-30
Last graded: 2026-10-30

Community

Discussions for @secondlayer/sentinel

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Was this listing for @secondlayer/sentinel helpful?

Check before you install, in Claude

Your assistant answers Block, Review or No known issues for any package before it installs it.

Get this check inside Claude