Skip to main content
Glama
agentlabbusiness

intesta-mcp

by agentlabbusiness
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to intesta-mcp

No user-submitted related servers found.

    Related Servers

    • a2a

      paul-salviani
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to check trustworthiness before recommending URLs, products, or organizations, with fail-closed pass/fail verdicts and attested-only recommendations.
      MIT

    • knowledge-trust-core

      haorantang97
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to get read-only trust verdicts on knowledge records by evaluating evidence maturity, provenance, intended use, risk level, and scope before deciding whether knowledge may be used.
      MIT

    • Gumi-MCP

      igv8101
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely inspect a local repository's code and metadata while blocking private data from leaving the machine, providing read-only tools for search, change tracking, and integrity verification.
      MIT

    • Safe MCP Server

      Rajnish9444
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read local business data and request database mutations, while requiring human approval before updates or deletions are executed. It provides read-only tools, approval workflows, and audit logging to prevent autonomous destructive changes.
      -

    • 404.directory

      MM-sheng
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to get evidence-backed allow, review, or block decisions before installing or invoking third-party tools, with trust-aware discovery, official docs search, and prediction-market risk preflight.
      1
      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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct step in the trust workflow: discovery via search_registry, trust assessment via check_trust, fact retrieval via get_facts, grounded Q&A via ask_entity, and interpretation via trust_ladder. Boundaries are clear, and descriptions explicitly guide when to use each tool.

    Naming Consistency4/5

    Most names use a consistent verb_noun snake_case pattern (search_registry, check_trust, get_facts, ask_entity). The one outlier is trust_ladder, which is noun-based rather than verb-based, but the overall convention remains readable and predictable.

    Tool Count5/5

    Five tools is well-scoped for a trust registry lookup server. Each tool has a clear purpose and no unnecessary redundancy, supporting a focused read-oriented workflow.

    Completeness4/5

    The toolset covers the core lifecycle: find entities, check trust, read facts, ask grounded questions, and explain the trust ladder. A minor gap is the lack of an explicit tool to verify returned passport signatures or hashes offline, though the descriptions suggest this can be done externally.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources