Skip to main content
Glama
mambalabsdev

mcp-page-finder-extractor

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesYour Apify API token. Create one at https://console.apify.com/account/integrations

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_company_pageA

Give it a company domain and name a page type. It finds that page on the company's own website and returns the URL, the method that found it, and a confidence for THAT method. 46 page types are available: pricing, investor_relations, security_trust_center, careers, about, contact, terms_of_service, privacy_policy, partners, integrations, documentation, api_reference, status_page, changelog, press_newsroom, customers_logos, sustainability_esg and 29 more. Discovery reads the homepage and footer link graph, the sitemap and its shards, known third party hosts such as boards.greenhouse.io and statuspage.io, and anchor vocabulary in 11 European languages; guessing a URL path is the LAST method tried and is scored 0.6 or below. Read {type}_confidence and threshold at 0.8 for anything a customer will see, and read coverage and fetch_status before trusting a false: found=false means the site was read and the page is not there, found=null means not enough was readable to say, and the two are never collapsed. Set mode to locate_and_extract to also read the page and return structured fields, which costs an extra event per page. Every input returns exactly one row, including the empty ones. Requires an APIFY_TOKEN and consumes Apify credits. Read only.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no ambiguity or risk of selecting between overlapping functions. The tool's purpose is clearly defined and distinct.

Naming Consistency4/5

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.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues