Crowdin MCP by usefulapi MCP server
online · 100% uptimeby usefulapi.io·
io.usefulapi/crowdin·v1.33.0MCP server for Crowdin — projects, files, strings, translation progress, tasks, and members.
D42/100grade D
Safety scan
D42/100
not scanned yet
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Crowdin MCP by usefulapi yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Crowdin MCP by usefulapi tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Crowdin MCP by usefulapi compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 42/100
- higher than 8% of 48,273 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 254 ms
- faster than 54% of 30,037 servers
Release history: 13 versions in the registry since 2026-07-17, latest 2026-10-31, typically one every 1 day.
Install Crowdin MCP by usefulapi in Claude Code, Cursor or VS Code
claude mcp add --transport http crowdin https://crowdin.usefulapi.io/mcp
Crowdin MCP by usefulapi: common questions
- Is Crowdin MCP by usefulapi MCP server safe?
- Not recommended: it is graded D (42/100). Read the Crowdin MCP by usefulapi safety report
- How do I install Crowdin MCP by usefulapi?
- It runs remotely at crowdin.usefulapi.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Crowdin MCP by usefulapi need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Crowdin MCP by usefulapi maintained?
- The last commit was 62 days ago (2026-09-01). The latest release is v1.33.0.
- Is Crowdin MCP by usefulapi up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Crowdin MCP by usefulapi compare with other MCP servers?
- safety score 42/100 (higher than 8% of 48,273 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 254 ms (faster than 54% of 30,037 servers). Full comparison.