mcp-page-finder-extractor
Related Servers
Alternatives to mcp-page-finder-extractor
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables 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.33 npmMIT
- AlicenseAqualityAmaintenanceExtracts 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.141 npmMIT
- AlicenseAqualityAmaintenanceEnables 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.143 npm1MIT
- AlicenseAqualityAmaintenanceMonitors a company domain for changes in hiring, tech stack, funding, firmographics, and social presence, returning only the deltas as typed change events.149 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables detecting what a website is built with—such as ecommerce platforms, CMSs, JS frameworks, analytics, and CDNs—by reading the page itself, returning evidence for each detection and listing detection coverage.MIT
- AlicenseNot gradedqualityBmaintenanceDomain and company intelligence for AI agents. Enables vetting companies, qualifying leads, and mapping targets from free public data without API keys.1MIT
TDQS
Scored across 1 tool
With only one tool, there is no ambiguity or risk of selecting between overlapping functions. The tool's purpose is clearly defined and distinct.
The tool name 'find_company_page' follows a clear verb_noun pattern, but with only one tool, consistency across a set cannot be evaluated. The name is descriptive and appropriate.
The server has exactly one tool, which is minimal and feels thin. While the tool is comprehensive, the server could benefit from additional tools (e.g., listing all available page types or managing extraction settings) to feel more complete.
The tool covers page discovery and extraction for 46 page types, which is thorough for its domain. However, it lacks a way to programmatically enumerate the full list of supported page types, and no other operations are exposed, leaving a minor gap.