AI Text Check in Cursor
Flag AI-writing tells in text. The MCP server is https://aitext.openkrill.app/mcp. No key. The steps below are only for Cursor. A call to check_ai_writing was checked against that server on 2026-10-01.
What this server answers
Paste a draft and see the habits that make writing read like it came from an AI model, each marked at its exact place with a plain-language fix.
Ask "which parts of this email sound like AI?", "check my blog post for filler" or "does this cover letter lean on stock phrases?".
AI Text Check looks for overused words and stock openers, hedging openers, sycophantic praise and chatbot sign-offs, generic closers, inflated claims, unnamed experts, "not just X, it's Y" turns, lists of three, heavy em-dash use, decorative bold bullets, and runs of sentences with the same length or the same opening.
Every finding gives the rule, a severity, the start and end offsets, the matched words, why it reads that way and a concrete fix. A score from 0 to 100 sums them up, and the answer states how the score is worked out.
The rules are fixed patterns, not an AI model, so the same text always gives the same answer. They are written for this service; the categories follow the open-source blader/humanizer catalogue (MIT licence) and Wikipedia's "Signs of AI writing".
A finding is a place to look at, not proof of who wrote the text: careful writers use all of these on purpose, and the tool is not an AI detector. It does not rewrite the text.
The text is checked and forgotten: it is never stored, and the only lasting record is a daily count of calls. It is limited to 12,000 characters (about 2,000 words); a score needs at least 40 words.
What it can do
- Flags overused words, stock openers and filler phrases
- Flags hedging openers, generic closers and chatbot sign-offs
- Flags sycophantic praise and inflated claims
- Flags lists of three, heavy em-dash use and decorative bold bullets
- Flags runs of sentences with the same length or opening
- Gives start and end offsets, a severity and a fix for each finding
- Gives a 0 to 100 score and states how it is worked out
- Uses fixed rules, with no AI model, and never stores the text
Tools
check_ai_writing, Check text for AI-writing tells. Flags writing habits. It cannot say who wrote the text. It marks each habit with a fix and a 0 to 100 score. Use it when the user asks which parts read like AI writing, for example "find the filler in my draft", "what makes this email read as machine-written". Pass the text exactly as written, at most 12,000 characters. Returns up to 60 findings in text order, each with a rule id, a severity (high, medium or low), start and end offsets in the text, the matched words, why it reads that way and a plain-language fix, plus a 0 to 100 score with how it was worked out, the source and the date of the rules. The rules are fixed patterns, not an AI model. A finding or a low score is not proof of who wrote the text, so it cannot say whether an AI wrote it, and the tool does not rewrite it. The text is not stored.
Add AI Text Check in Cursor
Cursor reads MCP servers from mcp.json. A project file at .cursor/mcp.json applies to that project. A user file at ~/.cursor/mcp.json applies everywhere. These steps were checked against the Cursor MCP docs on 2026-10-01. Streamable HTTP is the transport: a url, not a shell command.
Create or edit the file so it contains this server. Merge it with servers you already have. Do not replace the whole file if other servers are listed.
{
"mcpServers": {
"ai-text": {
"url": "https://aitext.openkrill.app/mcp"
}
}
}No headers and no auth block. Those are for servers that require a token or a pre-registered OAuth client. AI Text Check answers without either. Saving the file is the install. Open Cursor Settings, then MCP, and confirm AI Text Check is enabled. If it stays disconnected, reload the window. You should see check_ai_writing.
In Agent chat, ask: Which parts of this email sound like AI wrote them? Cursor calls the tool over streamable HTTP and shows the arguments before it runs them, depending on your run mode. Approve the call the first time and read the result. The server is public and read-only. It does not see your repository unless the model puts repository text into the arguments, so do not paste secrets into the question.
A one-click Marketplace install does not exist for this server. The JSON above is the whole setup. Team admins can distribute the same url through a team marketplace, but that is an admin step, not something this page can do for you. OAuth redirect URLs in the Cursor docs matter only for servers that require sign-in. Skip them here.
A call checked on 2026-10-01
A 59-word draft with stock openers is enough for a score. The tool uses fixed rules, stores nothing, and a score is not proof of who wrote the text. The request below was posted to https://aitext.openkrill.app/mcp as tools/call. HTTP 200. Source: the AI Text Check server, read 2026-10-01.
{
"method": "tools/call",
"params": {
"name": "check_ai_writing",
"arguments": {
"text": "In today's rapidly evolving landscape, it is important to note that this update is not just a change, it's a revolution. Furthermore, the team leveraged cutting-edge synergy to empower stakeholders and unlock seamless potential. Moreover, this robust solution stands as a testament to our commitment to innovation. In conclusion, the future looks bright as we continue this journey together."
}
}
}- as of. 2026-10-16
- score. 100
- level. high
- findings. 11
- source. Deterministic pattern rules written for this service, with no AI model. Rule categories follow blader/humanizer (MIT licence) and Wikipedia's Signs of AI writing.
- words. 59
Repeat the call yourself if you need a newer reading. Cached answers expire. A rate limit is not a result: wait and try again. Nothing in the call is a ranking, a filing, or advice.