Website Phrase and Business Model Classifier MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call needs one. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| classify_websiteA | Classify company websites from their own pages. Give domains (up to 500) and optionally your own phrases. For each domain the actor reads the homepage and up to 5 linked pages (about, products, services, wholesale, manufacturing, industries, pricing) and returns one row: business_model b2b, b2c, both, or unknown with the signals found; is_saas, is_ecommerce, is_agency, is_manufacturer, is_wholesaler, is_distributor, is_marketplace; phrases_matched and phrases_negated; and top_evidence_text with top_evidence_url quoting the page. Rules are deterministic, no language model. Unreachable, blocked, robots.txt disallowed, and empty sites come back free with a row_status saying so. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per domain classified. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of selecting the wrong tool. Its purpose—classifying websites by business model and phrase matches—is clearly stated.
The single tool follows a clear snake_case verb_noun convention: classify_website. There are no competing naming styles to create inconsistency.
A single batch-oriented classification tool is well matched to this narrow, read-only domain. The count is lower than the typical 3–15 range, but the server's scope does not demand separate operations.
The tool covers the core classification workflow with detailed per-domain outputs and statuses for unreachable or blocked sites. Minor gaps exist, such as no dedicated run-status or results-retrieval tool, though the synchronous response largely obviates that need.