Skip to main content
Glama
Sign In
yof

yof

Official
by yof-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to yof

No user-submitted related servers found.

    Related Servers

    • 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.
      86 npm
      MIT

    • MCP Shield

      rob925
      A
      license
      C
      quality
      D
      maintenance
      Security scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.
      2
      1
      MIT

    • guardvibe

      goklab
      A
      license
      B
      quality
      B
      maintenance
      Security MCP server with 300+ rules for AI-generated code. Scans Next.js, Supabase, Clerk, Stripe, Prisma, Hono, GraphQL and 20+ modules. Zero config, runs locally.
      39
      2,157 npm
      6
      Apache 2.0

    • mcp-heimdall

      caglarbozkurt
      A
      license
      Not graded
      quality
      C
      maintenance
      Security scanner for MCP servers — vet an MCP before you wire it into an agent. Detects prompt-injection, credential exfiltration (via taint analysis), RCE, and supply-chain risks, and catches cross-server exfil chains no single server reveals. Zero-dependency local CLI, SARIF output, CI-gateable, no account.
      63 npm
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a sharply distinct role: yof_check (full scan), yof_check_diff (changed lines only), and yof_verify (single file re-check) are explicitly separated by scope, and yof_findings is explicitly stated not to scan locally. yof_explain (rule background) vs yof_fix_prompt (step-by-step fix) vs yof_verify (post-fix confirmation) are also cleanly differentiated, as are yof_patch_status (open PRs) and yof_lessons (merged fixes).

    Naming Consistency5/5

    Every tool uses the same yof_ prefix plus a lowercase snake_case noun/verb phrase, with no camelCase or style drift. The check/check_diff, patch_status/lessons, and explain/fix_prompt pairs read as a predictable family.

    Tool Count5/5

    Eight tools is well-scoped for a scan-diagnose-fix-verify lifecycle, and each tool earns its place by covering a distinct step. Nothing feels redundant or padded.

    Completeness4/5

    The surface covers scanning (full, diff, single-file), explanation, fix instructions, verification, cloud findings, and Patch PR/lesson tracking, which is a coherent lifecycle. Minor gaps exist: there is no tool to dismiss/ignore a finding, initialize or edit .yof.yml config, or trigger Patch to open a fix PR, so a few lifecycle steps end in a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources