Skip to main content
Glama
mcp-page-finder-extractor

mcp-page-finder-extractor

Related Servers

Alternatives to mcp-page-finder-extractor

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables enrichment of company domains with verified firmographic signals including tech stack, hiring activity, email infrastructure, and SOC 2 compliance, returning compact typed JSON for AI agents.
      3
      7 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to submit a business website URL and retrieve source-cited JSON details such as contact information, address, opening hours, social links, and open/closed status, with per-field provenance and confidence.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Extracts people (names and titles) from a company's team, leadership, or about page given a domain. Uses Apify to crawl and return structured data, with optional filters for seniority and email inclusion.
      1
      343 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables enriching company domains into structured firmographics including employee band, industry, HQ, founded year, revenue estimate, logo, and description, with source provenance and data completeness scoring.
      1
      116 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to analyze a company’s business and domain footprint from a domain or URL, gathering pricing, terms, app-store listings, tech stack, ad-library counts, financials, price history, and job postings with evidence and explicit uncertainty. It supports validated claim-based reports using public sources and a bring-your-own LLM key.
      3
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is nothing to confuse it with. Its purpose (locate a specific page type on a company's own domain, optionally extract structured fields) is stated precisely and its boundaries are explicit.

    Naming Consistency5/5

    A single tool named find_company_page follows a clear verb_noun snake_case convention. There is no opportunity for inconsistency within a one-tool surface.

    Tool Count3/5

    A single tool is thin for a server, though it is deliberately scoped as a focused, single-purpose capability. The heavy parameterization (46 page types, locate_and_extract mode) compresses what could plausibly be several tools into one, which is defensible but borderline.

    Completeness4/5

    The tool covers its stated read-only discovery purpose well, including confidence, coverage, and tri-state found semantics, and clearly declares out-of-scope behavior (no crawling, no third-party sites, no monitoring). Gaps are minor, e.g. no multi-page or batch lookup in one call, requiring repeated invocations.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues