Skip to main content
Glama
adialaleal

cerif-mcp

by adialaleal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to cerif-mcp

No user-submitted related servers found.

    Related Servers

    • TogoMCP

      dbcls
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that gives AI assistants access to biological and biomedical RDF databases via SPARQL at the RDF Portal, as well as selected REST APIs (NCBI E-utilities, UniProt, ChEMBL, PDB, Reactome, Rhea, MeSH, and more).
      29
      15
      MIT

    • schema-org-mcp

      Theycallmeholla
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server enabling AI assistants to explore schema.org types, generate JSON-LD examples, validate structured data, and navigate the complete ontology with fuzzy matching and caching.
      5 npm
      21
      MIT

    • tendertool

      tendertoolai
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for TenderTool, enabling AI assistants to manage references and vault documents.
      MIT

    • paper-search-cli

      X-T-E-R
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for searching academic, patent, and web sources, normalizing identifiers, and managing workspace records. Exposes the same operations to AI clients via MCP tools.
      37 npm
      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

    A4.2/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing vs. getting entity/scheme, validating vs. building vs. analyzing vs. extracting vs. migrating. Even validate_xml and validate_file differ by input source, clearly described. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tool names follow a strict verb_noun pattern: list_entities, get_entity, build_link, validate_xml, analyze_document, migrate_15_to_16, etc. The verbs are consistent and the nouns clearly indicate the object, making the API predictable and easy to learn.

    Tool Count5/5

    13 tools is well-scoped for a domain as complex as CERIF 1.6. Each tool earns its place, covering catalog browsing, construction, validation, analysis, and migration without redundancy or bloat.

    Completeness5/5

    The tool surface covers the full lifecycle: discover entities/schemes, build entity/link/document fragments, validate against the official schema, inspect existing documents, and migrate from 1.5. No obvious gaps that would prevent an agent from working effectively with CERIF data.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources