# What's Allowed (npm · whats-allowed-mcp)

Merged agent permission rules: which settings file wins, and which rules your client ignores.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `whats-allowed-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/stcmain-whats-allowed-mcp/whats-allowed-mcp.md), [page](https://verifymcp.io/servers/stcmain-whats-allowed-mcp/whats-allowed-mcp)

## Channel facts

- Registry: `npm`
- Package: `whats-allowed-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 460 tokens (~115/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add stcmain-whats-allowed-mcp -- npx -y whats-allowed-mcp
```

### Codex

```bash
codex mcp add stcmain-whats-allowed-mcp -- npx -y whats-allowed-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stcmain-whats-allowed-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "whats-allowed-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add stcmain-whats-allowed-mcp --command npx --arg -y --arg whats-allowed-mcp
```

### Hermes

```yaml
mcp_servers:
  stcmain-whats-allowed-mcp:
    command: "npx"
    args: ["-y", "whats-allowed-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "stcmain-whats-allowed-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "whats-allowed-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 66, +61)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail
- [functional] Licence: MIT

### 2026-08-01 (score 5)

First indexed and scored.

## MCP tools (4)

### `whats_allowed` (~114 tokens)

What this agent can do without asking

Start here. One-call summary of the permission configuration in force for a directory: which settings files contribute, how many allow/ask/deny rules each carries, the winning defaultMode, blanket allows, hooks wired to tool use, and how many rules do not do what they look like they do. Use at session start, before an unattended run, or when a prompt appeared that you did not expect.

Input parameters:

- `dir` (string): Absolute path to the project directory whose permissions you want. Defaults to the server's working directory.

### `permission_sources` (~105 tokens)

Which files decide, in what order

Every settings file that can contribute permission rules, in documented precedence order, with whether it exists, whether it parsed, how many rules it carries, and what a leading `/` in its path rules anchors to. Use when a rule is not taking effect, when you cannot tell which file granted something, or to confirm a managed policy is or is not present.

Input parameters:

- `dir` (string): Absolute path to the project directory whose permissions you want. Defaults to the server's working directory.

### `rule_findings` (~132 tokens)

Rules that do not do what they look like

Permission rules whose documented behaviour differs from their apparent intent: rules Claude Code accepts and never consults, `/path` rules in user settings that anchor at the config directory rather than your project, wildcards without a word boundary, allow rules on commands that run other commands, and allow rules a deny or ask rule reaches first. Each finding cites the documented behaviour. Use before trusting a guard rail you wrote a while ago.

Input parameters:

- `dir` (string): Absolute path to the project directory whose permissions you want. Defaults to the server's working directory.
- `kind` (string): Restrict to one category of finding.

### `unattended_surface` (~109 tokens)

What proceeds with nobody watching

The parts of the configuration that let a tool call go through without a human: the winning defaultMode, blanket allow rules, extra directories granted, whether bypass and auto modes are disabled, and hook commands — which run on agent events without a permission prompt of their own. Use before leaving an agent running unattended, or when reviewing what a repo's settings would do on your machine.

Input parameters:

- `dir` (string): Absolute path to the project directory whose permissions you want. Defaults to the server's working directory.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/stcmain-whats-allowed-mcp/whats-allowed-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 5

## Links

- npm package: https://www.npmjs.com/package/whats-allowed-mcp
- Socket report: https://socket.dev/npm/package/whats-allowed-mcp
- Repository: https://github.com/stcmain/whats-allowed-mcp
- Website: https://shifttheculture.media/agent-tools
- Changelog RSS feed: https://verifymcp.io/servers/stcmain-whats-allowed-mcp/whats-allowed-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/stcmain-whats-allowed-mcp/whats-allowed-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/stcmain-whats-allowed-mcp/whats-allowed-mcp