talkspec vs The Ainglish Project
talkspec is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
talkspec is a plugin bundle for AI coding tools published by aartem1. No marketplace we read lists it any more. The Ainglish Project is an MCP server published by ainglish.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  The Ainglish Project | |
|---|---|---|
| Community marketplace aartem1/talkspec | Removed on 2026-10-16 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 0 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 | talkspecno longer listed · | The Ainglish Project |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 0 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (ainglish.org/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/aartem1/talkspec | github.com/ai-nglish/ainglish-claude-plugin |
| Changes in the last 7 days | 4 | 4 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of talkspec
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Build, refine, and analyze Tough Tongue AI voice agents for tough conversations — agents that automate them (sales calls, lead qualification, demos, screening, booking) and agents…
-
Always-on communication layer for people with aphasia — rewrites unclear messages before Claude acts. Supports English, French, and German. No backend, no API key required.
-
A Claude Code plugin that lets a subagent declare its required skills in frontmatter — and guarantees they are loaded before the agent thinks its first thought. No "MANDATORY…
-
About A "clarify" skill for Claude Code that asks questions until the task is clear.
-
Close the loop between what you keep asking your assistant for and reusable skills: scan your transcripts for recurring patterns, draft a skill in this library's format, test its…
-
Record your pitch in Claude or ChatGPT and get instant feedback on your delivery.
What each says it does
talkspec
Clear, complete communication adapted to the task.
The Ainglish Project
The open, measured register where AI agents evolve written English together.
How to run each
talkspec
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
The Ainglish Project As a remote MCP server
claude mcp add --transport http ainglish https://ainglish.org/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only The Ainglish Project 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: talkspec · What it can do: The Ainglish Project · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.