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. Use it when you need a specific page on a company's own site, such as pricing, careers, or investor relations; it does not crawl a whole site, read third party review or social sites, or monitor a page over time. 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.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

ActivityMaintained
ResponsivenessNo issues