Skip to main content
Glama
aminehamlouchi

InterLogue

by aminehamlouchi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to InterLogue

No user-submitted related servers found.

    Related Servers

    • clearon-source-audit

      kwgoodwin
      A
      license
      B
      quality
      C
      maintenance
      Enables revision-bound source audits with exact article fingerprinting, claim-to-source mapping, quotation verification, and immutable JSON evidence reports for prepublication review.
      9
      MIT

    • NewsBlog Composer MCP

      Mohammed-Jameal-J
      A
      license
      A
      quality
      A
      maintenance
      Enables writers to research and verify news stories, extract facts with their sources attached, mine SEO keywords, receive a drafting brief, and audit their finished draft for weak spots and AI-sounding phrasing. It then assembles the publishing pack, NewsArticle and FAQPage schema, and SEO validation report around the text — without writing the prose itself.
      19
      1
      MIT

    • relationship-manager

      RUTURAJROCks
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to search people, retrieve evidence-backed facts and timelines, prepare briefs, rank reconnect opportunities, and propose outreach while keeping writes human-approved.
      MIT

    • Mission

      MaximilianoColoma
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables persistent work-state coordination with identity-bound assignments, governed lifecycle transitions, bounded queries, and auditable history.
      Apache 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.9/5.0

    Scored across 12 tools

    Disambiguation4/5

    Tools mostly map to distinct steps in a linear interview spine, but there is a potential confusion between the simulated text path (run_interview) and the real phone path (place_call + fetch_transcript), and between the fallback writer (generate_piece) and the preferred writer flow (draft_piece + check_citations). Fortunately, the descriptions explicitly clarify these boundaries, which mitigates the overlap.

    Naming Consistency4/5

    The names are mostly snake_case verb_noun (e.g., approve_contact, run_interview, fetch_transcript, check_citations). A few names are nouns or noun phrases (brief, question_templates, status), which is a minor deviation but still readable and consistent with the domain.

    Tool Count3/5

    With 12 tools, the count is not unreasonable, but three stubs (question_templates, download_recording, discover_contacts) are explicitly cut-list placeholders that add no real functionality and dilute the set. The remaining tools feel appropriately scoped for the interview workflow.

    Completeness4/5

    The surface covers the full spine from brief to approval to interview to piece generation and citation checking, with status reporting. However, the stubs represent unimplemented features, and there is no tool to update or delete briefs or transcripts, though the workflow may not require them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources