
Rephrasy
io.github.rephrasyaiPublished by GitHub account rephrasyaiv0.1.0Updated Oct 24, 2026
Humanize AI text and check AI-detection scores from Claude, Cursor, or any MCP client.
Overview
Lets an assistant rewrite AI-generated text into a more human style and score how likely text is to be flagged as AI-written.
- What you can do
- The server exposes two tools. The humanize tool rewrites AI-generated text in a natural, human style while preserving meaning, and returns the rewritten text plus the number of words charged. The detect tool scores how likely a text is to be flagged as AI-written, returning an overall score and optionally a per-sentence breakdown. Both tools run through the Rephrasy API from an MCP client such as Claude or Cursor.
- When to use it
- Useful when drafting or editing text that must read as human-written, or when checking a draft's AI-detection score before publishing. It fits editor and agent workflows where rewriting and verification happen in the same session.
- Requirements
- A local Node.js runtime to run the npm package @rephrasy/mcp over stdio, plus a Rephrasy API key supplied in the REPHRASY_API_KEY environment variable. The key comes from a Rephrasy account (Account, then API). Network access to the Rephrasy service is required.
Installation
In SourceWeft
- Open Rephrasy in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Rephrasy MCP Server
Use Rephrasy from Claude, Cursor, or any MCP client: humanize AI-generated text and images, and check AI-detection scores, without leaving your editor or agent workflow.
Four tools, one API key:
Setup
1. Get an API key — sign in at rephrasy.ai → Account → API. Both tools bill against your Rephrasy plan.
2. Add the server to your client:
Claude Code
Claude Desktop
Add to claude_desktop_config.json (Settings → Developer → Edit Config):
Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
Until the package is on npm you can run it straight from GitHub: replace
"args": ["-y", "@rephrasy/mcp"]with"args": ["-y", "github:rephrasyai/rephrasy-mcp"].
Hosted server (no install)
Rephrasy also runs a hosted MCP server, so clients that speak streamable HTTP need nothing installed locally:
It supports OAuth as well — ChatGPT and other clients that require it discover it from the server and send you through a one-time consent page, so the key never reaches the client. The hosted server carries a wider tool set (engine recommendations, readability, bring-your-own-key detectors). Full docs: https://rephrasy.ai/mcp.
Tools
humanize
Returns the rewritten text plus the number of words charged.
Models
v3 and Undetectable Model v2 are retired. Old calls keep working: the API routes v3 to superstealth and v2 to v4. The v3-only style parameter is gone.
detect
Returns JSON with scores.overall (lower = more human-like) and, in per-sentence mode, sentences.
humanize_image
A diffusion pass removes invisible AI watermarks such as SynthID while subject,
composition and resolution stay the same. Costs 10 credits on standard and 20
on hq; a failed image is refunded. Standard images are usually saved within the
call. If a job is still running, the tool returns a job_id instead.
get_image_result
Waits up to about 50 seconds per call and saves the image once it is done. Results stay available for 72 hours and also show up in your image history on rephrasy.ai.
Example prompts
- "Humanize this paragraph, then run detect on the result to verify it."
- "Humanize this essay with superstealth so it passes Pangram."
- "Rewrite my draft with the humanize tool using model
<style-id>(my writing style)." - "Check which sentences of this post read as AI-written."
- "Humanize ~/Desktop/hero.png in hq and tell me where you saved it."
Development
License
MIT © Rephrasy
Source: README.md at commit 579032c
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts