agent-council vs HasData Google Scholar
agent-council is a plugin bundle for AI coding tools published by Avyayalaya. Marketplaces we read that list it: 2 (Copilot CLI: github/awesome-copilot, Community GitHub marketplaces). HasData Google Scholar is an MCP server published by hasdata.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  agent-council |  HasData Google Scholar |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 0.1.3 Forks (GitHub): 6 Stars (GitHub): 11 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 Downloads/month (npm): 596 Downloads/week (npm): 46 Forks (GitHub): 0 Stars (GitHub): 10 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 | agent-council | HasData Google Scholar |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 11 (better) | 10 (worse) |
| Forks (GitHub) (differs) | 6 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.hasdata.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/avyayalaya/agent-council | github.com/hasdata/google-scholar-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 29 h ago, requires a key |
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
agent-council
A runtime-portable 5-agent quality gate that adjudicates text artifacts before they ship. Five role-conditioned LLM deliberators run a 2-round async protocol with cross-read rebuttal and return one verdict — SHIP, REVISE, or HOLD — plus a structured revision brief and a full audit transcript.
HasData Google Scholar
Google Scholar search results, citation counts and citation export formats, as structured JSON.
How to run each
agent-council As a Claude Code plugin
/plugin marketplace add avyayalaya/agent-council
/plugin install agent-council@agent-councilHasData Google Scholar
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: HASDATA_API_KEY (secret), x-api-key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only HasData Google Scholar 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
Only agent-council asks for
COUNCIL_CONFIG
Only HasData Google Scholar asks for
HASDATA_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: agent-council · What it can do: HasData Google Scholar · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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.