Skip to main content
Glama
sourcey

Sourcey

Official

Related Servers

Alternatives to Sourcey

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to search local repositories and retrieve bounded, cited source chunks, look up full indexed chunks, and inspect index statistics through read-only MCP tools over stdio.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local stdio MCP server that exposes tools for running evidence-first research with source-linked, replayable reports, plus replay, citation-audit, and Agent Reach health checks. It preserves fetched page text, exact quote offsets, hashes, and run traces so a client can verify that quotes match retrieved sources, while withholding arbitrary shell or local-file access.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides deterministic local development tools over stdio MCP, including repository mapping, code review, secret and dependency scanning, release checks, whitelisted checks, scaffolding, and workflow state tracking.
      38 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables stdio-only MCP clients to reach an agent-native venue where autonomous agents chat in rooms, post and team up on problems, create and claim bounties (first claim wins), search all content, and pull deterministic digests, with an optional API key unlocking mutating tools and free read-only access otherwise.
      MIT

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    The set splits into two clear domains (startup offers vs. Agent Readiness) with search/get/compare/inspect patterns that read as distinct actions. Within each domain the verbs are reasonably unambiguous, though the verbose, jargon-heavy descriptions for prepare_declaration, search_readiness, and search_offers create some risk of overlap confusion around eligibility vs. readiness.

    Naming Consistency5/5

    All eight tools use a consistent snake_case verb_noun pattern (compare_offers, search_offers, get_readiness, get_services, etc.). Verb choices map predictably to intent (search_ for collections, get_ for a single exact record, prepare_ for submissions). No camelCase or stylistic mixing.

    Tool Count5/5

    Eight tools is well-scoped for a read-mostly discovery/assessment server. Two coherent sub-domains (offers and readiness) are each covered with a small, focused tool set plus one meta-discovery tool, with no redundant entries.

    Completeness4/5

    The surface covers search, comparison, change tracking, provenance inspection, and single-record retrieval across both domains, plus service discovery and a submission-preparation path. Minor gaps remain, e.g. no dedicated get_offer for a single offer and no explicit listing of entities/subjects, though agents can work around via search.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues