What's Allowed
NPM · WHATS-ALLOWED-MCP
Merged agent permission rules: which settings file wins, and which rules your client ignores.
Available components
Last scanned (21 hours ago)
Scores higher than 65% of npm servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 94 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 460 tokens (~115/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/whats-allowed-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
permission_sources Which files decide, in what order ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Absolute path to the project directory whose permissions you want. Defaults to the server's working directory. |
No output schema declared.
No examples provided.
rule_findings Rules that do not do what they look like ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
unattended_surface What proceeds with nobody watching ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Absolute path to the project directory whose permissions you want. Defaults to the server's working directory. |
No output schema declared.
No examples provided.
whats_allowed What this agent can do without asking ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Absolute path to the project directory whose permissions you want. Defaults to the server's working directory. |
No output schema declared.
No examples provided.
How do I install the What's Allowed MCP server?
What's Allowed runs locally as an npm package, launched with npx -y whats-allowed-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · whats-allowed-mcp
claude mcp add stcmain-whats-allowed-mcp -- npx -y whats-allowed-mcp
What is the What's Allowed MCP server?
What's Allowed is an MCP server listed in the public MCP registry as io.github.stcmain/whats-allowed-mcp. Merged agent permission rules: which settings file wins, and which rules your client ignores. This page covers its npm package (whats-allowed-mcp).
Is the What's Allowed MCP server safe to use?
What's Allowed scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the What's Allowed MCP server expose?
What's Allowed exposes 4 tools: whats_allowed, permission_sources, rule_findings, unattended_surface. Their descriptions and schemas cost roughly 460 tokens of context every time the server is loaded.
Is the What's Allowed MCP server still maintained?
What's Allowed is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the What's Allowed MCP server under?
What's Allowed declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.