NLP Tools - Sentiment, NER, Toxicity & Language Detection

io.github.fasuizu-brv1.1.0更新於 Oct 7, 2026

Toxicity, sentiment, NER, PII detection, and language identification tools

已驗證Streamable HTTP可網頁執行AI & MLSecurity & Monitoring

概覽

AI 產生的概覽

透過遠端端點提供毒性、情感、命名實體辨識、PII 偵測與語言辨識等文字分析工具。

功能
登錄描述列出毒性偵測、情感分析、命名實體辨識、PII 偵測與語言辨識等工具（D1）。它以遠端 streamable HTTP 端點形式提供，而非本機套件，清單中未列出個別工具名稱或結構。隨附的 README 是舊版儲存庫的遷移通知，並未說明這些 NLP 工具；內容描述的是已停用的閘道網址，並指向獨立的文字轉語音與語音轉文字服務。
適用情境
當助理需要在不於本機執行模型的情況下快速完成文字分類，例如情感判斷、實體擷取、毒性篩檢、PII 辨識或語言辨識時，可能適用。使用前請先確認端點是否仍可用，因為 README 稱該閘道與舊 MCP 網址已停用。
執行需求
宣告為位於 的遠端 streamable HTTP 端點，未宣告套件、環境變數、標頭或驗證。README 稱該閘道與舊 MCP 網址已停用（R2、R3），現行 API 改用 Authorization: Bearer YOUR_BRAINIALL_API_KEY 標頭（R15）。需要能連線至該端點的網路。
安裝前請注意
README 明確指出此儲存庫為舊版，原閘道與舊 MCP 網址已停用，並提醒不要使用這些網址（R2、R3、R4），因此清單中的端點可能已無法使用。README 所述現行 API 使用 Authorization: Bearer YOUR_BRAINIALL_API_KEY 標頭（R15），並警告切勿提交真實金鑰（R16）；而本條目未宣告任何驗證。PII 偵測意味著文字會傳送至第三方服務。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 NLP Tools - Sentiment, NER, Toxicity & Language Detection，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "nlp-tools": {
      "type": "http",
      "url": "https://apim-ai-apis.azure-api.net/mcp/nlp/mcp"
    }
  }
}

README

Brainiall Speech AI examples — migration notice

[Current TTS health] [Current TTS repository]

This repository is legacy. The former apim-ai-apis.azure-api.net gateway 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

NeedCurrent surface
Text-to-speech MCP serverhttps://api.brainiall.com/mcp/tts/mcp
Text-to-speech REST endpointPOST https://api.brainiall.com/v1/tts/synthesize
TTS health checkhttps://api.brainiall.com/mcp/tts/health
TTS setup, OpenAPI and maintained examplesfasuizu-br/brainiall-tts-mcp
Brazilian Portuguese transcriptionTranscreve BR
Speech-to-text API overviewBrainiall Speech-to-Text
Account and API keyBrainiall app
Offline contract compatibility checkscompatibility-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.

來源：README.md，提交 eab44aa

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v1.1.0最新Sep 16, 2026