Skip to main content
Glama
socialintel

Social Intel MCP

by socialintel

Social Intel MCP

Descubrimiento de influencers de Instagram para agentes de IA. Pago por llamada en USDC a través de x402 — sin claves API, sin suscripciones, sin registro.

Licencia MIT Python 3.10+ Compatible con MCP Pagos x402 socialintel.dev Servidor MCP socialintel-mcp

socialintel.dev es una capa de datos para agentes de IA que ejecutan flujos de trabajo de alcance a influencers, investigación de marca e inteligencia de creadores. Este repositorio incluye un servidor MCP que expone los mismos datos a través del Protocolo de Contexto de Modelo (MCP), para que cualquier cliente compatible con MCP (Claude, Cursor, VS Code, Cline, …) pueda llamarlo de forma nativa.

📋 Tabla de contenidos

Related MCP server: pulsenetwork-mcp

🚀 Inicio rápido — endpoint alojado

Recomendado. Apunta cualquier cliente MCP que utilice HTTP/SSE o transporte transmitible directamente a nuestro servidor alojado:

https://socialintel.dev/mcp

Sin instalación, sin pip, sin Docker. El cliente x402 de tu agente gestiona el pago en cada tools/call.

Si tu cliente necesita un envoltorio stdio (Claude Desktop en versiones anteriores, algunos clientes CLI), consulta la sección Clientes MCP para configuraciones de uvx / pip install que hacen proxy de stdio → HTTPS.

🔌 Clientes MCP

Claude Desktop

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "socialintel": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/socialintel/socialintel-mcp",
        "socialintel-mcp"
      ],
      "env": {
        "SOCIAL_INTEL_API_URL": "https://socialintel.dev"
      }
    }
  }
}

Reinicia Claude Desktop. search_leads aparecerá en la lista de herramientas.

Cursor

Preferencias → MCP → añadir servidor:

{
  "socialintel": {
    "command": "uvx",
    "args": ["--from", "git+https://github.com/socialintel/socialintel-mcp", "socialintel-mcp"]
  }
}

VS Code (con GitHub Copilot o Continue)

.vscode/mcp.json en tu espacio de trabajo:

{
  "servers": {
    "socialintel": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/socialintel/socialintel-mcp", "socialintel-mcp"]
    }
  }
}

Cline (extensión de VS Code)

Cline detecta automáticamente los servidores MCP desde cline_mcp_settings.json. Añade el mismo bloque de servidor que en Claude Desktop arriba.

Cherry Studio / Zed / cualquier cliente compatible con MCP

Usa el comando stdio:

uvx --from git+https://github.com/socialintel/socialintel-mcp socialintel-mcp

O apunta el cliente al endpoint HTTP alojado si admite MCP remoto: https://socialintel.dev/mcp

Instalación directa con pip

pip install git+https://github.com/socialintel/socialintel-mcp
SOCIAL_INTEL_API_URL=https://socialintel.dev socialintel-mcp

🛠️ Herramientas

search_leads

Busca influencers de Instagram por demografía, ubicación, palabra clave o categoría de negocio.

Parámetro

Tipo

Qué hace

query

string

Palabra clave en nombre/biografía (ej. yoga, travel blogger)

country

string

Código ISO (US, DE, UK, IN, BR) o nombre completo

city

string

Filtro de ciudad (ej. Los Angeles). Combinar con country

category

string

Fitness · Beauty · Travel · Food & Beverage · Gaming · Fashion · Lifestyle · Sports · Education · Finance · Tech · …

gender

string

male / female (también man / woman)

min_followers

int

Mínimo. 10000 = micro, 100000 = macro

max_followers

int

Máximo. 100000 excluye mega-cuentas

limit

int

1–100 (por defecto 20). El precio escala con el límite

demo

bool

true = 3 resultados de vista previa gratuitos, sin pago

Cada resultado:

{
  "username": "yoga_with_adriene",
  "full_name": "Adriene Mishler",
  "followers": 10500000,
  "category": "Fitness",
  "bio": "Yoga teacher & filmmaker from Austin TX",
  "public_email": "contact@adriene.com",
  "is_verified": true,
  "is_business": true,
  "gender": "woman"
}

public_email se completa cuando está disponible; es más frecuente en cuentas verificadas como empresa y menos en cuentas de creadores personales (realidad de la plataforma Instagram, no un filtro que apliquemos nosotros).

💰 Flujo de pago (x402)

Los pagos de los agentes siguen el protocolo x402: una respuesta de Pago Requerido 402 lleva requisitos de pago firmados; el cliente firma una transferencia USDC y reintenta; el servidor verifica + liquida a través de un facilitador y devuelve los resultados.

  1. El agente llama a search_leads(category="Fitness", country="US").

  2. El servidor responde HTTP 402 con metadatos extensions.bazaar y acepta bloques para Base (USDC) y Solana (USDC).

  3. Si el cliente ejecuta una biblioteca de cliente x402 (x402-httpx, agentcash, el paquete TypeScript x402, etc.), firma una transferencia en cualquiera de las cadenas y reintenta.

  4. Nuestro servidor verifica + liquida a través del facilitador CDP (principal — también nos cataloga en agentic.market) o el facilitador PayAI (alternativo). Los resultados se devuelven en la llamada reintentada.

Precios — transparentes por llamada, sin mínimos:

Límite

USDC

1–20

$0.50

50

$0.80

100

$1.30

Fórmula: $0.50 + max(0, límite − 20) × $0.01.

La demo gratuita con demo=true omite el pago por completo; consulta Modo demo gratuito.

🎯 Casos de uso

Descubrimiento de micro-influencers para alcance de marca

search_leads(
    category="Beauty",
    country="US",
    min_followers=15000,
    max_followers=200000,
    limit=50,
)

Devuelve 50 micro-influencers de belleza en EE. UU., con correos electrónicos comerciales públicos cuando estén disponibles.

Búsqueda de creadores locales (nivel ciudad)

search_leads(
    city="Los Angeles",
    category="Food & Beverage",
    min_followers=10000,
    limit=20,
)

Creadores de comida en LA con más de 10K seguidores.

Fusión de palabra clave + demografía

search_leads(
    query="personal trainer",
    gender="female",
    country="United Kingdom",
    min_followers=50000,
    max_followers=500000,
)

Entrenadores personales mujeres en el Reino Unido, nivel de seguidores medio-alto.

Exploración gratuita antes de pagar

search_leads(category="Travel", country="Germany", demo=True)

Devuelve 3 resultados de vista previa sin pago — perfecto para validar filtros antes de gastar.

🎛️ Configuración

Variable de entorno

Por defecto

Propósito

SOCIAL_INTEL_API_URL

http://localhost:8000

URL base para la API upstream. Configurar como https://socialintel.dev para producción.

POSTHOG_API_KEY

(vacío)

Opcional — si se establece, el servidor MCP emite eventos de uso anónimos a PostHog. Vacío por defecto para que no haya telemetría silenciosa.

POSTHOG_HOST

https://us.i.posthog.com

Solo se usa cuando POSTHOG_API_KEY está configurado.

🧪 Modo demo gratuito

Pasa demo=true en cualquier llamada a search_leads. Obtienes hasta 3 resultados de vista previa, sin necesidad de pago. La respuesta incluye un upgrade_message que apunta a la URL de pago para que tu agente pueda cambiar al modo de pago después de validar los filtros.

La demo tiene un límite de 5 solicitudes por IP por hora. Lee desde nuestra caché en lugar de la fuente de datos en vivo, por lo que el contenido refleja consultas recientes en lugar del estado de la plataforma en tiempo real.

🌐 Múltiples transportes

  • stdio (por defecto) — uvx --from git+... socialintel-mcp

  • HTTPS / transmitible — conecta directamente a https://socialintel.dev/mcp

  • SSE — el endpoint alojado también sirve Server-Sent Events para clientes que lo prefieran

El endpoint alojado es la ruta más sencilla — instalación cero, definiciones de herramientas idénticas.

🔒 Privacidad y telemetría

Este servidor emite un evento anónimo por llamada de herramienta cuando POSTHOG_API_KEY está configurado:

  • mcp_search_leads — incluye solo la forma del filtro (consulta, país, categoría, género, rango de seguidores, límite, bandera de demo) y el recuento de filas resultante. Sin nombres de usuario de perfil, sin correos electrónicos, sin direcciones de pagador.

Los eventos están desactivados por defecto (sin clave significa sin captura). Si habilitas la telemetría, puedes apuntarla a tu propio proyecto de PostHog — establece POSTHOG_API_KEY con tu propia clave y los eventos irán a tu instancia, no a la nuestra.

La telemetría a nivel de pago (liquidación x402, hashes de transacciones, ingresos) es capturada en el lado del servidor por socialintel.dev, no por este envoltorio MCP.

🗺️ Relacionado

📄 Licencia

MIT — ver LICENSE.

🐛 Problemas

Informes de errores, solicitudes de funciones, preguntas sobre integración de agentes: github.com/socialintel/socialintel-mcp/issues

Available Tools

1 tool
search_leadsA

Search Instagram influencers by demographics, location, or keyword.

Returns username, bio, follower count, category, and business email (~50% of accounts).

Price: $0.50 USDC on Base or Solana via x402 (auto-handled by AgentCash or x402 client). Set demo=True to try for free — returns up to 3 results, no payment required.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryNoKeyword or phrase to search by name/bio (e.g. 'yoga', 'travel blogger', 'NYC chef').
countryNoCountry filter. ISO code (US, DE, FR, UK, CA, AU, IN, BR, JP) or full name. Default: all countries.
cityNoCity filter (e.g. 'Los Angeles', 'London', 'New York'). Use with country for precise local targeting.
categoryNoInstagram business category. Examples: Fitness, Beauty, Travel, Food & Beverage, Gaming, Fashion, Lifestyle, Sports.
genderNoGender filter: 'male' or 'female' (also accepts 'man'/'woman').
min_followersNoMinimum follower count. Use 10000 for micro-influencers, 100000 for macro-influencers.
max_followersNoMaximum follower count. Use 100000 to exclude celebrities and large brands.
limitNoResults to return (1-100, default 20). Pricing: 1-20=$0.50, 50=$0.80, 100=$1.30.
demoNoTrue = free preview (3 results, no payment). False = full paid search via x402.

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description covers pricing ($0.50 USDC on Base or Solana via x402), demo mode limitations (3 results, free), and notes that ~50% of accounts have a business email. This goes beyond what annotations would typically provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with purpose and return fields. Pricing details are valuable but could be slightly more concise. Overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 9 parameters with full schema documentation and no output schema, the description covers pricing, demo mode, and email availability. This is sufficient for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the description adds limited meaning beyond schema. It only mentions query, country, city, etc., but the schema already documents parameters well. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool searches Instagram influencers by demographics, location, or keyword, and specifies what it returns (username, bio, follower count, category, business email). This clearly defines the action and output, distinguishing it from potential siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use demo mode vs paid mode, but does not provide direct alternatives or when-not-to-use scenarios. Since there are no sibling tools, this is acceptable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedsearch_leads

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no risk of confusion between tools.

Naming Consistency4/5

With only one tool, naming is consistent by default. The verb_noun pattern is followed.

Tool Count2/5

A single tool is insufficient for a server titled 'Social Intel MCP' which implies broader capabilities like lead management or analytics, resulting in a thin offering.

Completeness2/5

The server only provides search for leads, missing essential operations like saving leads, viewing saved lists, or updating contact information, leaving significant gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

  • Instagram data for AI agents: profiles, posts, reels, followers. Influencer + brand research.

  • Your agent needs public Instagram data — a creator's posts and reels, what a hashtag is producing, what a video actually says. The official Graph API only sees accounts you already own, and needs app review to see those. **What you can ask for** • "Pull this creator's last 50 posts and reels with engagement counts." • "What is trending under #skincare this week, and which profiles keep appearing?" • "Transcribe this reel and tell me what the hook in the first three seconds is." • "Read the comments on this post and group the objections." • "Which reels use this song right now?" **How to use it** Point any MCP client at https://mcp.aisa.one/instagram/mcp and sign in with OAuth — there is no key to create or paste. 17 read tools: profiles (basic and full), a user's posts, reels and highlights, post and profile digests, post comments, reels search, trending reels, reels by song, hashtag and profile search, and media transcripts. **Why this rather than the source** Public profiles without owning the account, and no app review to sit through. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Size a creator's audience here, then ask the same agent what their brand's site traffic looks like or who to contact there — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/social/mcp for X plus Instagram, Reddit, Pinterest and YouTube; https://mcp.aisa.one/gtm/mcp for those plus Similarweb and Apollo.

  • 5 pay-per-call SEO tools over MCP. Free discovery, tool calls settle in USDC on Base via x402.

  • Pay-per-use tool marketplace for AI agents. Search, price-check, and call APIs via MCP.

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    22 MCP tools for AI agents: crypto prices and trading signals (53 coins), stock prices and company financials, forex rates and conversion, and web scraping with AI summaries. All powered by x402 USDC micropayments on Base. $0.01-$0.25 per request.
    22
    19 npm
    MIT
  • A
    license
    C
    quality
    D
    maintenance
    One MCP install that lets your AI agents discover and pay (x402 micropayments, USDC on Base + Solana) for 66 specialized real-time intelligence APIs - finance, crypto, insurance, immigration, legal, markets and more. 68 tools, pey-per-query, no subscription.
    69
    22 npm
    3
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    55+ pay-per-call tools for AI agents over MCP: live telemetry, blockchain/on-chain checks, environmental, transit, finance, and network utilities. No API key or signup — agents pay per request with x402 USDC micropayments (Base and Solana).
    MIT