websec-validator (raccioly/websec-validator) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 4 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

websec-validator

Local-first security recon that briefs your AI coding agent: facts + tailored probes, code-in / artifacts-out. No LLM, no server, no running app.

→ raccioly/websec-validator· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

raccioly

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: TOKEN_A. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: WEBSEC_MCP_TOKEN, APIKEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretWEBSEC_MCP_TOKENThe optional HTTP transport is loopback-only and requires at startup:
configWEBSEC_INPUT_
configGITHUB_OUTPUT
configWEBSEC_CALIBRATION_HOME
configWEBSEC_ENRICH_DIR
configXDG_CACHE_HOME
configWEBSEC_HOOK_FAIL_ONcontinues to fail. changes the threshold; WEBSEC_HOOK_SCAN=1 executes scanners,
configWEBSEC_HOOK_SCANcontinues to fail. WEBSEC_HOOK_FAIL_ON changes the threshold; =1 executes scanners,
configWEBSEC_HOOK_SCANNERSand selects required adapters. The default is recon-only.
configTARGET
🔐 secretAPIKEY
configOBJ_B
configGROUP_B
configRULES_ENDPOINT
configOBJ_A
configTOKEN_A
configCOOKIE_A
configWEBHOOK_PATH
configSIG_HEADER
configTS_HEADER
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

4/4 tools missing one or more hints — websec_recon (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); websec_findings (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); websec_sarif (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Secrets stay with their owner

1 secret sent to a request target we could not resolve (TOKEN_A → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/raccioly/websec-validator)](https://m8ven.ai/mcp/raccioly/websec-validator)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 4448c3466afba5377b7641d481e151d9da11f356
code hash: 1faf7e1e310b42a0e4e175e20855ece70c4d151eb718059a87113791b7cc706d
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client