maltego-mcp
Related Servers
Alternatives to maltego-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables LLMs to author Maltego .mtgx graph files and perform OSINT lookups, with an optional transform layer for pivoting into MISP, TheHive, Cortex, and MITRE ATT\&CK directly in Maltego Desktop.1351 npm11MIT
- AlicenseAqualityAmaintenanceIt functions as an OSINT bridge that allows AI agents to execute complex transforms and analyze entities within a persistent investigation graph. By leveraging its built-in tools and machine chains, it enables a native round-trip exchange of intelligence with Maltego Desktop.20404 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to perform OSINT link-analysis by exposing transforms (DNS, WHOIS, Shodan, etc.) as MCP tools for autonomous investigation and graph enrichment.MIT

Ontolocy MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceAugments an LLM with Ontolocy cyber graph capabilities, enabling natural language queries against a Neo4j graph database populated with MITRE ATT\&CK data.1MIT- FlicenseNot gradedqualityAmaintenanceEnables AI agents and LLMs to query codebase structure and data flow through Joern Code Property Graphs, supporting CPGQL queries, taint tracking, program slicing, and vulnerability hunting across multiple languages.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and LLMs to query codebase structure and data flow through Joern Code Property Graphs, supporting CPGQL queries, taint tracing, program slicing, and vulnerability hunting across many languages.-
TDQS
Scored across 52 tools
Most tools have clearly distinct purposes, especially with detailed descriptions. However, there is some overlap between the generic 'maltego_investigate' and the type-specific 'maltego_investigate_domain', 'maltego_investigate_email', 'maltego_investigate_ip', and between 'maltego_suggest_next_steps' and 'maltego_next_best_actions', which could cause confusion.
All tools follow a consistent 'maltego_' prefix with snake_case naming. Verbs are uniform and descriptive (e.g., list_*, create_*, delete_*), and compound names like 'investigate_domain' follow a predictable pattern.
52 tools is a large number for an MCP server, bordering on excessive. While the domain is complex, many tools (e.g., type-specific investigates, legacy 'suggest_next_steps') could be consolidated, making the surface feel heavy.
The tool set covers the full investigation lifecycle: graph management, entity/link CRUD, transforms, analysis, scoring, reporting, and learning. Minor gaps exist (e.g., no tool to clear all entities), but overall it is comprehensive.