Neuroslop MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEUROSLOP_API_KEY | No | API key required only for the optional paid rewriting tool (`neuroslop_humanize`). The keyless `neuroslop_check` and local `neuroslop_clean` tools work without it. Add the key to the server environment only when rewriting is needed. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| neuroslop_checkA | Free deterministic style analysis: no LLM call, API key or quota debit. Sends text to neuroslop.net. Returns style markers, applicability and an explicit abstention when evidence is insufficient. Full rule coverage is currently RU/EN; other languages can have limited coverage. A 0–100 style score is NOT an AI-authorship probability or proof. |
| neuroslop_humanizeA | Request editorial rewriting with an API key and user approval to spend quota. Sends text to neuroslop.net and its configured generation providers. Reports billing fields; local edits may have spent=0 without paid editorial approval. Scores may be independently unavailable. Reuse requestId only for the same operation; replay depends on API receipt retention. A missing receipt or unknown delivery is not permission to start another paid run. |
| neuroslop_cleanA | Locally normalize invisible characters, unusual spaces and Latin lookalikes from Cyrillic/Greek. No network or API key. Returns cleaned text and change counts. These characters can be legitimate: review changes before replacing the original. This is not authorship detection. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct operational mode: free local analysis (check), paid server-side rewriting (humanize), and local character normalization (clean). Check and humanize both concern style and could be momentarily confused, but the free/paid and analysis/rewrite distinction is spelled out clearly in the descriptions.
All three tools use the same namespace prefix plus a short snake_case verb (neuroslop_check, neuroslop_humanize, neuroslop_clean). No mixed conventions or ambiguous naming.
Three tools map tightly to the server's narrow purpose of style analysis and text cleanup/rewriting, with no filler. It is on the lean side, but each tool covers a genuinely separate step of the workflow.
The surface covers the core lifecycle: normalize input (clean), analyze style (check), and rewrite (humanize). Minor gaps exist around account/quota inspection and retrieving prior results, but agents can work around these.