Skip to main content
Glama
Sign In
BerkayCelk

WikiPeatia MCP Server

by BerkayCelk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to WikiPeatia MCP Server

No user-submitted related servers found.

    Related Servers

    • Peptide Library MCP Server

      ryandelauz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search and retrieve structured peptide research profiles with cited, tier-labelled evidence, safety and regulatory status, and to compare two or three peptides side by side without ranking. Also provides research article and FAQ search, category and trend lookups, plus unit conversion, solution concentration, blend and cost-per-amount calculators, all read-only and anonymous.
      MIT

    • knowledgehub

      hikitni
      F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to search, read, and retrieve context from local knowledge bases with full-text search, absolute paths, and section-level details.
      4
      -

    • loci-mcp

      Ngoc18135
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and MCP hosts to query a locally built hybrid (vector + BM25) index of scattered notes, docs, and chat logs, retrieving answers with section-level citations. It exposes 8 tools plus resources and prompts so hosts like Claude Desktop, Cursor, and Cline can search, ask, and browse the user's personal knowledge base directly.
      -
    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

    B3.1/5.0

    Scored across 32 tools

    Disambiguation4/5

    Tools are mostly separable by prefix and resource, and descriptions explicitly distinguish similar ones (wiki_search vs corpus_search, corpus_ask vs corpus_deep_ask). However, there is still notable overlap among search/retrieval tools across wiki, corpus, and raypeat, which could cause occasional misselection.

    Naming Consistency4/5

    All names use snake_case with consistent domain prefixes (wiki_, corpus_, raypeat_), and most follow prefix_verb_noun. Minor deviations like wiki_read and noun-only corpus_health/corpus_library are readable and do not break predictability.

    Tool Count2/5

    32 tools is heavy for a single MCP server, even across three related domains; many retrieval/search variants could be consolidated or more clearly grouped. The count exceeds the recommended 15-tool range and increases selection burden.

    Completeness4/5

    The surface covers search, retrieval, metadata, discovery, QA, article listing, and corpus stats extensively, leaving few obvious retrieval gaps. It is read-oriented, so missing write/edit operations are acceptable for the apparent research purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources