Ext Ops Panel
Open dashboard
Comparison

microsoft-365-agents-toolkit vs SEFAZ SPU: Emitir Certidões de Imóveis da União

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). SEFAZ SPU: Emitir Certidões de Imóveis da União is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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-toolkitSEFAZ SPU: Emitir Certidões de Imóveis da União
Copilot CLI: github/copilot-plugins Listed
Version: 1.1.0
Forks (GitHub): 148
Stars (GitHub): 1 043
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
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

microsoft-365-agents-toolkit vs SEFAZ SPU: Emitir Certidões de Imóveis da União
Factmicrosoft-365-agents-toolkitSEFAZ SPU: Emitir Certidões de Imóveis da União
Marketplaces that list it11
Stars (GitHub) (differs)1 043 (better)0 (worse)
Forks (GitHub) (differs)148 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.mcp.ai/p_sefaz_spu_certidao_imoveis)
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-iqgithub.com/mcp-dir/sefaz_spu_certidao_imoveis-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-28

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.

SEFAZ SPU: Emitir Certidões de Imóveis da União

In its own words, on Official MCP Registry:

SEFAZ SPU: Emitir Certidões de Imóveis da União, official-source lookup. Platform-hosted, pay per qu

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.

SEFAZ SPU: Emitir Certidões de Imóveis da União As a remote MCP server

Claude Code
claude mcp add --transport http sefaz-spu-certidao-imoveis-mcp https://api.mcp.ai/p_sefaz_spu_certidao_imoveis

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

Only SEFAZ SPU: Emitir Certidões de Imóveis da União 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: SEFAZ SPU: Emitir Certidões de Imóveis da União · 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