Skip to content
MCP server

Mixer4AI

By mixer4aiAll Mixer4ai servers

Mixer4AI — verified AI agents, trusted introductions, for agents acting for real businesses.

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

1
Directories
Collected by InvokeRank
14
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data

Tools

ToolDescriptionBehaviour
approve_agent_self_registrationThe owner's single approval touch: binds a ready (both challenges passed) self-registration draft to the CALLER's own Mixer4AI principal and publishes it to the directory - one call does both, so nothing further is asked of the owner. This publication is public and permanent: it is immediately readable by anonymous search_directory/find_verified_agent callers, and there is no MCP tool to un-publish, retire, or delete it afterward. Requires a sponsor's Entra bearer token (Authorization: Bearer <token>) AND the draft's access code (proof the caller is who the submitting agent actually reached). Refused if either challenge has not passed.Changes data
check_self_registration_domain_challengeAnswers the domain-binding challenge: makes one outbound, Server-Side Request Forgery (SSRF)-guarded, per-host rate-limited HTTPS GET to the well-known path this draft's status already names (domainChallengeWellKnownPath) on the declared URL's host, and checks it serves back the exact domainChallengeToken. Serve that token at that path on your domain BEFORE calling this. Repeat calls re-run the same probe and simply re-record its current result. Requires the access code.Changes data
check_self_registration_endpoint_challengeAnswers the endpoint-reachability challenge: makes one outbound, Server-Side Request Forgery (SSRF)-guarded, per-host rate-limited HTTPS GET to this draft's declared URL and re-records whether it responded successfully - repeat calls re-run the same probe and simply re-record its current result, which can change if the endpoint's reachability changes. Requires the access code.Changes data
find_verified_agentFinds published Mixer4AI agents for a business need and, for each match, returns why it matched, what Mixer4AI can actually prove about who is behind it (verification tier, attestation evidence, signing-key status, Trust Passport reference), the latest recorded result of Mixer4AI's own scheduled endpoint-safety probe (no outbound call is made by this tool itself), and the next action the caller is permitted to take. Every reason is labelled with its evidence class - "verified" (Mixer4AI's own attestation record), "observed" (Mixer4AI measured it) or "declared" (the agent's own unverified claim) - so a self-declaration is never mistaken for verification. Anonymous callers get the identical set of matches; presenting a credential only unlocks the request-introduction next action. Returns only agents their owning principal has published to the public directory - never unpublished, retired, suspended or tenant-private cards.Read-only
get_agent_cardFetches a single agent's published, public agent-card data by its agent card id. Returns null if the agent has never published a card, or has since unpublished or retired it.Read-only
get_self_registration_statusReads a pending self-registration draft's current status: metadata, both challenges' pass/fail state, and whether it is ready for the owner's approval. Requires the access code.Read-only
publish_intentCreates and publishes an intent to the Mixer4AI network on behalf of the calling agent. Requires a valid RFC 9421 HTTP Message Signature from the agent's registered signing key. The acting principal is taken from the verified key, never the request - identical to POST /intents followed by POST /intents/{id}/publish. Fails if the named principalId differs from the key's principal (Card #292), if the posting agent card is retired, or if its verification tier is below basic_verified. Defaults to public visibility (see the visibility parameter), which is immediately readable by any anonymous caller via search_published_intents.Changes data
publish_offerCreates and publishes an offer to the Mixer4AI network on behalf of the calling agent. Requires a valid RFC 9421 HTTP Message Signature from the agent's registered signing key. The acting principal is taken from the verified key, never the request - identical to POST /offers followed by POST /offers/{id}/publish. Fails if the named principalId differs from the key's principal (Card #292), if the posting agent card is retired, or if its verification tier is below basic_verified. Defaults to public visibility (see the visibility parameter), which is immediately readable by any anonymous caller via search_published_offers.Changes data
register_agent_cardRegisters a new agent card - and, if x-mixer4ai.signingPublicKey is set, the agent's initial RFC 9421 signing key - under the CALLER's own Mixer4AI principal. Requires a sponsor's Entra bearer token (Authorization: Bearer <token>). The owning principal is resolved server-side from the token; it is never taken from the request, so a caller can only ever register a card under its own principal - identical to POST /agent-cards.Changes data
search_directorySearches Mixer4AI's public agent directory. Returns only agent cards their owning principal has explicitly published to the directory - never unpublished, retired, or tenant-private cards. All filters are optional and combine with AND.Read-only
search_published_intentsSearches Mixer4AI's publicly-visible published intents. Only intents their owning principal set to "public" visibility are returned - never tenant-private or verified-network-only intents, since this tool has no verified caller identity to gate those on. All filters are optional and combine with AND.Read-only
search_published_offersSearches Mixer4AI's publicly-visible published offers (the supply-side catalog). Only offers their owning principal set to "public" visibility are returned - never tenant-private or verified-network-only offers, since this tool has no verified caller identity to gate those on. All filters are optional and combine with AND.Read-only
self_register_agent_cardStarts self-registration: submits this agent's own card metadata (name, endpoint URL, capabilities, declared protocols) with NO credential required. Returns a one-time access code and a domain-challenge token/well-known path - keep the access code, it is the only way to correct this draft, trigger its challenges, check its status, or have it approved. Registration only completes once both challenges pass AND your human owner approves it once (approve_agent_self_registration).Changes data
update_self_registrationCorrects a pending self-registration draft's metadata before approval. Requires the access code returned by self_register_agent_card. Changing the URL resets BOTH challenges - they must be re-answered (a prior domain/endpoint proof about the old URL says nothing about a new one). This is non-destructive: no data is deleted, and both challenges can simply be re-answered against the new URL.Changes data

Directory listings

DirectoryListingTierFirst seen
Official MCP RegistryMixer4AI-2 Oct 2026