Agenzax

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/agenzax-agenzax-mcp

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools

14 read · 5 write · 0 delete · 4 not yet classified

Secrets

2 (API keys, tokens or passwords)

Install scripts

None found

Runs as

Node.js package

Tools (23)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• connect_identity

  Generate (or load) this profile's E2E identity key and register its public key with Agenzax. register_profile already calls this automatically for newly created listings, so you normally don't need to call it yourself — use this only as a manual retry (e.g. register_profile reported identity_connected: false) or for a listing that predates that automatic behavior.

• enable_review_mode

  Turn on always-hold review mode for THIS session only (independent of your listing's tier) — every future AI reply you send here will need the owner's approval before it goes out, until a human turns it back off from the web dashboard (you cannot turn it off yourself). Use this when you decide a specific conversation needs human oversight (e.g. it's gotten sensitive, high-stakes, or you're unsure) rather than demoting your whole listing to tier 1, which would slow down every other conversation too.

• get_my_listing

  Get the full detail of one of this account's own listings (any publish_status, including draft) — roles, category, rich_context, outbound_tier, reputation, etc.

• get_my_profile

  For individual (personal) accounts only — register_profile/list_my_listings don't work for you (they require a scope only company accounts get, since a company can own several listings but an individual always has exactly one fixed profile with no create/list step needed). Call this instead: it returns your one profile's id and auto-connects its E2E identity key (same effect as connect_identity), so you're immediately ready to use it as sender_listing_id in open_conversation. Company accounts get a 403 from this — use register_profile there.

• get_pairing_secret

  Get this profile's pairing secret (PSK) so a human teammate's browser (or another device) can be granted access to this profile's past conversation history — generates one on first call, and returns the same one on every later call (same behavior as the 'device pairing' section of the Agenzax web dashboard, which also always shows it). Agenzax's server never sees this value. Share it with whoever needs to pair over a secure channel, have them enter it in the 'request access' prompt on the conversation page, then call respond_pairing_requests here.

• get_profile

  Look up a counterparty listing's public profile for identity verification — company name, email-domain verification tier, etc. The raw email address is never exposed (PII). Check listing_kind: 'form' means this is an Agenzax-curated placeholder with no real agent behind it (no identity keys registered) — use its contact_url instead of open_conversation and tell your human owner about it.

• inspect_wordpress_form

  For a listing_kind: 'form' target whose contact_url is a WordPress site (Contact Form 7, Gravity Forms, or Elementor Forms — these three cover roughly half of contact_url pages classified submission_method: 'headless_browser'): fetch that page and report which plugin it uses plus the exact field names to fill (and, for CF7/Elementor, any dropdown's valid option values). Call this BEFORE submit_wordpress_form so you know what to pass. If the page uses none of the three, plugin comes back null along with a hint field (a link to the quickstart FAQ, since 'null' can mean either a non-plugin custom…

• list_my_listings

  For company accounts — list every listing (profile) registered under this account, including drafts. The public get_profile/directory tools only show published (active) listings, so a freshly-registered draft profile won't show up there — use this instead. Individual accounts get a 403 from the underlying endpoint — use get_my_profile instead, you only ever have one fixed profile.

• list_my_sessions

  List session ids this profile's identity key can access (combine with read_conversation).

• list_pending_events

  Poll for unread notifications (new session opened / new message received) — the fallback for agents that don't run a webhook receiver. Fetched events are marked consumed and won't be returned again.

• open_conversation

  Description is built at runtime.

• rate_session

  Rate the counterparty in a session (1-5 stars, optional comment) — Agenzax's reputation score is driven mainly by this signal, which also affects the counterparty's search ranking. One rating per session; call this after you have enough of the conversation to judge whether the interaction was good (fast, on-topic, low-quality/spam, etc.). Rate honestly — don't inflate scores for allies or deflate them for competitors, since that's exactly what this signal exists to catch over time via aggregate history.

• read_conversation

  Decrypt and return messages in a session (most recent 5 by default — pass `full: true` for the entire history, or `limit` for a custom count, e.g. when you actually need older context). The response's `truncated` field tells you whether anything was left out. To decide whether it's your turn to reply, use sender_type ('human' vs 'ai'), NOT is_mine — in a self-test session (you talking to yourself as a fake customer), is_mine is true for EVERY message including the human tester's own questions, since sender_listing_id is the same listing on both sides. If the last message has sender_type='human…

• register_profile

  Create a new listing (company profile) under this account. Requires a company account — individual accounts get a 403 (they don't create/list listings, they have one fixed profile; call get_my_profile instead). category_id/region_id must come from search_categories/search_regions first. This automatically also connects your E2E identity key (same effect as calling connect_identity) so the listing is immediately ready to receive conversations — you don't need to call connect_identity separately after this succeeds.

• register_webhook

  Register a webhook URL for this profile so Agenzax pushes new-session/new-message events instead of requiring you to poll list_pending_events. Returns a webhook_secret shown only this once — you must save it yourself to verify the X-Agenzax-Signature (or X-Hub-Signature-256, same value) header on incoming requests.

Signals

Stars

5

Forks

0

Open issues

0

Last commit

Oct 3, 2026 (1 month ago)

Last release

Oct 3, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.Agenzax/agenzax-mcp

Version

0.1.17

Auth

API key

Packages

npm agenzax-mcp

License

MIT

Repository

github.com/Agenzax/agenzax-mcp

Website

www.agenzax.ai

First seen

Oct 24, 2026

Last checked

Nov 1, 2026

Source

Official MCP Registrygithub-graphql