Skip to main content
Glama
Sign In
portveil-mcp

portveil-mcp

by roybogs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to portveil-mcp

No user-submitted related servers found.

    Related Servers

    • @qirabot/mcp

      qirabot
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to control mobile and desktop devices with natural language, including running automation tasks, taking screenshots, and managing devices.
      6
      5 npm
      MIT

    • tailscale-mesh-mcp

      R-zin
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to discover devices and perform connectivity diagnostics across a private Tailscale or WireGuard mesh through authenticated CLI or REST API backends. Supports safe dry-run simulations before affecting live node state.
      2
      Apache 2.0

    • benchfleet-mcp

      benchfleet
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely use real Android phones by listing devices, reading screens and UI elements, tapping, typing, launching apps, and running workflows only within allowed permissions and approvals, with every step recorded in an audit log.
      60 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.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action, and the descriptions explicitly disambiguate the tricky pairs: move_device vs rotate_device (chosen location vs next in list), rotate_device vs start_rotation (one-off vs scheduled), and list_devices vs get_device (all vs one). Even the connect/disconnect/reconnect trio is clearly separated by intent.

    Naming Consistency5/5

    Every tool follows a uniform snake_case verb_noun pattern (get_, list_, move_, rotate_, start_, stop_, reconnect_, disconnect_, update_, add_, remove_). The two-word forms like start_rotation/stop_rotation and move_device/rotate_device read as a coherent family.

    Tool Count5/5

    Fourteen tools sit in the well-scoped range for a device/VPN management server, and each one maps to a real operation (read, lifecycle, scheduling, account, locations). Nothing appears redundant or padding the surface.

    Completeness4/5

    Core lifecycle is fully covered: add/get/list/update/remove devices, connect/disconnect/reconnect, move/rotate/schedule, plus account and location lookups and an audit trail. The only visible gap is token management — list_activity reports 'tokens created' but no tool creates, lists, or revokes tokens.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources