Skip to main content
Glama
eyeinthesky6

unseen-mcp

by eyeinthesky6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to unseen-mcp

No user-submitted related servers found.

    Related Servers

    • Cortex

      liveevilkin
      A
      license
      Not graded
      quality
      D
      maintenance
      Obsidian-backed knowledge graph with semantic search, entity extraction, and cross-session memory. 11 MCP tools. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible editor.
      54 npm
      1
      MIT

    • omni-flow

      kanghelyu
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to create, customize, analyze and export relationship diagrams — theorem dependencies, paper maps, task RACI, org charts, conversation graphs — through 25 MCP tools, with cycle detection, centrality bottleneck reports, dependency closure and Mermaid/DOT/Markdown/JSON interop. Graphs stay local-first in a diff-friendly JSON source of truth and can be refined on a visual canvas.
      1
      -

    • Circuit

      brandononchain
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables building and running visual workflows conversationally inside Claude, orchestrating your existing connector tools step-by-step without storing credentials or owning integrations.
      8 npm
      MIT
    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

    A4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clear boundaries: detection, compilation, retrieval, revision, deterministic repair, semantic enhancement, and authentication are distinct operations. The main ambiguity is among revise_workflow, autofix_workflow, and enhance_workflow, since all can modify and return diagram artifacts, though their descriptions clarify structural delta edits vs deterministic connector healing vs semantic verification.

    Naming Consistency5/5

    Tool names consistently use snake_case with clear verb_noun phrasing: compile_workflow, revise_workflow, autofix_workflow, enhance_workflow, detect_workflows, get_workflow. The auth_* prefix groups authentication tools predictably.

    Tool Count5/5

    Nine tools is well-scoped for a workflow-diagram generation server, covering the core workflow lifecycle plus login. No tools appear redundant or unnecessary, and the count is within a manageable range for agent selection.

    Completeness4/5

    The surface covers the main workflow lifecycle: discovery, compilation, retrieval, revision, deterministic repair, and semantic enhancement, plus authentication. Minor gaps remain, such as listing/searching existing workflows or deleting/archiving them, but core agent workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources