yads-mcp
Enables MCP-capable LLM agents to control YADS queues, manage tags, and trigger scans through YADS's API-authenticated /api/v1 interface without dashboard access. All actions respect tenant isolation and scan limits.
README
yads-mcp
MCP server that lets any MCP-capable LLM agent (Claude Code, or another
agent process reachable over the same network as YADS) drive queue
control, tagging, scan execution, and target/asset management through
YADS's own /api/v1 API, without a human at the dashboard.
It's a thin stdio wrapper around YADS's existing HTTP API
(/api/v1/queue/*, /api/v1/tags*, /api/v1/targets/*) — no separate
execution path, no bypassing tenant scoping or the scan-dispatch code
path. Every action taken through here is subject to the same tenant
isolation, concurrent-scan limits, and change-detection logic as the
dashboard.
1. Create an API key
From a machine already logged into YADS (session cookie), via
/developer or the /api-keys/ endpoint, create a key with the scopes
this agent needs:
read— status/list operations (queue_status, tags_list, scan_get_findings, list_targets, get_target, get_target_changes, get_scan_status, get_network_context, ...)write— tag mutations, and target mutations (add_target, undo_bulk_delete_targets, bulk_archive_targets, archive_dead_targets, restore_target)scan_execute— triggering scans (single or bulk)destructive— queue_purge, tags_delete_globally, bulk_delete_targets, bulk_blocklist_targets (also requiresconfirm=Trueon the call itself)
Copy the returned token now — it is never shown again.
2. Install
cd yads-mcp
python -m venv .venv
.venv/bin/pip install -e .
Tests
.venv/bin/pip install -e ".[test]"
.venv/bin/pytest tests/ -q
tests/conftest.py runs YADS in-process (Starlette TestClient) against
the same test Postgres/Redis stack as the yads repo's own tests
(docker-compose.test.yml in that repo, ports 5433/6380) — start that
stack first if these tests aren't passing.
3. Configure a client
Environment variables the server needs:
YADS_URL— e.g.https://yads.example.comYADS_API_KEY— the token from step 1
Claude Code
claude mcp add yads \
--env YADS_URL=https://yads.example.com \
--env YADS_API_KEY=<token> \
-- /path/to/yads-mcp/.venv/bin/python -m yads_mcp.server
or add to .mcp.json:
{
"mcpServers": {
"yads": {
"command": "/path/to/yads-mcp/.venv/bin/python",
"args": ["-m", "yads_mcp.server"],
"env": {
"YADS_URL": "https://yads.example.com",
"YADS_API_KEY": "<token>"
}
}
}
}
Tools
Queue & Scan Control
queue_status()queue_list_rate_limited_modules()queue_pause()/queue_resume()— fleet-wide, not tenant-scopedqueue_cancel_task(task_id)queue_purge(confirm)— destructive, tenant-scoped, 60s undo windowqueue_undo_purge(undo_batch)
Tagging & Organization
tags_list()tags_add_to_target(target_id, tag)/tags_remove_from_target(target_id, tag)tags_bulk_assign(target_ids, tags, action="add"|"remove"|"replace")tags_bulk_add_by_ids(target_ids, tag)tags_delete_globally(tag_name, confirm)— destructive, no undo
Scanning Execution
scan_trigger(target_url, profile="standard")scan_trigger_by_target_id(target_id, scan_types, scan_priority=None)scan_bulk_preview_count(only_roots=False, online_only=False, scanned_before=None)scan_bulk_by_criteria(scan_types, only_roots=False, online_only=False, scanned_before=None)scan_bulk_selected(target_ids, scan_types)scan_get_findings()
Target & Asset Management (Wave 2)
list_targets(tag=None, online=None, scan_status=None, domain_search=None, archived=False, last_scanned_before=None, page=1, limit=20)get_target(target_id)add_target(domain)bulk_delete_targets(target_ids, confirm)— destructive, 60s undo windowundo_bulk_delete_targets(undo_batch)bulk_archive_targets(target_ids)/archive_dead_targets()/restore_target(target_id)bulk_blocklist_targets(target_ids, confirm)— destructive, no undoget_target_changes(target_id, limit=30)get_scan_status(target_id)get_network_context(target_id)
Waves 3–10 (Reports & Export, Findings & Compliance, OSINT/Discovery/Intelligence, Integrations/Webhooks/Notifications) are tracked separately, each with its own design spec.
Changelog
See CHANGELOG.md.
License
MIT — see LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。