BYOK, fully local AI agent that tests your app/API and writes a real Playwright spec on success.
MCPpedia last refreshed this data
io.github.sekharsdet/five46 is an MCP server that BYOK, fully local AI agent that tests your app/API and writes a real Playwright spec on success. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 59/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-sekharsdet-five46": {
"args": [
"-y",
"five46"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An autonomous AI testing agent that verifies your app or API actually works while you're still building it — fully local, using your own LLM key.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'five46' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked five46 against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in browser / ai-ml
MCP client bridge: connects to MCP servers and registers their tools on ctx.tools
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
The official MCP server implementation for the Perplexity API Platform
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
MCP Security Weekly
Get CVE alerts and security updates for io.github.sekharsdet/five46 and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An autonomous AI testing agent that verifies your app or API actually works while you're still building it — fully local, using your own LLM key.
You just changed something, and you want to know — right now, against the real running thing — whether it actually works, without first writing a test yourself. Give five46 a plain-English goal — "log in and confirm the dashboard loads," "create a user via POST, then confirm it via GET" — and an LLM, using your own OpenAI, Anthropic, Gemini, Groq, or AWS Bedrock key, drives your real app or real API, one real action at a time, and tells you honestly whether it worked, with a root-cause hypothesis if it didn't. Once it does, that exact run is captured as a real, standalone Playwright (or node:test) spec you keep — so the same check that helped you while you were building the feature becomes a permanent regression test afterward, with no five46 or LLM involved in ever running it again.

Status: early proof of concept, verified end-to-end against real live LLM keys across dozens of real-world sites and APIs.
If five46 is useful to you, a ⭐ on GitHub helps other people find it — much appreciated!
Most testing tools assume you already have a suite to run. five46 is built for the moment before that — mid-feature, before a test exists at all. Point it at what you're building, describe the outcome you expect in plain English, and keep re-running it as you keep changing code; once it's solid, the run it just did becomes your regression test, not a separate thing you write afterward.
Most AI-driven test-generation tools also run in a cloud sandbox: your app's traffic, screenshots, and DOM leave your machine and go through a third-party service you don't control. five46 is the opposite bet — everything runs on your laptop, using a key you already pay for, and the only thing that ever leaves your machine is the text sent to your chosen LLM provider on each step (always disclosed, never hidden). If your organization can't adopt a cloud-hosted AI testing platform for compliance or trust reasons, this is built for exactly that constraint.
It's also not a black box: every run ends with a real .spec.ts/.test.mjs file you can read, diff, commit to your repo, and run in CI with plain npx playwright test — no vendor lock-in, no proprietary runner.
.spec.ts (or node:test script for API tests) you can
re-run any time, with no five46 or LLM involved.getByRole() resolves uniquely to the exact element a
step acted on, the generated spec prefers it over a positional CSS
selecto