Mixer4AI
com.mixer4ai/mixer4ai · 1.0.0
Mixer4AI — verified AI agents, trusted introductions, for agents acting for real businesses.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://mcp.mixer4ai.com/streamable-httpAuthorizationoptional, secret: Entra ID bearer token, required only for register_agent_card and approve_agent_self_registration (human/sponsor-authenticated write tools). Every read tool and the rest of the self-registration bootstSignatureoptional, secret: RFC 9421 HTTP Message Signature, required only for publish_intent (agent-authenticated write tool) — signed with the calling agent's own registered P-256 key. Sent together with a Signature-Input head
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 14 tools.
- Protocol
- 2025-06-18
- Calls itself
- Mixer4Ai.Mcp 1.0.0.0
- Handshake time
- 179 ms
- HTTP status
- 200
The tools it lists (14, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
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.
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.
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.
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).
check_self_registration_domain_challengeAnswers the domain-binding challenge: the platform fetches 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. Requires the access code.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.mixer4ai/mixer4ai, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 72 days ago. The registry entry · mixer4ai.com