Skip to main content
Glama
Seiya-wasabi

mcp-server-security-snapshot

by Seiya-wasabi

Related Servers

Alternatives to mcp-server-security-snapshot

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that audits other MCP servers. Run MCPWatch security scans from inside Claude Code or any MCP-compatible agent with 10 OWASP MCP Top 10 aligned checks and A-F letter grades.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for website reconnaissance. Gives Claude the ability to fingerprint tech stacks, audit security headers, map endpoints, analyze SSL certificates, enumerate DNS records, and scan ports.
      8,443 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.
      6 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that lets your AI coding agent (Claude Code, OpenClaw, Codex, Cursor, etc.) discover and pay on-chain agents registered on ERC-8004, using Coinbase's official x402 protocol. No smart account. No bundler. No relay. Just your EOA, an HTTPS request, and an automatic 402 → sign → retry flow.
      3
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing 11 pay-per-call web intelligence tools (page reading, PDF extraction, RSS parsing, screenshots, summarization, structured data extraction) for AI agents, paid automatically in USDC via the x402 protocol on Base mainnet with no API keys required.
      26 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that enables AI agents to fetch web content as clean, structured Markdown via NanoParse's hosted API, using x402 micropayments in USDC on Base.
      1
      22 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: demo_security_snapshot provides a static example for testing, while scan_security_headers performs an active scan of a URL's security headers. There is no functional overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun naming pattern (demo_security_snapshot, scan_security_headers) using snake_case. The verbs 'demo' and 'scan' clearly indicate their different actions, maintaining perfect consistency throughout the set.

    Tool Count2/5

    With only 2 tools, the server feels severely under-scoped for a security snapshot domain. While the tools are distinct, a security-focused server would typically need more operations (e.g., historical scans, configuration management, or additional scan types) to provide comprehensive coverage.

    Completeness2/5

    The toolset is highly incomplete for security snapshot functionality. It lacks core operations like retrieving past scans, managing scan configurations, or covering other security aspects beyond HTTP headers. Agents will face dead ends when trying to perform typical security audit workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues