evalloop vs LiveScore MCP
evalloop is a plugin bundle for AI coding tools published by kingmadellc. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). LiveScore MCP is an MCP server published by holoduke. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |   LiveScore MCP | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0c586f1 No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.3.1 Forks (GitHub): 0 Stars (GitHub): 5 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 | evalloop | LiveScore MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 5 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (livescoremcp.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| 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/kingmadellc/claude-plugins | github.com/holoduke/livescore-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-13 |
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
evalloop
Autonomous prompt optimization using Karpathy's autoresearch pattern. Editable file + fixed eval metric + autonomous improvement loop.
LiveScore MCP
Football live scores, fixtures, standings, top scorers, matches, teams and players for 1000+ leagues
How to run each
evalloop As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install evalloop@claude-communityLiveScore MCP As a remote MCP server
claude mcp add --transport http livescore-mcp https://livescoremcp.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only LiveScore MCP 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: evalloop · What it can do: LiveScore MCP · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.