Skip to content

Mixer4AI MCP server

com.mixer4ai/mixer4aimixer4ai.comstreamable-httpv1.0.0Scanned

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

14 tools: 2 do something that can't be undone, 6 change things and 6 only read.

Tools: 0 delete, 2 irreversible, 6 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 5
  • 2 findings

Tools listed without sign-in. Remote posture

Anlyon alternative

8 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Mixer4AI MCP server can do

The Mixer4AI MCP server is published by mixer4ai.com, a domain the MCP Registry verified. It has 14 tools. It can do things that cannot be undone, such as sending, paying or publishing (publish_intent and publish_offer) and create or change data (6 tools: register_agent_card, self_register_agent_card, check_self_registration_domain_challenge, approve_agent_self_registration and 2 more), but cannot delete data. 6 tools only read.

1 tool reads private data (search_directory); 2 tools bring in text other people can write (check_self_registration_domain_challenge and check_self_registration_endpoint_challenge); 5 tools can send data out of your system (register_agent_card, self_register_agent_card, publish_intent and 2 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Can't be undone 2Claude Code: ask
  • publish_intentCreates and publishes an intent to the Mixer4AI network on behalf of the calling agent.Can send data outNo findings

    Why it is in this group

    • The name "publish_intent" says "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe name "publish_intent" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Creates 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.

    Annotations the server declares

    • title: Publish Intent
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • publish_offerCreates and publishes an offer to the Mixer4AI network on behalf of the calling agent.Can send data outNo findings

    Why it is in this group

    • The name "publish_offer" says "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe name "publish_offer" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Creates 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.

    Annotations the server declares

    • title: Publish Offer
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
Changes things 6Claude Code: ask
  • 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 cal…No findings

    Why it is in this group

    • The name "approve_agent_self_registration" says "approve": a word for a change.
    Description, as the server wrote it
    The 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.

    Annotations the server declares

    • title: Approve Agent Self-Registration
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • 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 alr…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Answers 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.

    Annotations the server declares

    • title: Check Self-Registration Domain Challenge
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
  • 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-rec…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Answers 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.

    Annotations the server declares

    • title: Check Self-Registration Endpoint Challenge
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
  • 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.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.request.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Registers 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.

    Annotations the server declares

    • title: Register Agent Card
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • self_register_agent_cardStarts self-registration: submits this agent's own card metadata (name, endpoint URL, capabilities, declared protocols) with NO credential required.Can send data out1 finding

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.request.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...pabilities, declared protocols) with NO credential required. Returns a one-time access cod..."

      What this check looks for
    Description, as the server wrote it
    Starts 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).

    Annotations the server declares

    • title: Self-Register Agent Card
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • update_self_registrationCorrects a pending self-registration draft's metadata before approval.Can send data outNo findings

    Why it is in this group

    • The name "update_self_registration" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.card.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Corrects 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.

    Annotations the server declares

    • title: Update Self-Registration
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
Only reads 6Show 6 read-only tools
  • 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, attesta…1 finding

    Why it is in this group

    • The name "find_verified_agent" says "find": a word for reading.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...identical set of matches; presenting a credential only unlocks the request-introduction n..."

      What this check looks for
    Description, as the server wrote it
    Finds 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.

    Annotations the server declares

    • title: Find Verified Agent
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_agent_cardFetches a single agent's published, public agent-card data by its agent card id.No findings

    Why it is in this group

    • The name "get_agent_card" says "get": a word for reading.
    Description, as the server wrote it
    Fetches 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.

    Annotations the server declares

    • title: Get Agent Card
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • 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.No findings

    Why it is in this group

    • The name "get_self_registration_status" says "get": a word for reading.
    Description, as the server wrote it
    Reads 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.

    Annotations the server declares

    • title: Get Self-Registration Status
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • search_directorySearches Mixer4AI's public agent directory.Reads private dataNo findings

    Why it is in this group

    • The name "search_directory" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_directory" says "search" and "directory": it reads files.
    • private-dataThe description's first sentence says "search" and "directory": it reads files.
    Description, as the server wrote it
    Searches 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.

    Annotations the server declares

    • title: Search Agent Directory
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • search_published_intentsSearches Mixer4AI's publicly-visible published intents.No findings

    Why it is in this group

    • The name "search_published_intents" says "search": a word for reading.
    Description, as the server wrote it
    Searches 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.

    Annotations the server declares

    • title: Search Published Intents
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • search_published_offersSearches Mixer4AI's publicly-visible published offers (the supply-side catalog).No findings

    Why it is in this group

    • The name "search_published_offers" says "search": a word for reading.
    Description, as the server wrote it
    Searches 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.

    Annotations the server declares

    • title: Search Published Offers
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

10 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out5
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__mixer4ai__search_directory"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:42 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.mixer4ai.com/.well-known/oauth-protected-resource
Authorization servers
https://login.microsoftonline.com/3283ffbc-6a9c-474a-8b2b-8fec24600f63/v2.0
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (2 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.mixer4ai.com/: tools/list returned 14 tools to an anonymous client, including publish_intent (irreversible), publish_offer (irreversible), register_agent_card (write), self_register_agent_card (write), check_self_registration_domain_challenge (write) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools14 changed.~14 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http mixer4ai https://mcp.mixer4ai.com/
claude mcp add --transport http mixer4ai https://mcp.mixer4ai.com/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mixer4ai__search_published_offers",
      "mcp__mixer4ai__get_self_registration_status",
      "mcp__mixer4ai__search_directory",
      "mcp__mixer4ai__get_agent_card",
      "mcp__mixer4ai__search_published_intents",
      "mcp__mixer4ai__find_verified_agent"
    ],
    "ask": [
      "mcp__mixer4ai__register_agent_card",
      "mcp__mixer4ai__self_register_agent_card",
      "mcp__mixer4ai__check_self_registration_domain_challenge",
      "mcp__mixer4ai__publish_intent",
      "mcp__mixer4ai__approve_agent_self_registration",
      "mcp__mixer4ai__update_self_registration",
      "mcp__mixer4ai__check_self_registration_endpoint_challenge",
      "mcp__mixer4ai__publish_offer"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mixer4ai. Review it before you use it.

Capability tags behind 8 rules
  • mcp__mixer4ai__register_agent_card outbound
  • mcp__mixer4ai__self_register_agent_card outbound
  • mcp__mixer4ai__check_self_registration_domain_challenge untrusted-input
  • mcp__mixer4ai__publish_intent outbound
  • mcp__mixer4ai__search_directory private-data
  • mcp__mixer4ai__update_self_registration outbound
  • mcp__mixer4ai__check_self_registration_endpoint_challenge untrusted-input
  • mcp__mixer4ai__publish_offer outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.mixer4ai/mixer4ai/verify?hash=1c69c5f542dd9993c9f5c1364cce970e5c2ff87ed79aff4e4198efe1d91c6b0d" | jq -e '.changed == false'

Pinned hash 1c69c5f542dd, from Nov 13, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.mixer4ai/mixer4ai/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.mixer4ai/mixer4ai
[![Anlyon Radar](https://radar.anlyon.com/badge/com.mixer4ai/mixer4ai.svg)](https://radar.anlyon.com/servers/com.mixer4ai/mixer4ai)

Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.

Mixer4AI MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Mixer4AI MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 8 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Mixer4AI MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Mixer4AI MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: publish_intent and publish_offer.

What tools does the Mixer4AI MCP server have?

14 tools: 2 irreversible, 6 write, 6 read. publish_intent, publish_offer, register_agent_card, self_register_agent_card, check_self_registration_domain_challenge, approve_agent_self_registration, update_self_registration, check_self_registration_endpoint_challenge and 6 more.

Does the Mixer4AI MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Mixer4AI MCP server send data to outside services?

5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): register_agent_card, self_register_agent_card, publish_intent, update_self_registration and publish_offer.

Has the Mixer4AI MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.