mcp-x-brand-presence-mapper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token. Required to call the Mamba Labs X Brand Presence Mapper actor. Get it 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| map_x_brand_presenceA | Resolve a company domain to that company's official X (Twitter) handle and profile URL, with follower count, bio and account age where X serves them. Returns one flat Clay ready row. Runs keyless out of the box and X rate limits that route aggressively, so on a large batch some rows return the handle and URL with the counts marked not_extractable; supplying your own X API bearer token removes that limit and returns full metrics at any batch size. A guessed handle that fails the identity check is reported as identity_mismatch rather than returned as the company's, and a company with no X account reports x_status not_found. Read x_status before any count. Read only; requires an APIFY_TOKEN and consumes Apify credits per call. |
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
There is only one tool, so there is no possibility of misselection or overlapping purpose. Its scope (domain → X handle/profile) is unambiguous from the name and description.
The single tool follows a clear verb_noun convention (map_x_brand_presence) in snake_case, matching the server name's domain. No inconsistency is possible with one tool, and the name is descriptive rather than vague.
One tool is thin for a server, though it is a substantive, focused operation rather than a trivial wrapper. A richer surface (e.g. reverse handle→domain lookup or batch helpers) would justify the server better.
For its narrow stated purpose, the tool covers the core lookup with thoughtful edge-case statuses (not_extractable, identity_mismatch, x_status not_found). Minor gaps exist, such as no reverse lookup or multi-platform presence mapping, but the essential operation is fully covered.