Hostile‑Command‑Suite

Created By
cycloarcanea year ago
MCP servers for automated penetration testing and OSINT.
Overview

what is Hostile-Command-Suite?

Hostile-Command-Suite is a suite of MCP servers designed for automated penetration testing and Open Source Intelligence (OSINT) gathering.

how to use Hostile-Command-Suite?

To use Hostile-Command-Suite, set up the MCP servers as per the documentation provided in the GitHub repository, and execute the desired penetration testing or OSINT commands.

key features of Hostile-Command-Suite?

  • Automated penetration testing capabilities
  • Integration with various OSINT tools
  • User-friendly command interface for executing tests

use cases of Hostile-Command-Suite?

  1. Conducting security assessments for web applications
  2. Gathering intelligence on potential targets for security audits
  3. Automating repetitive penetration testing tasks

FAQ from Hostile-Command-Suite?

  • What is penetration testing?

Penetration testing is a simulated cyber attack against your computer system to check for exploitable vulnerabilities.

  • Is Hostile-Command-Suite free to use?

Yes! Hostile-Command-Suite is open-source and free to use.

  • Can I contribute to Hostile-Command-Suite?

Absolutely! Contributions are welcome, and you can find guidelines in the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cycloarcane
Star
1
Language
Python
License
View license
Category
security
Tags

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago