Skip to main content
Glama
pranava0x0

sept11-mcp

by pranava0x0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sept11-mcp

No user-submitted related servers found.

    Related Servers

    • evidence-rag

      oguzhanozfe
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables local read-only search and retrieval of approved, current evidence via hybrid lexical and dense methods, with tools to get exact source spans, answer from cited passages, and create and verify recheckable evidence packets.
      MIT

    • studyproof

      Lapmlnex
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only search and context-pack creation over a local source library, letting AI assistants retrieve relevant excerpts and audit cited quotations.
      MIT

    • LegalQuants MCP

      onurkafk
      F
      license
      A
      quality
      C
      maintenance
      Enables searching a local catalog of LegalQuants community builds, inspecting individual listings and indexing status, and retrieving exact cited source excerpts from indexed GitHub repositories. All tools run locally and read-only, returning ranked results with revision, line numbers, and links while disclosing anything unavailable.
      4
      -

    • archive-org-mcp

      lesleslie
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only access to the Internet Archive's Wayback Machine and catalog, enabling retrieval of archived web captures, snapshot metadata, and catalog search.
      BSD 3-Clause
    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 10 tools

    Disambiguation4/5

    The two search tools (portal_search vs catalog_search) overlap in purpose but are sharply distinguished by source (live remote vs local metadata snapshot), and the get_document/get_page_text pair is clearly split into metadata vs verbatim text. portal_browse and portal_catalog_stats both expose counts and structure, which is the only mild boundary blur. Overall an agent can reliably pick the right tool.

    Naming Consistency3/5

    All names are snake_case and readable, but conventions are mixed: 'portal_' is used as a prefix on six tools while some follow prefix_get_noun (portal_get_document) and others prefix_noun (portal_browse, portal_changes_since), and the domain tools (citations_verify, doi_milestones, budget_lookup) drop the prefix entirely. Predictable enough but not a single uniform pattern.

    Tool Count5/5

    Ten tools is well-scoped for an archival research server: six core portal operations plus three focused domain tools (citation verification, settlement milestones, budget ledger). No tool appears redundant or padded.

    Completeness4/5

    The surface covers discovery (browse/search), retrieval (document metadata, page text), health/change tracking (stats, changes_since), and evidence verification (citations_verify) plus domain specifics — a strong lifecycle for an archive reader. The one gap is that fetching uncaptured documents requires an external command rather than a tool, but this is a deliberate design choice the descriptions call out.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources