invenio-mcp
Related Servers
Alternatives to invenio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceExposes an OSINT investigation toolkit to any MCP-compatible AI client, which can drive passive checks such as DNS, WHOIS/RDAP, breach, IP reputation, GitHub and news-geo lookups and chain findings across them. The server lists 20 tools by default (16 passive plus 4 graph and batch helpers) and 25 when active checks are explicitly allowed, running via uvx with no separate install.820MIT
- AlicenseDqualityDmaintenanceA comprehensive MCP server providing tools for IP, domain, email, and image-based open-source intelligence. It integrates services like Shodan, VirusTotal, and HaveIBeenPwned to facilitate advanced security research and data gathering.5640 npmISC
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that exposes multiple OSINT tools to AI assistants like Claude, enabling sophisticated reconnaissance and information gathering tasks using industry-standard OSINT tools.246MIT
- -licenseNot gradedqualityNot gradedmaintenanceExposes popular OSINT and reconnaissance tools like Sherlock, SpiderFoot, and Holehe through MCP and HTTP APIs for AI assistants. Runs security research tools in sandboxed environments and returns normalized JSON results for investigation and analysis.1-
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes 108+ omega-cli OSINT tools for reconnaissance, web analysis, threat intelligence, and reporting, enabling AI assistants to perform comprehensive open-source intelligence tasks.MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects AI assistants to OpenCTI threat intelligence platforms. It enables natural language interaction for searching threat intelligence, analyzing reports, managing indicators, and monitoring connectors.-
TDQS
Scored across 4 tools
Each tool targets a clearly distinct action: checking email risk, creating an OSINT search task, retrieving search results, and checking account status. There is no overlap between the email-risk tool and the async search lifecycle tools, and the two get_* tools operate on clearly different resources.
All tool names follow a consistent invenio_ prefix plus verb_noun pattern: check_email_risk, create_search_task, get_search_task, get_account_status. The convention is predictable and readable.
Four tools is well-scoped for a focused OSINT/email-risk API wrapper. Each tool corresponds to a real operation and none appear redundant or filler.
The core workflows are covered: submit an OSINT search, poll for its results, run an email-risk check, and inspect remaining account limits. Minor gaps exist, such as listing or cancelling search tasks and possibly batch email checks, but agents can work around these.