Skip to content
winfunc
Winfunc MCP

Security review inside your AI editor.

Ask for a focused code review, compare a change, or bring file context into a security investigation, without opening another dashboard. The output gives your engineer more context; it never silently approves or ships a change.

Open WinfuncView setup
AvailableWorks with
  • Cursor
  • Claude Desktop
  • Windsurf
  • Cline (VS Code)
winfunc-mcp
tools/list
  • 01scan_snippetReview a snippet
  • 02scan_codebaseReview with file context
  • 03verifyCompare a change
transport stdio · sseavailable
Demo

Keep the review close to the change.

The recording shows the interaction in a supported AI editor. Results depend on the code you supply.

Winfunc MCP workflow demonstrationscreen recording
Tools

Three focused review actions.

Each action sends explicit code context to the configured winfunc endpoint and returns material for an engineer to assess.

scan_snippet01

Review a snippet

Send selected code with its language and get a focused security analysis, with an explanation and suggested changes.

winfunc_mcp.scan_snippet(  code="def login(user, pw): ..."  language="python")
scan_codebase02

Review with file context

Provide the file content and its path so the review can reason about more than an isolated line.

winfunc_mcp.scan_codebase(  file_path="app/models/user.py"  file_content="...")
verify03

Compare a change

Review a before-and-after change for security regressions before it moves forward.

winfunc_mcp.verify(  original_code="# before"  code_snippet="# after"  language="python")
Configuration

Connect a supported client.

  1. Create an API key

    Generate a key in the winfunc app. Keys are stored only as SHA-256 hashes and can be revoked at any time.

  2. Add the server to your client

    Paste the configuration into your editor's MCP settings. stdio and SSE transports are both supported.

  3. Try it on sample code

    Run a review on non-sensitive code first, then roll the workflow out to the team.

Create an API keyAsk about your setup

mcp.json

stdio · replace YOUR_API_KEY

{  "mcpServers": {    "winfunc-mcp": {      "command": "pipx",      "args": [        "run", "winfunc-mcp-server",        "--api-url", "https://api.winfunc.com",        "--transport", "stdio",        "--key", "YOUR_API_KEY"      ]    }  }}
Boundaries

Useful context, with clear boundaries.

Start on representative code and judge the quality of the evidence and suggested changes before wider adoption.

  • Security review without leaving a supported editor
  • Snippet, file-context, and before-and-after change analysis
  • Finding explanations with severity and code-location context
  • Suggested changes stay subject to engineering review
  • stdio and SSE transport options for supported clients
  • Language coverage follows the code and review context
Bring security into the editor

Review the change
while the context is fresh.

Try the MCP workflow, or talk with us about language, client, and data-handling requirements.

Open WinfuncTalk with the team