Skip to main content
Glama
Sign In
vaultre-mcp

vaultre-mcp

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to vaultre-mcp

No user-submitted related servers found.

    Related Servers

    • lendlord-mcp

      dniasoff
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to manage a Lendlord landlord account through its private JSON API, covering properties, documents, tenants, maintenance reports, tasks and alerts, rent, transactions, compliance, and filing emails against properties. Supports local stdio or hosted HTTP transports with credential-based login, optional TOTP 2FA, read-only mode, and once-per-session write confirmation.
      40
      26 npm
      MIT

    • Property MCP Server

      digitsouler
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to operate property management systems via natural language, covering repair orders, owner info, payments, notices, and inspections. Features a full agentic workflow with human-in-the-loop and observability.
      1
      MIT
    • SmartAgent CRM MCP Server

      SmartAgent CRM MCP Serverofficial

      smartagent-ru
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and act on SmartAgent real estate CRM data, such as finding leads, creating tasks, moving deals through pipelines, looking up property listings, and leaving notes.
      MIT

    • Joist MCP

      cotlet-connect
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to operate a user's signed-in Joist account, creating estimates, sending invoices, managing clients, and reviewing overdue payments through natural language without a Joist API key. It supports hosted MCP access plus a local stdio server for clients that require it.
      7
      Elastic 2.0
    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

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: reading, clicking, typing, guidance, status checking, opening, and closing. The boundary between vaultre_open and vaultre_guide is clear because one starts a session and the other provides instructions.

    Naming Consistency5/5

    All tools follow a consistent vaultre_ + verb pattern: vaultre_read, vaultre_click, vaultre_type, vaultre_guide, vaultre_status, vaultre_open, vaultre_close. The convention is predictable and easy to scan.

    Tool Count5/5

    Seven tools are well-scoped for a browser-automation server: a compact lifecycle of open, inspect, interact, check status, get guidance, and close. Each tool earns its place without redundant operations.

    Completeness4/5

    The surface covers the essential browser lifecycle and core interactions needed for VaultRE workflows. Minor gaps exist for specialized interactions like dropdown selection, file upload, scrolling, or waiting, but the read/click/type trio provides workarounds for most tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources