Skip to main content
Glama

Related Servers

Alternatives to http-semantics-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Serves offline document validation and evaluation operations of the Judgment Pack Specification to MCP clients over stdio, enabling agents to validate and evaluate JPS documents as tool calls. Supports conformance validation, experimental evaluation with disposition and error classes, and corpus testing.
      2
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLMs and agents to check their own work by calling tools instead of trusting assertions, covering symbolic math identities, sandboxed Python execution, JSON-Schema validation, dimensional analysis, and regex testing. Runs over stdio or streamable HTTP for use in Claude Desktop and remote gateway deployments.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes the Value Context Protocol SDK to MCP clients, enabling users to parse and validate VCP/I tokens, CSM1 codes, and VCP-Lite documents, encode the 18 VCP/A context dimensions, and map constitution principles to Schwartz values. Runs purely local over stdio or stateless HTTP with no network calls or stored state.
      35 PyPI
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      A dependency-free stdio MCP server that exposes typed Jev decision tools, enabling coding agents to make binary checks, routing choices, scored rubric ratings, and mixed judgments with calibrated probabilities. It validates questions locally and returns structured JSON results for use in agent workflows.
      692 npm
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools target clearly distinct HTTP semantics concerns (cache freshness, Vary matching, conditional preconditions, CORS). The two CORS tools (cors_evaluate for a single response, cors_simulate_fetch for a redirect chain) and the two cache-related tools (cache_evaluate for freshness, vary_match for field matching) are related but their scopes are differentiated in the descriptions.

    Naming Consistency4/5

    All names use snake_case with a domain_prefixed convention (cors_*, cache_*, conditional_*, vary_match). Mostly consistent, though cors_simulate_fetch breaks the domain_action pattern slightly with an extra verb.

    Tool Count5/5

    Five focused tools are well-scoped for a narrow HTTP semantics/RFC-conformance evaluator, with no redundant or filler entries. Each tool earns its place.

    Completeness4/5

    The set covers the core RFC 9111 cache reuse path (freshness + Vary), RFC 9110 preconditions, and CORS including redirects, which is solid coverage. Minor gaps exist (e.g., no explicit cache storage/no-store decision or combined end-to-end request evaluation), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues