Skip to main content
Glama
nirhalfon

Cinch MCP Server

by nirhalfon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Cinch MCP Server

No user-submitted related servers found.

    Related Servers

    • pyntra

      prnvv2
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to orchestrate 100+ security tools over MCP for authorized penetration testing, including recon, scanning, exploitation, attack-chain planning, and knowledge-base retrieval.
      6
      Apache 2.0

    • Talos MCP Server

      arshabmohan03-hash
      F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to perform defensive security tasks such as vulnerability detection, CVE lookup, phishing/link safety checks, and security report generation via MCP tools.
      23
      -

    • secure-kb

      pavnxet
      A
      license
      B
      quality
      B
      maintenance
      Exposes seven MCP tools that let an AI coding agent detect a project's stack, fetch the priority security checks for that platform, search 2,057 OWASP-derived check cards with file-and-commit provenance, and record evidence-backed pass/fail results in a report.
      7
      MIT

    • SCML MCP Server

      ravindu57
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to enforce security policies by authorizing tool calls, scanning for prompt injection, checking memory writes, redacting PII, and accessing audit trails through MCP.
      -

    • iac-copilot

      togleid
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to search a security corpus, scan Terraform plan JSON for cited findings, and list sources via MCP tools grounded in CIS AWS Foundations and OWASP Top 10 CI/CD risks.
      3
      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

    A4.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing, running, retrieving, diffing checklists; retrieving protocols; mapping frameworks; searching threats; and collecting/verifying evidence. Even closely related tools like checklist_run and evidence_collect are clearly separated by static assessment vs. live probing.

    Naming Consistency5/5

    All tools use a consistent verb_noun snake_case pattern (e.g., checklist_list, protocol_get, evidence_verify). Minor synonym use like 'lookup' and 'search' does not break the overall predictable style.

    Tool Count5/5

    Nine tools is well-scoped for a security checklist/evidence server, covering discovery, assessment, cross-referencing, and evidence workflows without redundancy or bloat.

    Completeness4/5

    The set covers the core lifecycle: listing/running/retrieving/checklists, fetching protocols, mapping to frameworks, searching threats, and collecting/verifying evidence. The only notable gap is the lack of a protocol_list endpoint to enumerate available protocols without knowing names in advance, but this is workable.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources