Skip to main content
Glama
GiantRavens

mdb-mcp

by GiantRavens
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to mdb-mcp

No user-submitted related servers found.

    Related Servers

    • scout

      tools-for-agents
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that fetches web pages, extracts clean markdown (reducing token count), caches results, and provides searchable reading history.
      MIT

    • pagewatch-mcp

      toolshedlabs-hash
      A
      license
      A
      quality
      C
      maintenance
      MCP server that provides read_page, screenshot, and pdf tools using a real browser, enabling agents to fetch clean markdown, screenshots, and PDFs from any URL.
      5
      19 npm
      MIT

    • svipall

      ilien-dev
      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.
      29
      3
      AGPL 3.0

    • agentfetch

      SID1ART
      A
      license
      Not graded
      quality
      D
      maintenance
      An open-source web retrieval MCP server that fetches, crawls, and searches the web, returning clean markdown for AI agents. It integrates with Claude MCP, LangChain, and other frameworks for agentic web access.
      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

    A3.6/5.0

    Scored across 16 tools

    Disambiguation3/5

    Several capture/read tools overlap: fetch_page, archive_page, and curate_to_corpus all render a page with provenance but differ mainly in where the result goes, so an agent could pick the wrong one. The watch_* family and download_video/download_document pairs are clearly differentiated, but the archive/capture cluster requires careful reading.

    Naming Consistency3/5

    Tool names mix verb-first patterns (fetch_page, download_document, submit_form) with noun-first names (page_links, page_forms) and prefixed family names (watch_add, watch_scan); archive_search vs search_web also reverses the word order. Within each functional family the naming is readable, but there is no single consistent convention across the set.

    Tool Count4/5

    16 tools is at the high end but each addresses a distinct job: fetching, searching, forms, downloads, archiving, corpus curation, and page watching. It is slightly above the ideal 3-15 range but not bloated.

    Completeness4/5

    The surface covers browsing (fetch, links, forms, submit), searching, downloading, archiving and archive search, corpus curation, and a full watch lifecycle (add, list, remove, scan, diff). Minor gaps exist, such as no direct update-watch operation or explicit tool to read an archived hit's full content by path, but core workflows are supported.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources