Ext Ops Panel
Open dashboard
Comparison

com.amalgament/public-query vs parcelapi.net

com.amalgament/public-query is an MCP server published by amalgament.com. Marketplaces we read that list it: 1 (Official MCP Registry). parcelapi.net is an MCP server published by parcelapi.net. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplacecom.amalgament/public-queryparcelapi.net
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.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

com.amalgament/public-query vs parcelapi.net
Factcom.amalgament/public-queryparcelapi.net
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.amalgament.com/mcp)Remote server (api.parcelapi.net/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
RepositoryNot statedNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-16
Endpoint at the last check (differs)Responded 2 days ago, requires a keynot checked yet

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

com.amalgament/public-query

In its own words, on Official MCP Registry:

Agent-native MCP over US public + government records, entity- and parcel-keyed.

parcelapi.net

In its own words, on Official MCP Registry:

US property parcels and building permits from cleared public sources. No owner data. Pay per record.

How to run each

com.amalgament/public-query As a remote MCP server

Claude Code
claude mcp add --transport http public-query https://api.amalgament.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: X-API-Key header

parcelapi.net As a remote MCP server

Claude Code
claude mcp add --transport http parcelapi https://api.parcelapi.net/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only com.amalgament/public-query 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: com.amalgament/public-query · What it can do: parcelapi.net · Compare two other plugins

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