Ext Ops Panel
Open dashboard
Comparison

microsoft-365-agents-toolkit vs RegBase Japan Corporate Registry Diff

microsoft-365-agents-toolkit is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/copilot-plugins). RegBase Japan Corporate Registry Diff is an MCP server published by lexusdev7. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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

Where each is published
Marketplacemicrosoft-365-agents-toolkitRegBase Japan Corporate Registry Diff
Copilot CLI: github/copilot-plugins Listed
Version: 1.1.0
Forks (GitHub): 149
Stars (GitHub): 1 057
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
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

microsoft-365-agents-toolkit vs RegBase Japan Corporate Registry Diff
Factmicrosoft-365-agents-toolkitRegBase Japan Corporate Registry Diff
Marketplaces that list it11
Stars (GitHub) (differs)1 057No figure on GitHub
Forks (GitHub) (differs)149No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (regbase-mcp.local-connect-design.trade/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/work-iqNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-09
Endpoint at the last check (differs)no remote endpoint we checkResponded 20 h ago

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

microsoft-365-agents-toolkit

In its own words, on Copilot CLI: github/copilot-plugins:

Toolkit for building Microsoft 365 Copilot declarative agents — scaffolding, JSON manifest development, and capability configuration.

RegBase Japan Corporate Registry Diff

In its own words, on Official MCP Registry:

Japan corporate registry daily diff: new, changed and closed companies, lookup, signed-record check

How to run each

microsoft-365-agents-toolkit

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

RegBase Japan Corporate Registry Diff As a remote MCP server

Claude Code
claude mcp add --transport http jp-corp-diff https://regbase-mcp.local-connect-design.trade/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: X-API-Key header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only RegBase Japan Corporate Registry Diff 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: microsoft-365-agents-toolkit · What it can do: RegBase Japan Corporate Registry Diff · Compare two other plugins

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.

Where the data comes from: how the catalog is built