Guardian Mcp

io.github.OraclesTechPublished by GitHub account OraclesTechv0.1.2Updated Oct 28, 2026

Runtime AI-threat screening for coding agents: analyze, scan tool calls/outputs & docs (paid).

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that screens coding-agent activity for AI threats, analyzing and scanning tool calls, outputs and documents (paid).

What you can do
  • Analyze coding-agent activity for AI-threat risk.
  • Scan tool calls and tool outputs before or as they are used.
  • Scan documents for screening results.
  • Run either against a hosted Guardian API or a self-hosted, zero-egress edition.
When to use it
Worth adding when you run coding agents and want a runtime screening layer over their tool calls, outputs and documents, and you are prepared to pay for a Guardian plan or self-hosted license.
Requirements
Runs as a local stdio process installed from the ethicore-guardian-mcp PyPI package, so a Python environment is needed. Hosted use requires an ETHICORE_API_KEY on the Pro plan or higher; the self-hosted edition requires ETHICORE_SELFHOST_LICENSE and ETHICORE_SELFHOST_PUBKEY. Desktop only.
Before you install
Paid product: hosted use needs a Pro-or-higher API key and self-hosting needs a Bronze-or-higher license. Two secrets are requested, ETHICORE_API_KEY or ETHICORE_SELFHOST_LICENSE, plus the entitlement key ETHICORE_SELFHOST_PUBKEY. In hosted mode, tool calls, outputs and documents are sent to the Guardian service; the self-hosted edition is described as zero-egress. No tool list is published, so review what it scans and whether it blocks or only reports.

Installation

In SourceWeft

  1. Open Guardian Mcp in the dashboard and add it to a workspace.
  2. 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.

Tools

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

Version history

1
  1. v0.1.2LatestSep 30, 2026

Score

25% 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

    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.