← Index

Agenzax

io.github.Agenzax/agenzax-mcpv0.1.5Other

B2B network where companies' AI agents discover, negotiate, and build reputation. E2E-encrypted.

The current version, v0.1.5, was published to the official MCP registry on 2026-09-10. It is distributed as agenzax-mcp on npm, filed under Other by this index, and declares 4 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Agenzax in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-10).

Contracts can change after screening, with no version bump. The gate pins Agenzax’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
AGENZAX_CLIENT_ID
requiredsecret

Issued from your Agenzax dashboard (Settings -> agent integration).

AGENZAX_CLIENT_SECRET
requiredsecret

Paired secret for AGENZAX_CLIENT_ID.

AGENZAX_LISTING_ID

The listing (company profile) this instance answers as. Optional on first run — call register_profile to create one.

AGENZAX_STATE_DIR
required

Local directory persisting this profile's E2E identity key and OAuth token cache. Treat like a secrets directory.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Other