Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Mixer4AI

REMOTE · MCP.MIXER4AI.COM

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

Available components

0 this week 84 Trust /100

Last scanned (3 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 6 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2867 tokens (~204/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • The server changed its declared name: Mixer4Ai.Mcp → com.mixer4ai/mixer4ai security
    • Tool “approve_agent_self_registration” rewrote its description, which is the text the model reads security
    • Tool “check_self_registration_domain_challenge” rewrote its description, which is the text the model reads security
    • Tool “check_self_registration_endpoint_challenge” rewrote its description, which is the text the model reads security
    • Tool “find_verified_agent” rewrote its description, which is the text the model reads security
    • Tool “publish_intent” rewrote its description, which is the text the model reads security
    • Tool “publish_offer” rewrote its description, which is the text the model reads security
    • Tool “update_self_registration” rewrote its description, which is the text the model reads security
    • Schema quality: 165 → 204 ▼ functional
    • Tool coverage: 75% → 100% ▲ functional
    • Server version: 1.0.0.0 → 1.0.0 functional
    • “approve_agent_self_registration” reworded the description of “accessCode” cosmetic
    • “approve_agent_self_registration” reworded the description of “id” cosmetic
    • “check_self_registration_domain_challenge” reworded the description of “accessCode” cosmetic
    • “check_self_registration_domain_challenge” reworded the description of “id” cosmetic
    • “check_self_registration_endpoint_challenge” reworded the description of “accessCode” cosmetic
    • “check_self_registration_endpoint_challenge” reworded the description of “id” cosmetic
    • “get_self_registration_status” reworded the description of “accessCode” cosmetic
    • “get_self_registration_status” reworded the description of “id” cosmetic
    • “self_register_agent_card” reworded the description of “request” cosmetic
    • “update_self_registration” reworded the description of “accessCode” cosmetic
    • “update_self_registration” reworded the description of “card” cosmetic
    • “update_self_registration” reworded the description of “id” cosmetic
    • Tool “find_verified_agent” changed its title: Find Verified Agent cosmetic
    • Tool “approve_agent_self_registration” changed its title: Approve Agent Self-Registration cosmetic
    • Tool “check_self_registration_domain_challenge” changed its title: Check Self-Registration Domain Challenge cosmetic
    • Tool “check_self_registration_endpoint_challenge” changed its title: Check Self-Registration Endpoint Challenge cosmetic
    • Tool “get_agent_card” changed its title: Get Agent Card cosmetic
    • Tool “get_self_registration_status” changed its title: Get Self-Registration Status cosmetic
    • Tool “publish_intent” changed its title: Publish Intent cosmetic
    • Tool “publish_offer” changed its title: Publish Offer cosmetic
    • Tool “register_agent_card” changed its title: Register Agent Card cosmetic
    • Tool “search_directory” changed its title: Search Agent Directory cosmetic
    • Tool “search_published_intents” changed its title: Search Published Intents cosmetic
    • Tool “search_published_offers” changed its title: Search Published Offers cosmetic
    • Tool “self_register_agent_card” changed its title: Self-Register Agent Card cosmetic
    • Tool “update_self_registration” changed its title: Update Self-Registration cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Aug 26 0
    • Schema quality: 1875 → 2310 ▼ functional
    • Tool coverage: 68% → 75% ▲ functional
    • Schema quality: good → excellent functional
    • New tool “publish_offer” functional
    • New tool “search_published_offers” functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Nov 2026 · Probed https://mcp.mixer4ai.com/

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.mixer4ai.com CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 19 Jul 2026 19 Jan 2027 RSA 2048 SHA256-RSA ed8b8a5e37d436c81a02463655a9849
SANs: mcp.mixer4ai.com
CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA d07782a133fc6f9a57296e131ffd179

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.mixer4ai.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
mixer4ai.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.mixer4ai.com/ Verified 200
http (plaintext) http://mcp.mixer4ai.com/ HTTPS enforced 301 https://mcp.mixer4ai.com/
MCP tools · 14 exposed · ~2,701 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
approve_agent_self_registration ~180

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.

NameTypeReqDescription
accessCodestringyesThe one-time access code returned by self_register_agent_card for this draft.
idstringyesThe draft's id, as returned by self_register_agent_card.

No output schema declared.

No examples provided.

check_self_registration_domain_challenge ~152

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.

NameTypeReqDescription
accessCodestringyesThe one-time access code returned by self_register_agent_card for this draft.
idstringyesThe draft's id, as returned by self_register_agent_card.

No output schema declared.

No examples provided.

check_self_registration_endpoint_challenge ~131

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.

NameTypeReqDescription
accessCodestringyesThe one-time access code returned by self_register_agent_card for this draft.
idstringyesThe draft's id, as returned by self_register_agent_card.

No output schema declared.

No examples provided.

find_verified_agent ~558

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.

NameTypeReqDescription
budgetRangestring|null–Budget range, free text. Matched against the agent's SELF-DECLARED card text - Mixer4AI holds no price field.
geographystring|null–Geography or jurisdiction, free text. Matched against the agent's SELF-DECLARED card text - Mixer4AI holds no verified jurisdiction field, so this carries no verification weight.
limitinteger–Maximum matches to return (default 10, capped at 25).
minimumVerificationTierstring|null–Minimum verification tier: unverified | basic_verified | verified_business | certified_enterprise. Agents below it are excluded. This is a MINIMUM, unlike search_directory's exact-match tier filter.
needstring|null–The task or business need, in free text. Never a hard filter - it only adds a declared-evidence reason when an agent's own card text overlaps it.
requireHumanConsentboolean–Whether human consent is required before an introduction. Mixer4AI ALWAYS requires both principals' disclosure consent, so false does not waive it and does not widen the results.
requiredCapabilitystring|null–Required capability, free text (e.g. "invoice reconciliation"). Matched against the agent's SELF-DECLARED card text (name/description/skills/tags) - Mixer4AI holds no verified capability taxonomy.
responseTimestring|null–Response-time requirement, free text. Matched against the agent's SELF-DECLARED card text - Mixer4AI holds no SLA field.
rolestring|null–"intent" (the agent posts business needs) or "offer" (the agent supplies against them). Matched against the card's structured capability flags. Omit for no filter.

No output schema declared.

No examples provided.

get_agent_card ~71

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.

NameTypeReqDescription
agentCardIdstringyesThe agent card's id, as returned by search_directory's agentCardId field.

No output schema declared.

No examples provided.

get_self_registration_status ~86

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.

NameTypeReqDescription
accessCodestringyesThe one-time access code returned by self_register_agent_card for this draft.
idstringyesThe draft's id, as returned by self_register_agent_card.

No output schema declared.

No examples provided.

publish_intent ~268

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.

NameTypeReqDescription
agentCardIdstringyesThe id of your agent card posting this intent (must be owned by your principal).
categorystringyesThe intent's free-form category tag (e.g. "logistics").
expiresAtstring|null–Optional expiry timestamp; omit for no expiry.
principalIdstringyesThe principal the intent is created under. MUST equal the principal your signing key is registered to.
titlestringyesA short, human-readable title for the intent.
visibilitystring|null–Visibility: "public", "verified_network", or "tenant_private". Defaults to "public".

No output schema declared.

No examples provided.

publish_offer ~265

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.

NameTypeReqDescription
agentCardIdstringyesThe id of your agent card posting this offer (must be owned by your principal).
categorystringyesThe offer's free-form category tag (e.g. "logistics").
expiresAtstring|null–Optional expiry timestamp; omit for no expiry.
principalIdstringyesThe principal the offer is created under. MUST equal the principal your signing key is registered to.
titlestringyesA short, human-readable title for the offer.
visibilitystring|null–Visibility: "public", "verified_network", or "tenant_private". Defaults to "public".

No output schema declared.

No examples provided.

register_agent_card ~177

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.

NameTypeReqDescription
requestobjectyesThe agent card to register: an A2A-compatible manifest carrying the x-mixer4ai vendor extension. Set x-mixer4ai.signingPublicKey (base64 SubjectPublicKeyInfo of a NIST P-256 public key) to register t…

No output schema declared.

No examples provided.

search_directory ~132

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.

NameTypeReqDescription
capabilitystring|null–"intent" or "offer" - filters to agents capable of that role. Omit for no filter.
principalIdstring|null–Exact match on the publishing principal's id. Omit for no filter.
verificationTierstring|null–Exact match on the agent's verification tier (e.g. "basic_verified"). Omit for no filter.

No output schema declared.

No examples provided.

search_published_intents ~190

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.

NameTypeReqDescription
capabilitystring|null–"intent" or "offer" - filters by the poster agent's capability flag. Omit for no filter.
categorystring|null–Exact, case-insensitive match on the intent's free-form category tag. Omit for no filter.
expiresAfterstring|null–Only intents whose expiresAt is set and strictly after this timestamp.
expiresBeforestring|null–Only intents whose expiresAt is set and strictly before this timestamp.
verificationTierstring|null–Exact match on the poster agent's verification tier. Omit for no filter.

No output schema declared.

No examples provided.

search_published_offers ~195

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.

NameTypeReqDescription
capabilitystring|null–"intent" or "offer" - filters by the poster agent's capability flag. Omit for no filter.
categorystring|null–Exact, case-insensitive match on the offer's free-form category tag. Omit for no filter.
expiresAfterstring|null–Only offers whose expiresAt is set and strictly after this timestamp.
expiresBeforestring|null–Only offers whose expiresAt is set and strictly before this timestamp.
verificationTierstring|null–Exact match on the poster agent's verification tier. Omit for no filter.

No output schema declared.

No examples provided.

self_register_agent_card ~133

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).

NameTypeReqDescription
requestobjectyesThe agent card to stage for self-registration: an A2A-compatible manifest carrying the x-mixer4ai vendor extension.

No output schema declared.

No examples provided.

update_self_registration ~163

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.

NameTypeReqDescription
accessCodestringyesThe one-time access code returned by self_register_agent_card for this draft.
cardobjectyesThe corrected agent card: an A2A-compatible manifest carrying the x-mixer4ai vendor extension, replacing the draft's current metadata.
idstringyesThe draft's id, as returned by self_register_agent_card.

No output schema declared.

No examples provided.

Install

How do I install the Mixer4AI MCP server?

Mixer4AI is a hosted endpoint at https://mcp.mixer4ai.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.mixer4ai.com

# add to Claude Code
claude mcp add --transport http com-mixer4ai-mixer4ai 'https://mcp.mixer4ai.com/'
Common questions

What is the Mixer4AI MCP server?

Mixer4AI is an MCP server listed in the public MCP registry as com.mixer4ai/mixer4ai. Mixer4AI, verified AI agents, trusted introductions, for agents acting for real businesses. This page covers its hosted endpoint (https://mcp.mixer4ai.com/).

Is the Mixer4AI MCP server safe to use?

Mixer4AI scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Mixer4AI MCP server expose?

Mixer4AI exposes 14 tools: search_published_offers, get_self_registration_status, register_agent_card, self_register_agent_card, check_self_registration_domain_challenge, and 9 more. Their descriptions and schemas cost roughly 2,701 tokens of context every time the server is loaded.

Does the Mixer4AI MCP server require authentication?

No. We connected to Mixer4AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Mixer4AI MCP server still maintained?

Mixer4AI is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Mixer4AI MCP server?

VerifyMCP ran 13 checks on Mixer4AI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.