five46
NPM · FIVE46 · SCANNED SEP 23
BYOK, fully local AI agent that tests your app/API and writes a real Playwright spec on success.
Available components
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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 125 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 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 815 tokens (~407/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the five46 MCP server?
five46 runs locally as an npm package, launched with npx -y five46. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · five46
claude mcp add sekharsdet-five46 -- npx -y five46
{
"mcpServers": {
"sekharsdet-five46": {
"command": "npx",
"args": [
"-y",
"five46"
]
}
}
} {
"servers": {
"sekharsdet-five46": {
"command": "npx",
"args": [
"-y",
"five46"
]
}
}
} codex mcp add sekharsdet-five46 -- npx -y five46
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sekharsdet-five46": {
"type": "local",
"command": [
"npx",
"-y",
"five46"
],
"enabled": true
}
}
} openclaw mcp add sekharsdet-five46 --command npx --arg -y --arg five46
mcp_servers:
sekharsdet-five46:
command: "npx"
args: ["-y", "five46"] {
"McpServers": {
"sekharsdet-five46": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"five46"
]
}
}
} assistant mcp add sekharsdet-five46 -t stdio -c npx -a -y five46
{
"mcpServers": {
"sekharsdet-five46": {
"command": "npx",
"args": [
"-y",
"five46"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −2
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −2
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 23 Sept 2026 · Analysed npm/five46@0.2.3
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 →
Dependencies 125 packages
| Packages resolved | 125 |
|---|---|
| Stale | 31 |
| 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 →
five46_api ~375
Drive real HTTP requests toward a stated goal, one request/assertion at a time, using your own configured LLM key (BYOK). Writes a real, standalone node:test script on success. Read-only for this server (GET/HEAD/OPTIONS only) — set FIVE46_MCP_ALLOW_WRITES=1 in the server environment to unlock POST/PUT/PATCH, FIVE46_MCP_ALLOW_DELETES=1 to separately unlock DELETE. Neither is ever settable via a tool call argument. Requests are restricted to the target base URL's own origin — no additional host allowlist is available via this tool. Discloses: request/response data, including response bodies (which may contain a live session token or other secret), is sent to your configured LLM provider on every step. On a real assertion failure, one additional LLM call analyzes the failure for a root-cause hypothesis — built only from information already visible to the agent during the run, always on for this tool, and included in the returned report as a hypothesis, not a confirmed diagnosis.
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | yes | The live http(s) base URL to test |
| goal | string | – | What the agent should accomplish — provide exactly one of `goal`/`story`. A vague goal would burn real BYOK cost on an unfocused run. |
| maxSteps | integer | – | Step budget (default 15, hard-capped at 50 regardless of what is passed) |
| story | string | – | A raw, possibly multi-scenario user story/acceptance-criteria text to split into independent goals and run with bounded concurrency (see `concurrency` context, set via FIVE46_MCP_CONCURRENCY on the s… |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | array | – | Present only for a `story` call — one entry per split acceptance criterion, in the order they were run. |
| outcome | string | – | Present only for a plain `goal` call (never a `story` call — see acceptanceCriteria instead). |
| passed | boolean | yes | Whether this call fully succeeded — for a plain goal, outcome === "goal-reached"; for a story, every acceptance criterion reached goal-reached. |
| specPath | string | – | Absolute path to the generated spec file — present only for a plain `goal` call. |
No examples provided.
five46_test ~440
Drive a real local Playwright browser toward a stated goal, one action at a time, using your own configured LLM key (BYOK). Writes a real, standalone, re-runnable Playwright spec on success. Discloses: the page's visible text/labels/values are sent to your configured LLM provider on every step. Clicking an element that looks like it deletes/deactivates/closes an account or permanently erases data (e.g. "Delete Account") is blocked for this server — set FIVE46_MCP_ALLOW_DELETES=1 in the server environment to unlock it. Never settable via a tool call argument. This is a best-effort heuristic on the clicked element's visible text, not a guarantee. On a real assertion failure (a genuine finding about the app, not a tooling issue), one additional LLM call analyzes the failure for a root-cause hypothesis — built only from information already visible to the agent during the run (never a new disclosure), always on for this tool, and included in the returned report as a hypothesis, not a confirmed diagnosis.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | What the agent should accomplish — provide exactly one of `goal`/`story`. A vague goal would burn real BYOK cost on an unfocused run. |
| headed | boolean | – | Watch it drive a real visible browser instead of headless (default false) |
| maxSteps | integer | – | Step budget (default 15, hard-capped at 50 regardless of what is passed) |
| storageStatePath | string | – | Relative path (under the configured project root) to a session file previously captured by `five46 login` — starts the browser already authenticated |
| story | string | – | A raw, possibly multi-scenario user story/acceptance-criteria text to split into independent goals and run with bounded concurrency (see `concurrency` context, set via FIVE46_MCP_CONCURRENCY on the s… |
| url | string | yes | The live http(s) or file:// URL to test |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | array | – | Present only for a `story` call — one entry per split acceptance criterion, in the order they were run. |
| outcome | string | – | Present only for a plain `goal` call (never a `story` call — see acceptanceCriteria instead). |
| passed | boolean | yes | Whether this call fully succeeded — for a plain goal, outcome === "goal-reached"; for a story, every acceptance criterion reached goal-reached. |
| specPath | string | – | Absolute path to the generated spec file — present only for a plain `goal` call. |
No examples provided.
What is the five46 MCP server?
five46 is an MCP server listed in the public MCP registry as io.github.sekharsdet/five46. BYOK, fully local AI agent that tests your app/API and writes a real Playwright spec on success. This page covers its npm package (five46).
Is the five46 MCP server safe to use?
five46 scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 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 five46 MCP server expose?
five46 exposes 2 tools: five46_test, five46_api. Their descriptions and schemas cost roughly 815 tokens of context every time the server is loaded.
Is the five46 MCP server still maintained?
five46 is still listed as active in the MCP registry. We last reached this channel on 23 September 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 five46 MCP server under?
five46 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.