Skip to main content
Glama
Sign In
oathe-mcp

oathe-mcp

Official
by oathe-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to oathe-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • agent-crashtest

      glibey
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server that lets agents scan a project's AI agent setup — Claude Code, Codex, Cursor, MCP servers and instruction files — and surface security findings such as the lethal trifecta, broad permissions, exposed secrets and unpinned packages.
      78 npm
      MIT

    • offsec-mcp

      nadirzhon
      A
      license
      B
      quality
      C
      maintenance
      MCP server for offensive-security tooling, enabling AI agents to run reconnaissance, CVE intelligence, JavaScript analysis, HTTP probing, and port scanning against authorized targets.
      10
      MIT

    • mcp-audit

      saagpatel
      A
      license
      Not graded
      quality
      A
      maintenance
      Audits MCP server configurations for security risks including capability inventory, SSRF, prompt injection, and drift detection. Works in read-only mode and can also be used as an MCP server to let AI agents audit their own attack surface.
      145 PyPI
      4
      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

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct action: submitting, checking status, retrieving a fast summary, retrieving a full report, and searching. Even the two report-style tools are clearly separated by their descriptions, which explicitly tell when to use each.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: submit_audit, check_audit_status, get_audit_report, get_skill_summary, search_audits. The pattern is uniform and easy to predict.

    Tool Count5/5

    The 5 tools are well-scoped for a focused security-audit service: submission, status tracking, report retrieval, quick check, and historical search. No tool feels redundant or missing.

    Completeness5/5

    The tool surface fully covers the audit lifecycle: submit an audit, poll for status, retrieve the report or a quick summary, and search past audits. There are no obvious dead ends or critical gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources