install

Additional install commands

macOS

Homebrewverified · 100%

brew install metaproxy

local Homebrew formula metadata

MacPortsverified · 94%

sudo port install metaproxy

MacPorts ports tree · net/metaproxy/Portfile · source: api.github.com

overview

Package summary

Z39.50 proxy and router utilizing Yaz toolkit

Project links

Commands and aliases

metaproxy
metaproxy-config

history

Project history and usage

Metaproxy is Index Data's Z39.50/SRW/SRU proxy, router, and metasearch server for library and information-retrieval systems. The upstream repository identifies it as a universal Z39.50/SRU router with Index Data copyright beginning in 2005, while the product page describes it as a server that presents a single standards-based front end to multiple back-end database servers.

Project history

The technical core is a configurable routing pipeline. The manual describes Metaproxy as a standalone program that accepts requests from information-retrieval clients using protocols such as ANSI/NISO Z39.50 and SRU, acts as a client to back-end servers, and satisfies requests by transforming, multiplexing, forwarding, merging, and returning results. Its XML configuration defines routes made of filters for operations such as accepting packets, logging, query transformation, multiplexing, and SRU-to-Z39.50 translation; additional filters can be added as loadable modules.

Adoption history

Its adoption niche is narrow but durable: libraries, catalogs, and discovery systems that need standards-based search interoperability. The Library of Congress documents an Index Data MetaProxy deployment as an SRW/SRU/Z39.50 gateway to its Folio and Zebra Z39.50 servers, which illustrates the kind of institutional infrastructure where the tool appears. Related documentation from the Library of Congress also explains why SRU and Z39.50 gateways matter: SRU carries Z39.50-style search semantics into web-service form.

How it is used

As a package-manager entry, metaproxy is specialist server software. Homebrew and MacPorts make it easier for integrators and library-system developers to install the router and its companion metaproxy-config tool on development or small deployment machines without building the YAZ-based stack by hand.

Sources

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for metaproxy. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 6 platform targets.
Installs with 3 runtime dependencies.
Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

Command	Kind	Exposure	Note
`metaproxy`	cli	global executable
`metaproxy-config`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08

manager version1.22.4

manager updated2026-05-21

local dataok

upstreamnot checked

latest detectednot detected

https://www.indexdata.com/resources/software/metaproxy/

infoRelease/tag comparison is only available for GitHub repositories.https://www.indexdata.com/resources/software/metaproxy/none confidence

install metadata

Package metadata

Package key	brew:metaproxy
Version	1.22.4
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/metaproxy
Homepage	https://www.indexdata.com/resources/software/metaproxy/
Repository	https://github.com/indexdata/metaproxy
Upstream docs	https://software.indexdata.com/metaproxy/doc
License	GPL-2.0-or-later
Source archive	https://ftp.indexdata.com/pub/metaproxy/metaproxy-1.22.4.tar.gz
Last updated	2026-05-21T10:31:05Z
Pulse	updated
Dependencies	boost, yaz, yazpp
Build dependencies	pkgconf
Uses from macOS	libxml2, libxslt
Bottle	available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	metaproxy
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

MacPorts95%

metaproxy

sudo port install metaproxy

normalized package name match
Matched by: Metaproxy

MacPorts ports tree · api.github.com · MacPorts ports tree: net/metaproxy/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/metaproxy.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Install metaproxy with Homebrew, MacPorts