ARTEX MCP:a built-in server, an outside bridge and an MCP client.
MCP, the Model Context Protocol, lets an AI agent call tools on another system. ARTEX touches it three ways. Since v0.3.30 it can run its own MCP server so outside agents manage tasks. One separate repo bridges the ARTEX pentesting console to MCP clients. And ARTEX workers call remote MCP servers themselves. This page covers each, the ports involved and what the READMEs say about security.
- release that added the MCP server, 2026-11-14
- v0.3.30
- tools in the built-in server
- 11
- tools in the artex-mcp bridge
- 10
- default console and API port
- 8787
The built-in ARTEX MCP server:added in v0.3.30, off by default.
RuoJi6 released v0.3.30 on 2026-11-14 with an MCP server so outside agents can run tasks. The README says an outside agent, such as a personal assistant or a bot, can view tasks and findings, create tasks, and pause or resume them. An admin switches it on in System settings, under System and account, MCP server. While it is off, /mcp returns 404.
The README keeps two directions apart. The System, MCP page manages the external MCP servers that ARTEX's own agents call. The server described here is the endpoint ARTEX offers outward. Its address is your ARTEX address plus /mcp. It uses Streamable HTTP in stateless mode and answers in JSON only, with no SSE and no stdio. A client sends an access token as a bearer token. Tokens start with artex_mcp_ and are shown once, when created.
A token only sees the tools in its scopes. A token can also be limited to chosen companies, and it can carry a cap on unfinished tasks, a cap on tasks created per hour, an expiry date and instant revocation. The README notes that a company limit ties tasks to an asset scope and is not a network block, and points to asset blocking rules for a hard limit.
read scope
7 tools
list_tasks, get_task, get_task_graph, list_task_findings (without raw request and response traffic), list_companies, list_task_categories and list_llm_profiles (without API keys).
task:create scope
1 tool
spawn_task creates and starts a task. It can take company_ids and a category_id.
task:control scope
3 tools
pause_task, resume_task and add_task_hint.
Not exposed
Creating or editing custom tools, MCP servers or skills, reading or writing workspace files, LLM keys and system settings.
What defenders should know:/mcp does not use Basic Auth.
The README says /mcp skips HTTP Basic Auth and accepts only the access token. It does not accept the Basic credentials, the console password or the admin login token. Turning on Basic Auth therefore adds no protection to /mcp. The README points to a source allowlist of IP addresses or CIDR ranges, checked before the token, which answers 403 to every other source. Behind a reverse proxy, a trusted-proxy setting makes ARTEX read X-Forwarded-For only from proxies you list. Browser requests that carry an Origin header are refused with 403, and no CORS headers are sent.
Every call is logged with the token, tool, arguments, result, source address and time, including calls refused for a missing scope. The settings page keeps the latest 20,000. The README also warns that spawn_task starts real security tests, that text returned from a target can carry prompt injection, and that a public endpoint needs HTTPS because the token travels in a header.
ARTEX as an MCP client:remote servers and bundled tools.
In the other direction, ARTEX workers call MCP servers. The README lets a remote MCP use http (Streamable HTTP) or sse (the older SSE) in system settings, and the Docker image includes Playwright MCP, as the tool list on the how-it-works page shows. Some forks go further.
wpsec/ARTEX-Pro
ARTEX-Pro iteration
Bundles OWASP ZAP 2.17.0 with the MCP Integration add-on 0.4.0, started by default. The ZAP tools show on the MCP page, and Playwright MCP covers modern single-page apps.
MoLeft/ARTEX
v0.26.11.07.005
Browser MCP is no longer built in. System config has switches for Chrome and Lightpanda that create ordinary MCP entries named browser and lightpanda, which you can rename, restrict or remove on the MCP page. It also caps concurrent browser sessions, marked experimental.
TATHPE/ARTEX-Endfield
REA MCP
Connects REA, an MCP server and command line for binaries, APKs, firmware and JavaScript, as an MCP tool server, with a built-in step that seeds the bundled REA runtime.
azrielnan/artex-ko-main
REA MCP preset
Lists an optional REA preset on the MCP page for analyzing local programs and packages.
chu0119/Pojun
offensive-class
The README lists MCP presets for FOFA mapping, Playwright and Burp. This guide links only its fork page.
Fork page on artex.shFork page only: offensive-class builds are not linked
An outside MCP bridge:nu11b1ade/artex-mcp.
nu11b1ade/artex-mcp is a standalone stdio MCP server. It runs on the machine of the outside agent and manages ARTEX through its web address, so it works for Docker, binary and reverse-proxy setups. The README, in Chinese, says it needs web access and ARTEX admin credentials, reads passwords from files, indexes 315 HTTP method and route combinations from the nu11b1ade/ARTEX source at a pinned commit, and offers 10 tools. Hermes and Pi are its example clients, and the same stdio settings work in other MCP clients.
The README warns that the bridge holds the admin rights of the configured account and that routes can have real effects, including running Repeater requests and changing approvals or MCP settings. Callers should treat page, log and traffic text as data. A stdio bridge is a different design from the built-in server, which is Streamable HTTP with scoped tokens.
Session tools
4 tools
artex_status, artex_login, artex_initialize and artex_logout.
Credential tools
2 tools
artex_change_password and artex_configure_basic_auth.
Route tools
3 tools
artex_find_routes searches the catalog, artex_call runs a route and artex_read_events reads log and task streams for a limited time.
artex_browser
AGPL-3.0, last push 2026-11-03
An optional isolated Chromium for features that only exist in the web interface, such as the Repeater local workspace.
The ARTEX console and its ports:8787 for the console, 8788 for the proxy.
The ARTEX pentesting console is a Next.js web app embedded in the Go program. By default the console and API listen on port 8787, and the recording proxy that saves tool traffic uses port 8788 with its own certificate authority, as the how-it-works page lists. The README gives the MCP endpoint as the ARTEX address plus /mcp, not as a separate port number.
BaaRai v0.5.0, released 2026-11-04, made Docker publish port 8787 on 127.0.0.1 by default. The 0x7377 class kit shows the console at 127.0.0.1:8787 beside a CVE MCP server at 127.0.0.1:8800/mcp, with port 8000 inside its container network. Exposed consoles are a known problem, and v0.3.14 has a login bypass, so keep the console off the internet.
Keep reading:related pages and sources.
Related pages
Follow the ARTEX story.
New forks, releases and reports, dated and sourced.
