Skip to main content
Glama
Sign In
mcp-api-guardian

mcp-api-guardian

by petrovicistefan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to mcp-api-guardian

No user-submitted related servers found.

    Related Servers

    • Specwise MCP Server

      Bytestay
      A
      license
      A
      quality
      C
      maintenance
      Enables coding agents to validate OpenAPI documents, detect breaking changes between API versions including against git refs, and validate JSON Schemas and data.
      3
      MIT

    • Specwise

      hybridforgelab
      A
      license
      A
      quality
      A
      maintenance
      Enables coding agents to validate OpenAPI documents and JSON Schemas, validate data against a schema, and diff OpenAPI versions—including against a git ref—to classify breaking changes and suggest semver updates.
      3
      MIT

    • LockSpec

      LockSpec
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with accurate OpenAPI contract details to prevent hallucinated API calls, supporting multi-version pinning, endpoint discovery, and request validation.
      42 npm
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation4/5

    audit_openapi targets a single document (lint/auth review) while compare_openapi targets two documents (breaking-change diff), so the action and input shape differ clearly. They share the same domain and both are static analysis, so an agent could momentarily hesitate, but the descriptions disambiguate well.

    Naming Consistency5/5

    Both tools follow the same verb_noun snake_case pattern (audit_openapi, compare_openapi), with the noun being the OpenAPI artifact. Fully predictable and readable.

    Tool Count3/5

    Two tools is thin for a server presented as an API guardian; linting and diffing are the core operations but little else is exposed. It is borderline rather than mismatched, since the stated scope is narrow.

    Completeness4/5

    Auditing and comparing cover the main lifecycle of reviewing OpenAPI specs, with honest scope caveats in the descriptions. Gaps exist (no spec fetching/resolution, no remediation or validation-report output tooling), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources