SpryTools API MCP Server vs Textavia MCP
SpryTools API MCP Server is an MCP server published by sprytools.com. Marketplaces we read that list it: 1 (Official MCP Registry). Textavia MCP is an MCP server published by catorch. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  SpryTools API MCP Server | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.2 Downloads/month (npm): 125 Downloads/week (npm): 18 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | SpryTools API MCP Server | Textavia MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.sprytools.com/mcp) | On your machine (@textavia/mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/grenzfrei/sprytools-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-22 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
SpryTools API MCP Server
Utility tools for AI agents: hashing, text stats, validation, DNS, currency, GEO audits.
Textavia MCP
Local-first MCP server for text, JSON, Base64, CSV, regex, and developer utilities.
How to run each
SpryTools API MCP Server As a remote MCP server
claude mcp add --transport http sprytools https://api.sprytools.com/mcp --header "x-api-key: <YOUR_X_API_KEY>"Requires: x-api-key header
Textavia MCP As a local MCP server: npm package
claude mcp add --transport stdio textavia-mcp -- npx -y @textavia/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SpryTools API MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: SpryTools API MCP Server · What it can do: Textavia MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.