Skip to main content
Glama
georgecurta

anonym-community-mcp

by georgecurta

Related Servers

Alternatives to anonym-community-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server that exposes the curated Sumi Docs corpus through four tools, enabling agents to query documentation content programmatically.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Zero-auth multi-source research MCP server that enables web search, reading URLs, PDFs, GitHub repos, and querying Hacker News, Stack Overflow, Semantic Scholar, and YouTube transcripts without API keys.
      10
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for grounded agentic Q&A over customer feedback, exposing typed tools to query a feedback corpus and return answers with citations to specific record IDs or a refusal when unsupported.
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that enables AI clients to search a knowledge base and retrieve complete source documents via narrow search and fetch tools.
      2
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      A Personal Knowledge-Base MCP Server that provides semantic search over a student-owned document collection using MCP, Gemini embeddings, and Qdrant. It exposes tools for searching notes, retrieving full documents, and listing indexed sources.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI tools to query a user's private, locally stored memories (notes, documents) with source citations, using the MCP protocol.
      10 npm
      MIT

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct content type: FAQ entries, pain points, structural drivers, jurisdiction statuses, research papers, and corpus metadata. The search tools are differentiated by their object type, and the descriptions explicitly state when to use each, so there is no overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., search_faq, search_pain_points, list_structural_drivers, lookup_jurisdiction, search_research_papers, get_corpus_stats). Verbs are action-appropriate and nouns clearly indicate the resource.

    Tool Count5/5

    With 6 tools, the server is well-scoped for its purpose of accessing a privacy research corpus. Each tool covers a distinct content type or metadata function, and none are redundant.

    Completeness5/5

    The server covers discovery and search across all major corpus components (FAQ, pain points, structural drivers, jurisdictions, research papers) plus a stats/metadata tool for valid filters. There are no obvious dead ends, as every tool returns the information needed for its use case.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues