Skip to main content
Glama
jietianliang

specir-mcp

by jietianliang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to specir-mcp

No user-submitted related servers found.

    Related Servers

    • OpenPapers

      arjhinety
      A
      license
      B
      quality
      A
      maintenance
      Enables provenance-first scholarly retrieval, paper ingestion, and reproducible research workflows by searching academic and developer sources, extracting source-located facts and claims, and preserving evidence and provider uncertainty for MCP clients.
      37
      1
      Apache 2.0

    • my-lit-mcp

      nlaanait
      F
      license
      C
      quality
      B
      maintenance
      Enables users to build and query a project-local literature database by ingesting papers from Semantic Scholar, PubMed, arXiv, and OpenAlex, caching open-access PDFs, extracting full text, ranking results, and exposing MCP tools for search, seeds, feedback, and pipeline status over stdio.
      16
      -

    • speclib-mcp

      rang501
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to search, discover, and retrieve technical specifications from a SpecLib instance. It provides tools for full-text search, scope listing, and reading specs as markdown content.
      -

    • mcp-rag-platform

      mittal-umang
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables retrieval-augmented question answering with source-grounded citations, document retrieval, and idempotent ingestion through MCP tools.
      -

    • knowledge-mcp

      gilanggsb
      A
      license
      A
      quality
      B
      maintenance
      Vendor-neutral MCP server for knowledge retrieval across repositories, offering stable tools for searching, getting, and listing documents with hybrid lexical and optional semantic search.
      3
      MIT
    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 5 tools

    Disambiguation4/5

    Each tool has a distinct primary purpose: resolve by name, fetch by UID, explain with context, search broadly, and status for system info. Resolve and fetch are similar but differentiated by input type (name vs UID), while explain is a composite of entity and section.

    Naming Consistency5/5

    All tools follow a consistent specir_ prefix followed by a clear action verb (resolve, fetch, explain, search, status). The pattern is uniform and predictable, making it easy to infer tool behavior from name alone.

    Tool Count5/5

    Five tools is ideal for a focused specification entity retrieval service. Each tool covers a distinct interaction mode without redundancy, and the count is well within the typical range for a useful MCP server.

    Completeness5/5

    The tool set covers the core needs for querying a spec database: search, targeted retrieval by name or UID, contextual explanation, and system status. No obvious lifecycle operations are missing because the domain is read-only retrieval, and the provided methods form a complete workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources