Skip to main content
Glama
skyphusion-labs

@skyphusion/common-thread-mcp

Official
by skyphusion-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @skyphusion/common-thread-mcp

No user-submitted related servers found.

    Related Servers

    • ThreatWeaver

      Hadobot
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP-native agentic threat investigation server that investigates IOCs across multiple threat intelligence sources, correlates findings to detect campaigns, and outputs STIX 2.1 bundles.
      1
      -

    • CyberSecurityLab MCP Server

      dbolatti
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides an educational MCP server with cybersecurity examples, exposing a threat-intel lookup tool, an asset inventory resource, and an investigation prompt using simulated data.
      -
    • production-master-mcp by ProductionMasterAI

      production-master-mcpofficial

      ProductionMasterAI
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for the Production Master incident-investigation service, enabling any MCP client to drive investigations via tool calls with pass-through authentication.
      MIT

    • Pharus MCP

      rfalexandre
      F
      license
      C
      quality
      Not graded
      maintenance
      A Python MCP server for integrated discovery and querying of investigative services in the Pharus ecosystem. It exposes specialized tools for analyzing RIF, SIMBA, Telefônica, Telemática, KYT, and Graph data through a decoupled service architecture.
      63
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action within the investigation lifecycle, seed management, ingest, attribution, and manifest verification. The async job polling pairs (ingest_apify_twitter/get_ingest_job, attribute/get_attribution_job) are clearly separated. No two tools have overlapping responsibilities.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_, create_, get_, update_, delete_, add_, remove_, verify_, debug_). Minor deviations include 'health', 'investigation_summary', and 'attribute', which lack the standard verb prefix or object, but overall the naming is predictable.

    Tool Count3/5

    23 tools is at the heavy end for a single server, covering a full investigation pipeline with ingest, attribution, and manifest verification. While each tool has a specific purpose, the sheer number may overwhelm agents and suggests some tools (e.g., debug_* utilities) could be split into a separate server.

    Completeness4/5

    The tool surface covers the core workflow: create investigation, manage seeds, ingest data, run attribution, view runs, retrieve packets, and verify manifests. Missing features like listing all investigations or updating seeds are minor and can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources