Skip to main content
Glama
labaccessnow

aiops-field-notes-mcp

by labaccessnow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to aiops-field-notes-mcp

No user-submitted related servers found.

    Related Servers

    • Cloud DevOps MCP Server

      alexcgodwin
      A
      license
      A
      quality
      A
      maintenance
      Enables AI clients to assess infrastructure-as-code deployment risk, generate incident response runbooks, review CI/CD delivery readiness, and calculate SLO error budgets through structured advisory tools. Runs locally over stdio without cloud credentials or external API calls, returning guidance for platform work, pull request review, and production readiness checks.
      12
      2,512 npm
      MIT

    • netops-field-notes

      labaccessnow
      A
      license
      A
      quality
      B
      maintenance
      Provides read-only network engineering analysis by parsing configs and logs to explain config changes, check CIS/PCI compliance, diagnose 802.1X issues, find embedded certificates, infer topology, and assess proposed changes before pushing them.
      12
      MIT

    • nable (finops-mcp)

      getnable
      A
      license
      A
      quality
      A
      maintenance
      Local-first FinOps MCP server. Ask about your AWS, Azure, GCP, and SaaS costs in plain English. Anomaly detection, rightsizing, idle-resource cleanup, and Jira/Linear ticketing. Credentials never leave your machine.
      10
      18
      Apache 2.0

    • Security & GRC MCP Server

      ninoajn
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables local security scanning and compliance gap analysis for code and text, detecting secrets, PII, and OWASP vulnerabilities, and assessing readiness across major frameworks like NCA, ISO 27001, NIST CSF, and SOC 2.
      -
    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.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: model cost estimation, GPU fit, RSS news, MCP config auditing, MCP server lookup, config diffing, and compliance checking. Even the two network config tools are cleanly separated by action (diff vs compliance), and the two MCP tools operate on different objects (client config vs server directory).

    Naming Consistency4/5

    Six of seven tools follow a clear verb_noun snake_case pattern: estimate_llm_cost, check_vram_fit, audit_mcp_config, lookup_mcp_server, explain_config_diff, check_config_compliance. latest_field_note is the one outlier since it is a noun phrase rather than an imperative verb, but it still uses the same snake_case convention.

    Tool Count5/5

    Seven tools is a well-scoped set for a field-notes oriented MCP server. Each tool addresses a distinct practical need without bloat or redundancy.

    Completeness4/5

    The toolkit covers its main workflows well: model selection has cost and VRAM checks, MCP sanity has audit and lookup, and network config has diff and compliance. Minor gaps exist, such as latest_field_note only fetching the most recent item and no way to submit servers to the directory or auto-fix audit findings, but these do not create dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources