Skip to main content
Glama
KongFangXun

sofagent

by KongFangXun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to sofagent

No user-submitted related servers found.

    Related Servers

    • Proofpane by Proofpane

      Proofpaneofficial

      Proofpane
      A
      license
      B
      quality
      A
      maintenance
      A governance proxy for AI tools — every MCP/agent tool call is policy-gated, secret-redacted, and written to a hash-chained, offline-verifiable audit trail.
      13
      MIT

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

    • Pandaone Guard

      hellob1889
      A
      license
      A
      quality
      A
      maintenance
      Forces every AI Agent code change (Claude Code, Cursor, Trae) to leave a structured problem/reason/approach audit record before commit. 11 MCP tools with full annotations, pre-commit hook blocks unaudited changes. Local stdio, no API key, MIT. M8ven Trust 100/A.
      11
      MIT

    • gitl

      akomyagin
      A
      license
      Not graded
      quality
      A
      maintenance
      AI code reviews and git activity digests with machine-readable risk scoring, available as an MCP server for use within an agent session.
      1
      MIT
    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

    C2.8/5.0

    Scored across 105 tools

    Disambiguation2/5

    The domain prefixes help organize the tools, but multiple clusters have unclear boundaries: read_think/read_think_md, create_agent/activate_workflow, fde_compose/fde_deploy/workflow_create, evaluate/eval_suite/evaluate_output, and data_push/device_data_push are easy to confuse. An agent navigating 105 tools will frequently struggle to pick the correct one without very careful description reading.

    Naming Consistency3/5

    All names use snake_case and many follow a domain-prefix pattern like train_*, fde_*, workflow_*, and pr_*, which is helpful. However, the action position is inconsistent: workflow_create is domain-action while activate_workflow is action-domain, and run_audit/audit_file/audit_trail mix styles. The pattern is readable but not predictable.

    Tool Count1/5

    105 tools is far beyond the 50+ threshold for an extreme mismatch. Even accounting for the broad enterprise-agent domain, the surface is far too large for an agent to navigate efficiently and for the set to feel curated.

    Completeness2/5

    Coverage is wide, but several common lifecycle operations are missing: no workflow deletion/deactivation, no agent update/delete, no training cancellation/stop, and no connector/device unregister. These are significant dead ends for an operations-focused platform and will cause agent failures when decommissioning or stopping resources is required.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources