MCP Sentinel

io.github.oaslanankaPublished by GitHub account oaslanankav1.0.0Updated Oct 24, 2026

Zero-trust MCP security proxy with policy enforcement, PII scrubbing, approvals, and audit trails.

VerifiedSTDIODesktop onlyDeveloper Tools Security & Monitoring

Server details

Identifier: io.github.oaslananka/sentinel
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account oaslananka for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.oaslananka%2Fsentinel.svg)](https://sourceweft.com/mcp/io.github.oaslananka%2Fsentinel?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local zero-trust security proxy for MCP traffic that adds policy enforcement, PII scrubbing, approvals and audit trails between clients and backend MCP tools.

What you can do: Sits between MCP clients and backend MCP servers, wrapping client-facing traffic with policy and audit controls (R33). Enforces zero-trust policies, approval steps and PII controls on proxied tool traffic (D1, R14). Records audit data and keys in a local SQLite database (V1.1). Connects to upstream MCP servers either by launching a stdio command or by pointing at an HTTP endpoint (V2.1, V3.1).
When to use it: Worth adding when MCP servers are used beyond a single local demo and you need a trust boundary, approval gates, PII handling and an audit record for tool traffic, for example in teams or internal platforms (R5, R6).
Requirements: Runs as a local process on the user's machine (desktop only) via the npm package over stdio. Needs Node.js and a writable SQLite database path set in SENTINEL_DB_PATH. An upstream must be configured with SENTINEL_UPSTREAM_COMMAND for a stdio server or SENTINEL_UPSTREAM_URL for an HTTP endpoint. No authentication is declared.

Before you install

It proxies and inspects traffic to backend MCP servers, so it sees the data those tools handle; the audit and key store lives in the SQLite file at SENTINEL_DB_PATH, which should be protected. Policy, approval and PII behavior should be verified before relying on it, since the manifest lists no tools and the README gives no configuration details.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Buy me a coffee]

MCP Infrastructure Suite

The missing infrastructure layer for Model Context Protocol ecosystems.

[CI] [codecov] [npm scope] [License: Apache 2.0] [MCP Spec 2025-11-25] [Node >= 24] [pnpm] [Smithery Ready]

mermaid

flowchart LR    Shared["@oaslananka/shared"]    Forge["@oaslananka/forge"]    Sentinel["@oaslananka/sentinel"]    Atlas["@oaslananka/atlas"]    Composer["@oaslananka/composer"]    Bridge["@oaslananka/bridge"]    Observatory["@oaslananka/observatory"]    Lab["@oaslananka/lab"]
    Shared --> Forge    Shared --> Sentinel    Shared --> Atlas    Shared --> Composer    Shared --> Bridge    Shared --> Observatory    Shared --> Lab
    Clients["IDE / Agent / SDK clients"] --> Sentinel    Clients --> Composer    Composer --> Backends["Backend MCP servers"]    Sentinel --> Backends    Forge --> Composer    Forge --> Sentinel    Atlas --> Clients    Observatory --> Sentinel    Observatory --> Forge    Lab --> Composer

flowchart LR    Shared["@oaslananka/shared"]    Forge["@oaslananka/forge"]    Sentinel["@oaslananka/sentinel"]    Atlas["@oaslananka/atlas"]    Composer["@oaslananka/composer"]    Bridge["@oaslananka/bridge"]    Observatory["@oaslananka/observatory"]    Lab["@oaslananka/lab"]
    Shared --> Forge    Shared --> Sentinel    Shared --> Atlas    Shared --> Composer    Shared --> Bridge    Shared --> Observatory    Shared --> Lab
    Clients["IDE / Agent / SDK clients"] --> Sentinel    Clients --> Composer    Composer --> Backends["Backend MCP servers"]    Sentinel --> Backends    Forge --> Composer    Forge --> Sentinel    Atlas --> Clients    Observatory --> Sentinel    Observatory --> Forge    Lab --> Composer

Why mcp-suite?

Most MCP projects stop at the server boundary. mcp-suite focuses on the harder production layer around it: transport compatibility, trust boundaries, orchestration, discovery, observability, and operator workflows. That makes it useful once you move past a single local demo and start running MCP in teams, CI, or internal platforms.

The suite is built for guarded GitHub-hosted release automation, with every publishable package prepared for public npm publishing under the @oaslananka scope. The monorepo stays strict TypeScript, Turborepo, pnpm, and release-please manifest based.

Compared with one-off MCP utilities, the packages here are designed to compose: shared defines the protocol/runtime baseline, sentinel and composer control traffic, forge orchestrates work, atlas catalogs capability, bridge generates servers, observatory closes the feedback loop, and lab gives contributors a desktop workbench.

Packages

Package	What it does	Docs
`@oaslananka/shared`	Shared MCP protocol, transports, auth, retry, telemetry, and testing primitives	Shared docs
`@oaslananka/forge`	Pipeline engine for orchestrating MCP tools and external steps	Forge docs
`@oaslananka/sentinel`	Zero-trust security proxy with audit, approval, and PII controls	Sentinel docs
`@oaslananka/atlas`	Registry API and catalog UI for discovering MCP servers	Atlas docs
`@oaslananka/composer`	Aggregation proxy for multiple backend MCP servers	Composer docs
`@oaslananka/bridge`	OpenAPI and schema-first MCP server generation	Bridge docs
`@oaslananka/observatory`	Metrics, traces, anomaly detection, alerting, and dashboard UI	Observatory docs
`@oaslananka/lab`	Electron desktop workbench for connecting to and debugging MCP servers	Lab docs

MCP Lab Screenshot

[MCP Lab desktop screenshot]

Local Playground

The reproducible demo path is a local playground with seeded Atlas and Observatory data:

Then start Observatory in another terminal:

Open Atlas at http://localhost:4003, Observatory at http://localhost:4006, and Lab with pnpm --filter @oaslananka/lab dev. Full steps live in the local playground guide.

Quick Start

bash

pnpm install --frozen-lockfilepnpm build
# Seed and run Atlaspnpm --filter @oaslananka/atlas exec node dist/cli.js seed --db ./data/atlas.sqlitepnpm --filter @oaslananka/atlas exec node dist/cli.js serve --db ./data/atlas.sqlite --port 4003
# In another terminal, run Observatorypnpm --filter @oaslananka/observatory exec node dist/cli.js serve --db ./data/observatory.sqlite --port 4006

pnpm install --frozen-lockfilepnpm build
# Seed and run Atlaspnpm --filter @oaslananka/atlas exec node dist/cli.js seed --db ./data/atlas.sqlitepnpm --filter @oaslananka/atlas exec node dist/cli.js serve --db ./data/atlas.sqlite --port 4003
# In another terminal, run Observatorypnpm --filter @oaslananka/observatory exec node dist/cli.js serve --db ./data/observatory.sqlite --port 4006

Once the services are up:

Atlas UI: http://localhost:4003
Atlas health: http://localhost:4003/health
Observatory UI: http://localhost:4006
Observatory health: http://localhost:4006/health

Architecture

shared carries the protocol baseline, logger factory, transports, telemetry helpers, and test fixtures used everywhere else. MCP client-facing traffic is typically wrapped by sentinel for policy and audit, then aggregated through composer, or orchestrated from forge. atlas and observatory are HTTP-first operator surfaces, while lab is the developer-facing desktop entry point.

The suite currently defaults to MCP protocol version 2025-11-25 while keeping compatibility helpers for 2025-11-05 handshakes during the 1.0 transition.

Architecture decisions are recorded in the ADR index.

Development

bash

make installpnpm run format:checkmake lintmake typecheckmake testpnpm run securitymake test-coveragemake knippnpm run release:dry-run

make installpnpm run format:checkmake lintmake typecheckmake testpnpm run securitymake test-coveragemake knippnpm run release:dry-run

More setup and workflow guidance lives in docs/development.md, docs/testing.md, docs/security.md, docs/release.md, the generated API reference path in docs/api-reference.md, and the guide docs under docs/guide.

Release Policy

release-please manifest mode owns version bumps, changelogs, tags, and GitHub releases.
GitHub Actions builds npm package tarballs, a machine-readable release manifest, SBOM, checksums, and attestations from clean checkout state.
Production npm publishing is separate, environment-protected, and uses npm trusted publishing/OIDC after checksum, attestation, package-content, and clean-install verification.
Partial npm publication is resumable: identical immutable versions are skipped, missing versions publish in dependency order, and integrity conflicts fail closed.
Docs-only, internal-only, and CI-only changes do not publish to npm or update registry metadata.

Contributing

Contributions are welcome. Start with CONTRIBUTING.md, use Conventional Commits for user-visible changes, and keep GitHub Actions parity when adding validation steps. For issue triage, support, stale handling, labels, and maintainer response targets, see docs/governance.md.

Roadmap

@oaslananka/gateway: HTTP-first multi-tenant MCP gateway
@oaslananka/sdk: cross-language SDK surface starting with Python
Forge visual editor built on React Flow
Atlas federation across multiple registry instances
Observatory exports for Grafana and OTel collector pipelines
Sentinel policy integration with OPA

License

Source: README.md at commit 7c63ba0

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.0LatestSep 16, 2026

Score

50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
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
License10 pts