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. 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
The set contains a single tool, so there is no possible confusion between tools. Its purpose—resolving a domain to an X (Twitter) profile—is specific and distinct. An agent will not misselect because there are no alternatives.
The sole tool uses a clear verb-object pattern: 'map' + 'x_brand_presence'. It is descriptive and free of any naming style conflicts since no other tools exist. Consistency is trivially maintained.
A single tool perfectly matches the server's narrow stated purpose of mapping X brand presence. The tool is substantial, with configuration and error handling, not a trivial stub. This is an appropriate, well-scoped size for a focused microserver.
For a read-only domain-to-X lookup, the tool covers all core needs: resolving the handle, verifying identity, returning metrics, and managing rate-limit outcomes. It also supports optional authentication for full metrics. No obvious missing operations exist for this specific task.