SMS GSM-7 Sanitizer MCP for AI. Stop paying for multi-part text messages.

Q: How do I use sanitizegsm7 in a Python agent?

You simply pass your draft text as an argument to sanitizegsm7. The function returns the cleaned, compliant string that you can then safely send via any messaging API.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Connect to your AI in seconds.

SMS GSM-7 Sanitizer sanitizes draft text by stripping emojis, complex Unicode characters, and non-GSM-7 symbols. It converts content to pure 7-bit ASCII encoding, guaranteeing compliance with the standard 160-character SMS limit.

This prevents messaging services from automatically splitting your campaign into multiple parts, saving you unnecessary telecom charges.

What your AI can do

Sanitize gsm7

Strips emojis and complex Unicode from draft text, converting it to pure 7-bit ASCII. This guarantees GSM-7 encoding so your SMS message remains under the 160-character limit.

Strip Emojis and Special Characters

The tool removes all emojis and zero-width characters from the text, leaving only plain, readable ASCII characters.

Convert Complex Accents

It converts accented letters (like é or ü) into their basic 7-bit English equivalents, ensuring compatibility with older SMS systems.

Guarantee GSM-7 Encoding

The output text is guaranteed to adhere to the strict 7-bit ASCII encoding required for single-segment SMS messages.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

SMS GSM-7 Sanitizer MCP Server: 1 Tool for SMS Compliance

This server lets you sanitize draft text by stripping emojis and complex Unicode, guaranteeing pure 7-bit ASCII encoding for reliable message delivery.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using SMS GSM-7 Sanitizer on Vinkius

Sanitize Gsm7

Strips emojis and complex Unicode from draft text, converting it to pure 7-bit ASCII. This guarantees GSM-7 encoding so your SMS message...

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The SMS GSM-7 Sanitizer integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "sms-gsm-7-sanitizer": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the SMS GSM-7 Sanitizer tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"sms-gsm-7-sanitizer": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with SMS GSM-7 Sanitizer, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,100+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Unidecode & Emoji Regex. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 1 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Sending SMS with AI copy often leads to unexpected bill shock.

You write a great campaign draft—it's engaging, it has emojis, and it sounds human. You pass this text from your agent into the messaging service API. What happens next is usually invisible: the carrier sees Unicode characters, determines they exceed 7-bit ASCII limits, and automatically splits your single message into three or four parts. Suddenly, that $0.50 send costs you $1.50.

With this MCP server, you feed the draft text to `sanitize_gsm7`. The tool strips out all the fancy Unicode and emojis, leaving only pure 7-bit ASCII text. You get back a single, clean string that is guaranteed compliant with GSM-7 rules, keeping your campaign cost predictable.

SMS GSM-7 Sanitizer MCP Server: Clean text for carrier compliance.

Manual testing shows the problem every time. You have to manually check if accents break the message, if adding a single emoji forces a segment split, or if smart quotes cause issues. It's tedious, slow, and failure-prone.

Now, you just pipe all content through `sanitize_gsm7`. The tool handles all those edge cases instantly. You trust the output because it’s been aggressively sanitized to meet strict telecom standards. Period.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

What your AI can actually do with this

You know how it is with marketing copy generated by an AI agent. The thing spits out this fancy-pants text, loaded up with emojis and characters that look cool but absolutely wreck your SMS campaign. Those little flourishes—the zero-width spaces, the hearts, the complex Unicode symbols—they instantly break the standard 160-character GSM-7 limit.

When that happens, the messaging service doesn't just chop it off; it forces you to pay for multiple segments, which costs a fortune and makes your messages look sloppy.

That’s where sanitize_gsm7 comes in. It’s not some vague suggestion box tool; it’s a dedicated sanitizer that runs aggressive cleaning protocols straight through your draft text. You feed it whatever mess you've got—whether it's riddled with accent marks, fancy quotes, or obscure Unicode symbols—and what you get back is pure, clean 7-bit ASCII copy.

This process guarantees the message adheres to strict GSM-7 encoding rules, keeping everything simple and fitting into a single segment.

The tool works by systematically identifying non-compliant characters. First up, it strips all emojis and every zero-width character from your text payload. There are no exceptions; anything that isn't basic English ASCII gets wiped out. This step alone eliminates the visual clutter and the technical risk posed by modern Unicode symbols.

You'll only be left with plain, readable letters.

Next, it handles those complex accents. If your source text uses characters like é, ü, or ñ, the system doesn't just fail; it transcribes them. It converts every accented letter into its basic, safe 7-bit English equivalent (like converting ‘é’ to ‘e’). This transliteration process ensures compatibility with older, stricter SMS systems that don't recognize special diacritics.

This whole mechanism guarantees the output text maintains strict adherence to 7-bit ASCII encoding. Because of this rigorous filtering and conversion, your resulting message is guaranteed to fit within the single-segment 160-character limit required by GSM-7 standards. You don't get those multi-part segments that cost you extra money just because some agent got too creative with a rocket emoji.

The tool processes content from various sources; it doesn’t care if your copy came from an LLM draft or a legacy system. It simply cleans the payload until it meets the exacting standards of single-segment SMS messaging. You write the message, you run it through sanitize_gsm7, and you get back text that's ready to blast out without worrying about unexpected carrier fees or accidental truncation.

It’s simple, direct cleanup for maximum delivery reliability.

Built · Hosted · Managed by Vinkius SMS GSM-7 Sanitizer - Clean Text for SMS Compliance

Server ID 019e38ef-a1d5-7261-bb67-1dbd92f0ee88

Vinkius Inspector

Compliance Grade A+

Score 100/100

Report View Report ↗

Here's how it actually works

The bottom line is you get a single, guaranteed GSM-7 compatible text payload that won't break carrier billing rules.

Pass your draft message (the raw, unsanitized text) into the sanitize_gsm7 tool.

The engine strips all emojis and transliterates complex Unicode characters to pure 7-bit ASCII.

You receive the clean, compliant string, ready for immediate sending via SMS APIs.

What Changes When You Connect

Stops unexpected billing charges. Since the sanitize_gsm7 tool enforces pure 7-bit ASCII, you guarantee your message stays within the single 160-character segment limit. No more surprise fees from carriers.

Works with any AI client. Whether your agent is running in Claude Desktop or VS Code Copilot, connecting this MCP ensures that the text data passed for SMS always meets GSM-7 compliance standards.

Saves time on debugging failures. Don't waste hours figuring out why a message was cut off mid-sentence. Run it through sanitize_gsm7 first to validate payload integrity before sending.

Handles complex inputs reliably. The tool aggressively strips emojis and zero-width characters, meaning you don't have to worry about the LLM adding flair that breaks your campaign copy.

Universal compatibility. It doesn't matter if your source text has smart quotes (”) or fancy accents; sanitize_gsm7 converts it all into basic ASCII, making the message universally compatible.

See it in action

01 01

The AI Draft Went Too Fancy

An agent drafts a campaign: 'Check out our new ☕️ feature! Don't forget to call us today!' The developer tries to send it, but the carrier splits it into three parts because of the emoji and Unicode. Instead, they run the draft through sanitize_gsm7, which cleans it up to: 'Check out our new feature! Don't forget to call us today!', solving the billing problem instantly.

02 02

Handling International Copy

A marketing team has copy with many accented characters (e.g., 'résumé', 'São Paulo'). If they send it raw, some carriers might reject or mangle the text. They use sanitize_gsm7 to strip these accents down to plain ASCII letters, ensuring maximum delivery success across different regional SMS gateways.

03 03

Cleaning Up Raw User Input

A system accepts user feedback via chat and needs to send a summarized alert SMS. The raw input includes emojis and complex symbols. Running the payload through sanitize_gsm7 cleans up the data first, ensuring that the resulting automated summary is clean and compliant for immediate broadcast.

04 04

Validating AI Output Before Publish

Before publishing a high-volume alert, developers pipe every draft message through sanitize_gsm7. This acts as a mandatory final gate check. If the tool returns a clean string, they know it's safe for mass distribution and won't trigger billing overruns.

The honest tradeoffs

Assuming LLMs are perfect.

Anti-pattern

Just passing the AI-generated text directly to the SMS API because, 'The LLM is smart enough to handle it.'

The Fix

Never trust raw AI output for carrier transmission. Always pass the draft text through the sanitize_gsm7 tool first. This guarantees compliance before you pay the bill.

Using simple character filters.

Anti-pattern

Only running a basic filter that strips emojis but leaves complex Unicode accents and smart quotes intact, leading to partial failures.

The Fix

You need full transliteration. Use sanitize_gsm7. It handles everything: emojis, zero-width characters, AND accented letters, guaranteeing pure 7-bit ASCII.

Testing with clean text only.

Anti-pattern

Only testing the system with simple English phrases and never running a test case that includes international accents or multiple emojis.

The Fix

Test edge cases. Run drafts containing accented characters, symbols (like &), and full emoji sets through sanitize_gsm7. This proves its robustness.

When It Fits, When It Doesn't

Use this server if your workflow sends automated SMS messages using AI-drafted or user-provided content AND you are worried about multi-part billing charges. If your source text contains emojis, Unicode symbols, smart quotes, or accented letters (like é, ü), running it through sanitize_gsm7 is mandatory. Don't use this if you simply need to strip out malicious characters—the tool does that too, but its primary value is guaranteeing carrier compliance. Don't use it if your messaging platform already has built-in, robust GSM-7 sanitization logic; in that case, the overhead isn't necessary. But because most AI tools spit out rich text, this sanitizer remains a critical, non-negotiable step in any production message pipeline.

Questions you might have

Does SMS GSM-7 Sanitizer strip out useful emojis? +

Yes, it strips them. That's how it works. Emojis are non-ASCII characters and break the standard encoding limit; stripping them is necessary to guarantee single-segment message delivery.

How do I use sanitize_gsm7 in a Python agent? +

You simply pass your draft text as an argument to sanitize_gsm7. The function returns the cleaned, compliant string that you can then safely send via any messaging API.

What if my message is already clean? Does sanitize_gsm7 break it? +

No. If your text is already pure 7-bit ASCII and contains no complex Unicode, the tool passes the content through unchanged. It only modifies what needs fixing.

Is this better than using a basic regex clean-up? +

Yes. A simple regex won't handle transliteration (like converting é to e) or complex Unicode symbols. This tool handles the full spectrum of encoding compliance.

When I run sanitize_gsm7 with accented characters like é or ñ, what happens to them? +

It converts them using Unicode Transliteration. The tool doesn't just strip accents; it safely translates complex characters into their closest 7-bit ASCII equivalents. This ensures your message retains its intended meaning while guaranteeing strict GSM-7 compliance.

If I need to send thousands of messages, does sanitize_gsm7 handle rate limiting or batch processing? +

The server is built for high throughput and continuous message flow. While you should always check the Vinkius Marketplace documentation for current usage quotas, it's designed to process large volumes efficiently, preventing character segment failures even in big batches.

When I pass sensitive text to sanitize_gsm7, how is my input data handled? +

Data processing occurs via the MCP standard. Your AI client sends the text directly for sanitization. The provider and Vinkius adhere to strict protocols; the service only reads and modifies the string as needed for GSM-7 compliance.

What happens if my SMS draft contains highly corrupted or unknown Unicode characters? +

The tool is designed to be robust. It uses aggressive regular expressions that detect unsupported sequences and removes them entirely instead of failing the process. This guarantees you always receive a clean, sendable string.

Why does an emoji cost more? +

Emojis force the telecom provider to use UCS-2 encoding, which cuts the character limit from 160 down to 70 per message segment.

What happens to accented letters? +

Using the unidecode algorithm, letters like 'ç' become 'c' and 'ã' become 'a', ensuring strict ASCII compatibility.

Is this needed for WhatsApp? +

No, WhatsApp handles Unicode perfectly. This is specifically for legacy SMS gateways like Twilio and SNS.

Connect to your AI in seconds.

Sanitize gsm7

SMS GSM-7 Sanitizer MCP Server: 1 Tool for SMS Compliance

Make your AI actually useful.

Sanitize Gsm7

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Works with Claude, ChatGPT, Cursor, and more

Sending SMS with AI copy often leads to unexpected bill shock.

SMS GSM-7 Sanitizer MCP Server: Clean text for carrier compliance.

What your AI can actually do with this

Here's how it actually works

Who is this actually for?

What Changes When You Connect

See it in action

The AI Draft Went Too Fancy

Handling International Copy

Cleaning Up Raw User Input

Validating AI Output Before Publish

The honest tradeoffs

Assuming LLMs are perfect.

Using simple character filters.

Testing with clean text only.

When It Fits, When It Doesn't

Questions you might have