Skip to main content
Glama
vinkius-labs

doc-breach-mcp

by vinkius-labs

Related Servers

Alternatives to doc-breach-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      A local-first MCP server that lets AI agents read any webpage as clean Markdown, crawl whole sites within configured limits, search without API keys, and solve supported captchas locally — all without cloud services or third-party keys.
      30
      13
      AGPL 3.0
    • A
      license
      A
      quality
      A
      maintenance
      Local MCP server for web search and page extraction, providing clean markdown from URLs, search results, site mapping, and research endpoints without API keys or accounts.
      5
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      A lightweight, zero-config MCP server that makes documentation and API specifications instantly accessible to AI models using the llms.txt standard. It enables searching and retrieving full documentation, OpenAPI, and AsyncAPI specs without requiring a complex RAG infrastructure or vector database.
      2 npm
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A locally-hosted MCP server that provides AI assistants with advanced web crawling capabilities, including structured data extraction, deep site crawling, and page screenshots. It enables users to convert single or multiple URLs into clean Markdown content for processing by LLMs without requiring external API keys for basic features.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Self-hosted Go MCP server that crawls documentation sites into local Markdown/JSONL corpora and lets agents read pages, run crawls, check freshness, and diff changes with zero network access at read time. Single static binary, no CGO, Apache-2.0.
      11
      100
      Apache 2.0

    TDQS

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: discovering sources, exploring structure, reading content, extracting specs, and searching within a known site. No overlap despite some similarity between discover and search.

    Naming Consistency5/5

    All tools follow the consistent 'docs_verb' pattern with imperative verbs, making the set predictable and easy to navigate.

    Tool Count5/5

    Five tools is an ideal size for a documentation assistant, covering core needs without excess.

    Completeness5/5

    The tool set covers the full workflow of finding, reading, mapping, and extracting documentation, with no obvious gaps for typical use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues