NLP Tools - Sentiment, NER, Toxicity & Language Detection
RemoteAbout NLP Tools - Sentiment, NER, Toxicity & Language Detection
This legacy repository does not provide a supported NLP tools service: its listed historical endpoints may no longer work. The current notice points instead to Brainiall speech services and offline contract checks.
Key features
- 01Notice about retired historical endpoints
- 02Pointers to current Brainiall speech services
- 03Offline contract compatibility checks
Use cases
- 01Locate current Brainiall speech API information
- 02Inspect offline contract checks without API calls
MCP support
The repository points to a current Brainiall text-to-speech MCP endpoint; the old documented MCP URLs have been retired.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://apim-ai-apis.azure-api.net/mcp/nlp/mcpclaude mcp add --transport http fasuizu-br-nlp-tools https://apim-ai-apis.azure-api.net/mcp/nlp/mcp{"mcpServers":{"fasuizu-br-nlp-tools":{"type":"http","url":"https://apim-ai-apis.azure-api.net/mcp/nlp/mcp"}}}Open in Cursor{"servers":{"fasuizu-br-nlp-tools":{"type":"http","url":"https://apim-ai-apis.azure-api.net/mcp/nlp/mcp"}}}Open in VS Code{"mcpServers":{"fasuizu-br-nlp-tools":{"type":"http","url":"https://apim-ai-apis.azure-api.net/mcp/nlp/mcp"}}}{"mcpServers":{"fasuizu-br-nlp-tools":{"serverUrl":"https://apim-ai-apis.azure-api.net/mcp/nlp/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
6| Parameter | Type | Required | Description |
|---|---|---|---|
| text | string | Yes | Text to analyze for toxicity (hate speech, insults, threats) |
Details
From the project READMEBrainiall 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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.