Skip to main content
Glama

Related Servers

Alternatives to docintel

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to transcribe insurance rate filings into executable rating engines with full citation tracking, supporting validation, review, and quote generation through MCP tools.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to extract structured data from PDFs with confidence scores and provenance, and to search, review, and correct documents via MCP tools, resources, and prompts.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to work with business-document data through MCP tool calls constrained by a registry, data tiers, human approval for writes, and a tamper-evident audit log. Ships with saved evals and a dashboard to prove and inspect those controls.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes life-insurance back-office tools (policy document search, application status, product/underwriting rules) to LLM agents. Enables agents to retrieve policy documents, check application status, and evaluate underwriting rules via hybrid search and rule lookup.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables enterprise MCP clients and partner agents to execute tenant-isolated underwriting, claims, and compliance workflows with durable step checkpointing, evidence-grounded tool calls, and deterministic PDF citation receipts. It supports A2A task dispatch and MCP JSON-RPC operations while blocking cross-tenant access and ungrounded deliverables.
      MIT

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct action+target: listing documents, running an extraction, fetching a stored result, and listing low-confidence fields. The only mild overlap is between get_extraction and list_low_confidence_fields, since both read extraction results, but the descriptions make the split (full result vs. review-needed fields) reasonably clear.

    Naming Consistency5/5

    All four names follow a clean snake_case verb_noun pattern (list_documents, extract_document, get_extraction, list_low_confidence_fields). Verb choice is meaningful: list for enumeration, extract for the write action, get for single-item fetch.

    Tool Count4/5

    Four tools is a coherent, small surface for a focused extraction service, and each one plays a role in the extract-then-review flow. It sits slightly on the thin side given the workflow it implies, but nothing here is redundant.

    Completeness3/5

    The surface covers listing documents, extracting, and reading results, but the human-review loop is a dead end: you can list low-confidence fields yet there is no tool to submit corrections, accept/reject an extraction, or re-run one. No delete, update, or batch extraction operations are exposed, which will limit agents working beyond the happy path.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues