tasie-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@tasie-mcp Scan this code for vulnerabilities and suggest fixes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
TASIE MCP
TASIE — autonomous SAST + real exploit + human-gated remediation — exposed as an MCP app (NitroStack + NitroCloud), so ChatGPT and other MCP clients can scan code for vulnerabilities and get proof-carrying remediation.
This Node/TypeScript service is a thin MCP surface over the TASIE FastAPI
backend (demo/backend/). All detection, live exploitation and patching happens
in the Python engine; this app forwards tool calls over HTTP.
Architecture
ChatGPT / Studio ──MCP──▶ tasie-mcp (this app) ──HTTP──▶ TASIE FastAPI backend
(~90 engines + Docker
exploit sandbox)The backend URL is TASIE_API_BASE (default http://localhost:8000).
Stateless tools (
scan_code,scan_dependencies,detect_frameworks) send the code/manifest inline — they work against any reachable TASIE host.Backend-state tools (
remediate_file,scan_repo) act on files that live on the TASIE host and need the full Docker-enabled deployment.
Related MCP server: chatgpt-codex-local-mcp
Tools
Tool | Backend route | Needs Docker host | Purpose |
|
| no | Static scan of inline source → ranked findings (renders scan-report widget) |
|
| no | SCA over an inline dependency manifest |
|
| no | Fingerprint web framework(s) + attack surface |
|
| yes | Detect → live-exploit → patch → re-verify a host file |
|
| yes | Route discovery + scan of a repo on the host |
|
| no | Backend reachability + which endpoint is wired |
Setup
npm install # main app
npm --prefix src/widgets install # widget subpackage (or run `npm run dev`)
cp .env.example .env # then set TASIE_API_BASEStart the TASIE backend first (from demo/backend):
.venv/Scripts/python.exe -m uvicorn app:app --host 127.0.0.1 --port 8000Run
npm run dev # MCP server (STDIO) + widget dev server (:3001)Then connect in NitroStudio → Add Server → Nitro Project → this folder →
Studio App Canvas. Test scan_code on the Tools page; the TASIE Scan Report
widget renders the findings.
Deploy (NitroCloud → ChatGPT)
Set
TASIE_API_BASEto a publicly reachable TASIE host (a cloud VM/Docker host runningdemo/backend). NitroCloud deploys only this Node app — the Python engine + exploit sandbox must be hosted separately.In Studio App Canvas: Link to app / Create Cloud App → Deploy.
In ChatGPT: Settings → Plugins → Developer mode (Plus/Pro) → + → Server URL =
{serviceUrl}/sse→ Create → Connect.
Cloud builds run on Node 20 (
enginespins20.x). Local dev on newer Node works but test against 20 before deploying.
Config
Var | Default | Meaning |
|
| TASIE backend base URL |
| — | optional bearer token ( |
|
| per-request timeout |
Notes
ctx.loggeronly inside tools —console.*breaks the STDIO transport.Verified end-to-end:
scan_codeon a Flask SQLi sample returnscritical / CWE-89 / OWASP A03from the live backend.
Available Tools
6 toolsdetect_frameworksA
Fingerprint the web framework(s) in a source file (Flask, FastAPI, Django, …) and report where the request-handling attack surface is. Send the code inline.
Inputs: source (required).
remediate_fileA
Full verified remediation loop on a file already loaded on the TASIE host: detect -> live-exploit in a sandbox -> assemble patch -> re-verify. Requires the full Docker-enabled TASIE deployment (TASIE_API_BASE). Returns the proof and the proposed patch for human review.
Inputs: file.
scan_codeA
Statically scan a source file for security vulnerabilities using TASIE. Returns ranked findings (SQLi, command injection, SSTI, XSS, path traversal, deserialization, and ~90 more classes) with severity, CWE and OWASP tags. Send the code inline — no files need to exist on the server.
Inputs: content (required), filename.
scan_dependenciesA
Software Composition Analysis: scan a Python dependency manifest (requirements.txt / Pipfile / pyproject) for known-vulnerable packages. Send the manifest text inline.
Inputs: manifest (required), online, filename.
scan_repoA
Ingest a multi-file repository on the TASIE host: discover routes and scan every module for vulnerabilities. Requires the path to exist on the TASIE backend (full deployment).
Inputs: path (required).
tasie_healthA
Check that the TASIE backend is reachable and report which endpoint the MCP app is wired to.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct action: framework detection, vulnerability scanning (code, dependencies, repo), remediation, and health checking. No two tools appear to do the same thing, and their descriptions clearly delineate the use cases.
Five of six tools follow the verb_noun pattern (detect_frameworks, remediate_file, scan_code, scan_dependencies, scan_repo). The outlier is tasie_health, which uses a noun_health format and breaks the predictable verb-led pattern.
With six tools, the set is well-scoped for a security scanning MCP server. Each tool covers a distinct and necessary capability without redundancy or bloat.
The tool surface covers the core workflow: detect frameworks, scan code and dependencies, scan full repos, remediate, and check health. Minor gaps exist (e.g., no tool for managing or re-listing past findings), but no critical dead ends are present.
Maintenance
Related MCP Connectors
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
MCP server teaching AI agents to implement TideCloak: auth, E2EE, IGA, security analysis
Audit your MCP servers for poisoned tools and leaked secrets, and check AI-generated code for flaws.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP server that exposes a 60+ tool security and threat-intel stack to AI agents, enabling secret scanning, Sigma rule generation, ransomware lookup, OSINT, and deep research.1MIT
- FlicenseAqualityDmaintenanceA secure MCP server that exposes local repository context to ChatGPT/Codex with read-only access, path validation, and no generic shell.17-
- AlicenseNot gradedqualityAmaintenanceSelf-hosted MCP server that lets ChatGPT work with your local codebase through explicit tools.MIT
- AlicenseNot gradedqualityDmaintenanceLocal MCP server enabling Codex and ChatGPT to read/write files, execute commands, manage processes, use Git, and inspect images on the user's machine with full privileges.Apache 2.0