Home / MCP registry index / com.brainiall/nlp
Brainiall NLP
com.brainiall/nlp in the official MCP registry.
Endpoint https://api.brainiall.com/mcp/nlp/mcp.
The registry describes it as: Sentiment, toxicity, entity extraction, PII, translation, summary, QA, fraud scoring, safety audit.
We read its 22 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
analyze_toxicity analyze_sentiment extract_entities detect_pii detect_language check_nlp_service translate_text summarize_text answer_question knowledge_ingest knowledge_query knowledge_list_documents fraud_score fraud_feedback extract_key_phrases aspect_sentiment classify_text_custom link_entities_to_wikidata detect_conversational_pii detect_prompt_injection check_groundedness detect_protected_material
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-brainiall-nlp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.