Skip to main content
Glama
Sign In
feature-separate-eval-mcp

feature-separate-eval-mcp

by 73882
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to feature-separate-eval-mcp

No user-submitted related servers found.

    Related Servers

    • feature-separate-batch-eval

      73882
      F
      license
      C
      quality
      C
      maintenance
      Enables users to analyze already-persisted single-patent evaluations to discover cross-patent batch issues such as language, technical-domain, input-structure sensitivity, and language-structure interactions, without modifying existing MCP, ledger, or single-record evaluation JSON.
      5
      -

    • USPTO Office Actions

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search and retrieve patent prosecution records, including full-text examination documents, examiner and applicant citations with AI/ML-enriched metadata, claim-level rejection data under 35 U.S.C. 101/102/103/112, and Commissioner final decisions on patent application petitions. It also supports raw-response passthrough for self-diagnosing upstream issues.
      230 npm
      MIT

    • Claude Patent Creator MCP

      AmitRossi4626
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables patent-rule lookup with citations over MPEP/USC/CFR via hybrid vector, lexical, and reranked search, plus prior-art searching across 100M+ patents through Google BigQuery. Also runs automated 35 USC 112 compliance checks on draft claims and applications and generates patent-style diagrams and flowcharts.
      -
    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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool covers a distinct stage of the evaluation workflow: status lists pending records, check performs a pre-flight evaluability test, and run executes the actual evaluation. There is no meaningful overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the same feature_separate_eval_ prefix plus a single clear verb: status, check, run. The naming pattern is entirely consistent and predictable.

    Tool Count5/5

    Three tools is appropriate for this focused evaluation pipeline. Each tool provides a distinct, necessary function, and none are redundant or ornamental.

    Completeness5/5

    The tool set covers the full workflow from discovering the next pending record, to verifying evaluability, to running the evaluation and persisting results. No critical missing operation is evident for the server's stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources