Take Blip MCP server

by codespar·io.github.codespar/mcp-take-blip·v0.2.2·271 stars

No reviews yet

MCP server for Take Blip — chatbots, messaging, contacts, broadcasts

B82/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B82/100

full report

Adoption

Established

271 stars22 downloads/wk

Reviews

Write one

Nobody has reviewed Take Blip yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Take Blip tools (18, 7 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

close_ticket
Close an open support ticket
create_broadcastwrite action
Create a broadcast distribution list and send messages
create_contactwrite action
Create a contact in Take Blip
create_ticketwrite action
Open a support ticket / human handoff for a contact
delete_contactwrite action
Delete a contact by identity
get_analytics
Get chatbot analytics and metrics
get_bot_resource
Get a bot resource value by name (variable / state)
get_chatbot_flow
Get chatbot flow/builder configuration
get_contact
Get a single contact by identity
get_contacts
List contacts in Take Blip
get_thread
Get the message thread between the bot and a specific identity
get_threads
Get message threads (recent conversations)
list_tickets
List tickets, optionally filtering by status
send_messagewrite action
Send a message to a contact via Take Blip
send_notificationwrite action
Send a notification message to a contact
set_bot_resource
Set a bot resource value (used as bot variables / state via /resources bucket)
track_event
Track a custom analytics event in the bot event tracker
update_contactwrite action
Merge/update fields on an existing contact

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings

Code scan5 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitystatic API keys via environment variables6/15
Maintenancelast push 29 days ago15/15
Maintainer identityregistry namespace matches repository owner7/10

Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Take Blip compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 82/100; higher than 63% of 48,255 servers
Tools: 18; the typical server has 7
Tools that change things: 39%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 271; more than 95% of 28,688 servers
Downloads a week: 22; more than 8% of 12,191 servers with a package

What its tools let an agent do: 9 read · 3 create · 3 change · 1 delete · 2 send or post

Install Take Blip in Claude Code, Cursor or VS Code

Runs npx -y @codespar/mcp-take-blip on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-take-blip -- npx -y @codespar/mcp-take-blip

Add to Cursor

What the publisher says

From the Take Blip repository's README, as published. We do not edit it. Read it on GitHub

MCP Dev LATAM 🌎 Every commerce API your AI agent needs to run a business in Latin America. Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 · Chile 🇨🇱 · Peru 🇵🇪 · plus 4 agentic payment protocols. MCP servers for LATAM commerce · live in the official MCP Registry · MIT License Machine-readable catalog: codespar.dev/api/servers Catalog · Quick Start · Agentic Protocols · All Servers · Contribute

The Problem

AI agents can write code, analyze data, and chat. But they can't operate a business — collect payments, issue invoices, ship products, or notify customers. Especially not in Latin America, where every service has its own API, auth pattern, and quirks (mTLS for BACEN Pix v2, JWT-RSA for STP-SPEI, AFIP web services, contract-gated developer portals, and on).

Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — and none of them compose cleanly with each other or with the regional rails businesses actually run on.

MCP Dev LATAM bridges both gaps. Traditional LATAM services + the new agentic payment protocols, all accessible through a single MCP interface.

The Solution

Each MCP server in this repo wraps a real provider — payments, fiscal, logistics, messaging, banking, ERP, identity, fraud, crypto, and the agentic protocols — so your agent can operate a complete business workflow.

🛒 Customer places order
  → 💳 Agent charges via Pix (Asaas / Mercado Pago / Zoop)
  → 📄 Agent issues NFe (Nuvem Fiscal / Focus NFe / NFe.io)
  → 📦 Agent generates shipping label (Melhor Envio / Skydropx)
  → 📱 Agent sends tracking via WhatsApp (Z-API / WhatsApp Cloud)
  → 📊 Agent records in ERP (Omie / Bling / Tiny)
  → 🏦 Agent reconciles balance (Stark Bank / Itaú / BTG)

Six systems. Zero human intervention. One agent.

Agentic Payment Protocols

Four servers for the emerging agentic payment stack:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Take Blip: common questions

Is Take Blip MCP server safe?: Mostly: it is graded B (82/100). Read the Take Blip safety report
How do I install Take Blip?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Take Blip need an API key?: Yes. The registry entry asks for TAKE_BLIP_API_KEY.
Is Take Blip maintained?: The last commit was 67 days ago (2026-08-29). The latest release is v0.2.2.
How does Take Blip compare with other MCP servers?: safety score 82/100 (higher than 63% of 48,255 servers); tools 18 (the typical server has 7); tools that change things 39% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.