INDIVIDUAL MCP TOOL
generate_threat_model
Create a threat model from a normalized architecture (ReactFlow nodes + edges).
LIVE ENDPOINT
https://mcp.aribot.ayurak.com/mcp
Connect to this endpoint to inspect the live schema for generate_threat_model and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description contains a write-action term.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.aribot-mcp]
url = "https://mcp.aribot.ayurak.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"aribot-mcp": {
"type": "http",
"url": "https://mcp.aribot.ayurak.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: aribot-mcp
Remote MCP URL: https://mcp.aribot.ayurak.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"aribot-mcp": {
"url": "https://mcp.aribot.ayurak.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"aribot-mcp": {
"type": "http",
"url": "https://mcp.aribot.ayurak.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "aribot-mcp",
"transport": "streamable-http",
"url": "https://mcp.aribot.ayurak.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
get_billing— Billing status + self-service payment for your company: credit-wallet balance, pay-per-use flag, license tier / annual commitment, per-action prices, purchasable plans, and any approved-but-unpaid plans.onboard_agents— Bulk-onboard agent identities to the governed fleet (Agent Governance).verify_threats_in_code— Verify whether threats are mitigated in a scan's uploaded code.get_traceability— Return the diagram→threat→finding→control→requirement→remediation traceability matrix for a scan in your scope, with coverage metrics.get_framework_coverage— Compliance-framework coverage for a diagram (real, ControlCodeMap-backed), optionally for one framework, plus an optional crossmap relationship graph.get_remediation— Compute a remediation plan for a threat/finding WITHOUT applying it (mode=dry_run).compliance_status— Company-level compliance posture rollup (pass rate, control compliance, mitigated counts, per-framework coverage).discover_shadow_ai— Shadow-AI posture (part of Code Security): unsanctioned / unknown AI-service usage discovered in code — totals, risk score, provider/type breakdown, hardcoded-key count, and top discoveries.