NLP Tools - Sentiment, NER, Toxicity & Language Detection
Toxicity, sentiment, NER, PII detection, and language identification tools
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).
claude mcp add --transport http nlp-tools-sentiment-ner-toxicity-languag 'https://apim-ai-apis.azure-api.net/mcp/nlp/mcp'{
"mcpServers": {
"nlp-tools-sentiment-ner-toxicity-languag": {
"type": "http",
"url": "https://apim-ai-apis.azure-api.net/mcp/nlp/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Brainiall Speech AI examples — migration notice
This repository is legacy. The former
apim-ai-apis.azure-api.netgateway and the old Speech AI MCP URLs documented in earlier revisions have been retired. Do not use those URLs. The other files in this repository are retained only as historical source and may no longer run.
Current supported surfaces
| Need | Current surface |
|---|---|
| Text-to-speech MCP server | https://api.brainiall.com/mcp/tts/mcp |
| Text-to-speech REST endpoint | POST https://api.brainiall.com/v1/tts/synthesize |
| TTS health check | https://api.brainiall.com/mcp/tts/health |
| TTS setup, OpenAPI and maintained examples | fasuizu-br/brainiall-tts-mcp |
| Brazilian Portuguese transcription | Transcreve BR |
| Speech-to-text API overview | Brainiall Speech-to-Text |
| Account and API key | Brainiall app |
| Offline contract compatibility checks | compatibility-pack/ |
Authentication for the current API uses an Authorization: Bearer YOUR_BRAINIALL_API_KEY header. Never commit a real key.
For TTS examples for Claude, Cursor, VS Code, n8n, Postman and raw REST clients, use the maintained TTS repository linked above. It is the canonical source for current voices, prices and request schemas.
The small compatibility pack is different from the historical examples. It is an offline-only contract test for buffered TTS, generic diarized-STT review artifacts, a synthetic diarization canary and local-by-default usage planning. It performs no API call during tests, contains no key, copies no third-party source, and does not claim streaming, cancellation, OpenAI drop-in compatibility, completed third-party integration or billing. Read its kill gates before reusing it.
Why this notice exists
External directories and search engines may still link to this repository. This notice prevents an old listing from sending developers to endpoints that no longer work and points them to the maintained production surfaces.
License
MIT — Brainiall
C112 — hosted STT contract fixture
The Whisper-WebUI OpenAI-compatible fixture is a provider-neutral, synthetic request/response example for maintainers evaluating an external speech-to-text path. It does not claim that Whisper-WebUI has adopted the contract, and it never includes a key or private audio.
Frequently asked questions
What is NLP Tools - Sentiment, NER, Toxicity & Language Detection?
Toxicity, sentiment, NER, PII detection, and language identification tools
How do I install NLP Tools - Sentiment, NER, Toxicity & Language Detection?
It runs as a remote server. In Claude Code: claude mcp add --transport http nlp-tools-sentiment-ner-toxicity-languag 'https://apim-ai-apis.azure-api.net/mcp/nlp/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does NLP Tools - Sentiment, NER, Toxicity & Language Detection need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is NLP Tools - Sentiment, NER, Toxicity & Language Detection open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains NLP Tools - Sentiment, NER, Toxicity & Language Detection?
It is published by fasuizu-br. 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.