Skip to main content
Glama
Sign In
Kaushalendra-Marcus

evident

by Kaushalendra-Marcus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to evident

No user-submitted related servers found.

    Related Servers

    • extrapify

      christ0pper
      A
      license
      A
      quality
      D
      maintenance
      Structured web context infrastructure for AI agents. Extract reliable schema-guided JSON from websites using Claude-powered parsing, Browserless fallback rendering, and MCP-native workflows.
      1
      1
      MIT
    • webpeel by webpeel

      webpeelofficial

      webpeel
      A
      license
      Not graded
      quality
      B
      maintenance
      The web data platform for AI agents. Fetch, search, crawl, extract, monitor, and screenshot any URL. 55+ domain extractors, 65-98% token savings. 7 MCP tools included.
      332 npm
      12
      AGPL 3.0

    • AgentQL MCP Server

      Saga43460
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to extract structured data from web pages by giving a URL and a natural-language prompt describing the fields to retrieve. It exposes this capability as an MCP tool that plugs into clients like Claude, VS Code, Cursor, and Windsurf.
      237 npm
      MIT

    • ratatosk

      PabloSergi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to build, run, and repair deterministic web scrapers through MCP tools, and to fetch scraped data without needing a model at runtime.
      16 npm
      Apache 2.0
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools mostly have distinct purposes: fetch grabs raw content, extract does structured LLM extraction, recipes are deterministic parsers, health_check verifies things. There's some boundary fuzziness between fetch and extract (both fetch a URL), and between extract and use_recipe (both produce structured data), but descriptions strongly clarify which to use when.

    Naming Consistency4/5

    Tools use consistent snake_case naming with imperative verbs (fetch, extract, list, use, health_check). 'list_recipes' and 'use_recipe' pair well, and 'health_check' is clear. Minor inconsistency: health_check is a compound noun rather than verb_noun, and 'extract'/'fetch' are bare verbs without object nouns, though still readable.

    Tool Count5/5

    Five tools is well-scoped for a web-scraping/extraction server. Each tool serves a distinct layer of the pipeline (fetching, LLM extraction, deterministic recipes, recipe invocation, health verification), with no redundant or padding tools.

    Completeness4/5

    The surface covers the full extraction lifecycle: discover recipes (list_recipes), use them (use_recipe), fall back to generic extraction (extract), basic fetching (fetch), and verification (health_check). Minor gap: no listing or discovery of available entities/boards beyond recipes, and no way to retrieve cached/past results, but the core workflow is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources