dataverse vs PJM vs MISO Energy Arbitrage Oracle
dataverse is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 2 (Copilot CLI: github/awesome-copilot, Copilot CLI: github/copilot-plugins). PJM vs MISO Energy Arbitrage Oracle is an MCP server published by dornansgar390-hue. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |  dataverse |  PJM vs MISO Energy Arbitrage Oracle |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 1.16.1 Forks (GitHub): 63 Stars (GitHub): 248 Not marked · First seen |
Not listed |
| Copilot CLI: github/copilot-plugins | Listed Version: not stated Forks (GitHub): 63 Stars (GitHub): 248 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.3.1 Forks (GitHub): 0 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 | dataverse | PJM vs MISO Energy Arbitrage Oracle |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 248 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 63 (better) | 0 (worse) |
| Last release (differs) | 2026-10-23 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (energy-arbitrage.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/microsoft/dataverse-skills | github.com/dornansgar390-hue/energy-oracle-group |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-16 |
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
dataverse
Microsoft Dataverse plugin for coding agents, covering record CRUD, bulk data operations, advanced queries, schema and metadata, administration, security, environment management, and solution lifecycle through MCP, CLI, and SDK workflows.
PJM vs MISO Energy Arbitrage Oracle
PJM/MISO energy arbitrage. Intel TDX attested, on-chain every 60 min. MCP tools for AI agents.
How to run each
dataverse
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
PJM vs MISO Energy Arbitrage Oracle As a remote MCP server
claude mcp add --transport http energy-oracle https://energy-arbitrage.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only PJM vs MISO Energy Arbitrage Oracle 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: dataverse · What it can do: PJM vs MISO Energy Arbitrage Oracle · 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 the public marketplace file https://github.com/github/copilot-plugins/blob/HEAD/.github/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.