io.humantone/humantone
HumanTone
Is the HumanTone MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
Humanize AI drafts in 60+ languages and check AI likelihood. Sign in with your HumanTone account.
needs auth probed 2026-11-15 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint:
- Endpoint
- https://mcp.humantone.io/mcp (streamable-http)
- Host
- mcp.humantone.io
- Package
- The publisher's package npm:humantone-mcp did not list its tools in the container: needs env, MCP error -32000: Connection closed humantone-mcp: HUMANTONE_API_KEY env var is missing or invalid. Get a key at https://app.humantone.io/settings/api.
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.humantone.io/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server mcp.humantone.io, PKCE S256, grants authorization_code, refresh_token.
Scopes humantone.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/humantone/humantone-mcp
- Website
- https://humantone.io/docs/mcp/
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Servers that mention likelihood or languages.
- Canvora ai.canvora/canvora · needs auth
- ai.cdbx/mcp-server · needs auth
- Hermitsh Texts ai.hermitsh/texts · needs auth
- i18n-agent ai.i18nagent/i18n-agent · needs auth
- Maguyva ai.maguyva/maguyva · needs auth
- mazdek AI — Kurdish Language Tools ai.mazdek/mazdek-ai · needs auth
- TheWholeTorah ai.thewholetorah/thewholetorah · alive
- User Intuition ai.userintuition/research · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.