Skip to main content
Glama
intesta-mcp

intesta-mcp

Related Servers

Alternatives to intesta-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to invoke registry-governed, fail-closed tools such as requesting child tasks in other domains, reporting results, querying a domain's context and contracts, and submitting or approving plans. All work is gated on real evidence (analysis, independent review, actual test runs), so a task can never be marked done without proof.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and agents to perform read-only lookups of dated on-record facts about agents, wallets, and endpoints, including evidence levels and history, so they can assess what is known before paying or relying on them.
      4
      121 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to check trustworthiness before recommending URLs, products, or organizations, with fail-closed pass/fail verdicts and attested-only recommendations.
      MIT
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to verify links and payments for scam risk before acting, returning deterministic allow/ask/deny verdicts with scores, reasons, and warnings using local checks.
      3
      1
      MIT
    • 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

    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

    ActivityStale
    ResponsivenessNo recent community issues