Skip to main content
Glama
jmshinhwa

ReadyStack Compliance Linters (40 MCP servers)

by jmshinhwa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ReadyStack Compliance Linters (40 MCP servers)

No user-submitted related servers found.

    Related Servers

    • Compileq

      PsylinksSecurityWeb
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI-assisted compliance scanning of codebases for GDPR, CCPA, WCAG, PCI-DSS, HIPAA, EU AI Act, and other regulations, providing risk scores, fine estimates, and suggested fixes within MCP-compatible IDEs.
      -

    • EU Compliance & Factur-X MCP

      EroNiiChan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to classify AI systems against the EU AI Act with requirement checklists and penalty exposure, generate and validate Factur-X / EN 16931 electronic invoices, and assess GDPR and NIS2 readiness directly from the IDE. Runs as a zero-dependency Python stdio server for Claude Desktop, Cursor, and similar clients.
      Apache 2.0

    • shipcheck-mcp

      noureldeensalama
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI agents to scan code for leaked secrets, copyleft licenses, unprotected routes, missing privacy policies, and risky card handling before committing or shipping.
      103 npm
      MIT

    • Meridian

      KNambiarDJsc
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first AI compliance scanner via Model Context Protocol, scanning codebases for violations of DPDPA 2023, RBI FREE-AI, SEBI AI/ML, and the EU AI Act.
      73 PyPI
      1
      Apache 2.0
    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

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct input type (text, file, directory) for the same lint operation, leaving no ambiguity about which to use based on the data source.

    Naming Consistency5/5

    All tools follow a consistent 'check_<input>' pattern, making the naming predictable and easy to learn.

    Tool Count5/5

    Three tools is perfectly scoped for the server's purpose of running Kubernetes removed API lints on different input forms; each tool earns its place.

    Completeness5/5

    The tool set covers all common input scenarios (text, single file, directory) for the linting domain, and the fixed 15-check set means no missing functionality for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources