com.mambabuilt/mcp-ai-tooling-detector
Detect whether a company declares, deploys, or charges for AI, with evidence.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@mambalabsdev/mcp-ai-tooling-detectorclaude mcp add mcp-ai-tooling-detector -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-ai-tooling-detector@1.4.0
{
"mcpServers": {
"mcp-ai-tooling-detector": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-ai-tooling-detector@1.4.0"
],
"env": {
"APIFY_TOKEN": "<your apify_token>"
}
}
}
}
Environment variables
APIFY_TOKENrequired secret Apify API token from https://console.apify.com/account/integrations
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
AI Tooling Detector MCP Server
An MCP server that exposes the Mamba Labs AI Tooling Detector as a single tool. Install one package and give your MCP client a way to ask, for any company domain, whether that company only talks about AI, actually runs AI tooling on its site, or charges money for AI. It wraps the Mamba Labs actor on Apify and returns Clay-ready flat JSON.
What's Inside
- What it does
- Quick start
- Prerequisites
- Example prompts
- Tool and inputs
- Full actor documentation
- Mamba Labs GTM Suite
- License
What it does
This server gives an AI client one tool:
detect_ai_tooling: return anai_maturitytier for a company domain, plus the evidence behind it.
The tier has four levels and each one needs its own class of evidence:
| Tier | What it means | What proves it |
|---|---|---|
commercialized | The company charges for AI | AI credits, a token allowance, an AI add-on, an AI-named plan, or a per-outcome AI price on the pricing page |
deployed | AI tooling is running on the site | An AI-native vendor, a direct inference endpoint, or an AI-capable platform backed by AI copy |
declared | The company says AI, nothing observable | A validated llms.txt, AI crawler rules in robots.txt, or weighted marketing copy |
none | No signal fired | Nothing |
max_charge_usd | number | Optional cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. |
A domain sitting behind a bot challenge comes back with blocked: true at low confidence rather than as a confident no, so a challenged site is never mistaken for a company with no AI.
All of the work runs on Apify. This package is a thin client that routes the tool call to the actor and hands back the result.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config:
{
"mcpServers": {
"mamba-ai-tooling-detector": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-ai-tooling-detector"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}
Restart the client and the detect_ai_tooling tool appears.
Prerequisites
- Node.js 18 or newer
- An Apify API token from https://console.apify.com/account/integrations
Calls consume Apify credits, billed per domain analyzed. Free Apify plans get 15 results per calendar month.
Example prompts
- "Does intercom.com actually charge for AI, or do they just market it?"
- "Check notion.so, figma.com and berkshirehathaway.com for AI adoption and tell me which ones already pay for AI."
- "Which AI vendors are running on zendesk.com?"
- "Does cursor.com publish an llms.txt, and does their robots.txt block GPTBot?"
Tool and inputs
detect_ai_tooling
| Input | Type | Required | Description |
|---|---|---|---|
domain | string | one of these | A single company domain, e.g. intercom.com. |
domains | string[] | one of these | Batch mode. Takes precedence over domain. |
vendors | array | no | Report only these AI vendors, one or more of the 52 fingerprinted tools (sierra, decagon, intercom_fin, openai_api, anthropic_api, pinecone, langchain and the rest). The site wide AI maturity read is never narrowed by this. Omit for every vendor. |
check_pricing | boolean | no | Fetch and score the pricing page. Default true. Setting it false is faster but caps the result at deployed, because commercialized can only be proven on a pricing page. |
skipCache | boolean | no | Force a fresh analysis and ignore the 7 day result cache. |
request_timeout_ms | integer | no | Per-request timeout in milliseconds, 3000 to 20000. Default 9000. |
batchSize | integer | no | Batch mode only: how many domains the actor analyzes at once, 1 to 10. Default 5. |
The tool reads public data and writes nothing, but every call starts a paid Apify run, so it is not marked read only.
The tool starts the actor run and polls it to a finished status, so a long run is not cut off at 300 seconds. The run is allowed 1,800 seconds. If it is still going two minutes after that, the call stops waiting and returns the run ID with a link to it in the Apify Console, where the results land when it finishes. A run that does not succeed comes back as an error with its run ID and status.
Pricing
Price per event on the Apify FREE plan, from the live pricing record; paid Apify plans pay less per event.
| Event | Price (USD) |
|---|---|
Actor start (actor-start) | 0.00005 |
Domain analyzed (domain-analyzed) | 0.003 |
Full actor documentation
Input reference, the complete output field list, pricing tiers, error handling, and the measured limitations are on the actor's Apify Store page:
https://apify.com/mambalabs/ai-tooling-detector
Immutable actor ID: EwkHhmqiuJgRoVEbE
Mamba Labs GTM Suite
This server is part of the Mamba Labs GTM Suite, a fleet of specialized MCP servers for go-to-market signal intelligence, each backed by a dedicated Apify actor. The @mambalabsdev/mcp-gtm-suite umbrella server exposes all of them, including this one, through a single install.
| Actor | Immutable Actor ID |
|---|---|
| GTM Hiring Signal Scraper | D7O1SA2EqwHGsGr1P |
| GTM Tech Stack Signal Enrichment | qyd7nNyqFPelQViBx |
| GTM Signals Aggregator | xKdRfnfFNkdMpFuNs |
| Job Board Keyword Signal Scanner | 4DvqpvhMR74NLcDDY |
| Domain to LinkedIn URL Resolver | 3HtnSaqPHOg1Qg5gx |
| ICP Fit Scorer | W161DT8W4kW55dMFh |
| Domain Deliverability Checker | 0tVgxI7A6o9jMlxmc |
| Company Firmographic Enricher | YlUtLWjfPpqykmB8g |
| Company Social Presence Mapper | 4k6CCemkgBDz18m2h |
| Company Identity Resolver | lr8fTRAmZCBZmuwwh |
| Company Change-Event Feed | oX44rS0fkEJ3rXLWe |
| Funding & Press Signal Scanner | FS13X6dhQVgX3XOM6 |
| AI Tooling Detector | EwkHhmqiuJgRoVEbE |
Built by Mamba Labs | npm | Apify Store
License
MIT
Built by Mamba Labs. https://apify.com/mambalabs
Frequently asked questions
What is com.mambabuilt/mcp-ai-tooling-detector?
Detect whether a company declares, deploys, or charges for AI, with evidence.
How do I install com.mambabuilt/mcp-ai-tooling-detector?
It runs on your machine. In Claude Code: claude mcp add mcp-ai-tooling-detector -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-ai-tooling-detector@1.4.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does com.mambabuilt/mcp-ai-tooling-detector need an API key?
Yes. It expects APIFY_TOKEN, which you set in its configuration.
Is com.mambabuilt/mcp-ai-tooling-detector open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains com.mambabuilt/mcp-ai-tooling-detector?
It is published by mambalabsdev. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.