A
licenseA
qualityD
maintenanceSimulates real users navigating your app and delivers qualitative UX feedback, including persona-driven testing, auto-friction detection, and WCAG accessibility audits.
14
30
1
MIT
Mimiq - Synthetic User Testing
Server Details
Your agent tests pages, copy, and flows on simulated users while you build.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- victorgulchenko/mimiq-mcp
- GitHub Stars
- 1
- Server Listing
- Mimiq MCP
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
6 tool updates
- Changed
mimiq.ask_audience4 fields changed- added
Input schema / properties / audience / maxLengthAdded value: +500 - changed
Input schema / properties / concurrency / descriptionPrevious value: -"Parallel survey workers (default 6)."New value: +"Number of parallel survey workers (default 6). Higher values return results faster but may hit rate limits." - added
Input schema / properties / context / maxLengthAdded value: +500 - added
Input schema / properties / timeout_secondsAdded value: +{ + "default": 300, + "maximum": 900, + "minimum": 30, + "type": "integer" +}
- Changed
mimiq.test_component4 fields changed- added
Input schema / properties / audience / maxLengthAdded value: +500 - added
Input schema / properties / component_html / maxLengthAdded value: +50000 - added
Input schema / properties / component_text / maxLengthAdded value: +20000 - added
Input schema / properties / goal / maxLengthAdded value: +500
- Changed
mimiq.test_copy4 fields changed- changed
Input schema / properties / audience / descriptionPrevious value: -"Target audience. E.g. \"developers evaluating CI/CD tools\" or \"e-commerce shoppers\"."New value: +"Target audience. E.g. \"developers evaluating CI/CD tools\". If omitted, defaults to \"likely audience for this content\"." - added
Input schema / properties / audience / maxLengthAdded value: +500 - added
Input schema / properties / variant_a / maxLengthAdded value: +20000 - added
Input schema / properties / variant_b / maxLengthAdded value: +20000
- Changed
mimiq.test_flow6 fields changed- changed
Input schema / properties / audience / descriptionPrevious value: -"Target audience description. E.g. \"small business owners looking for accounting software\"."New value: +"Who should test this page. Natural language, e.g. \"startup founders in SF\" or \"parents shopping for kids toys\". If omitted, Mimiq auto-detects the likely audience from page content." - added
Input schema / properties / audience / maxLengthAdded value: +500 - removed
Input schema / properties / bridge_idRemoved value: -{ - "description": "Deprecated. Use cloudflared tunnel directly instead.", - "type": "string" -} - changed
Input schema / properties / goal / descriptionPrevious value: -"What success looks like, e.g. \"complete the signup and reach the dashboard\"."New value: +"What success looks like, e.g. \"complete the signup and reach the dashboard\". Providing a goal helps personas evaluate the page against a specific conversion objective." - added
Input schema / properties / goal / maxLengthAdded value: +500 - added
Input schema / properties / url / maxLengthAdded value: +2000
- Changed
mimiq.test_page6 fields changed- changed
Input schema / properties / audience / descriptionPrevious value: -"Who should test this page. Natural language, e.g. \"startup founders in SF\" or \"parents shopping for kids toys\". If omitted, auto-detects from page content."New value: +"Who should test this page. Natural language, e.g. \"startup founders in SF\" or \"parents shopping for kids toys\". If omitted, Mimiq auto-detects the likely audience from page content." - added
Input schema / properties / audience / maxLengthAdded value: +500 - removed
Input schema / properties / bridge_idRemoved value: -{ - "description": "Deprecated. Use cloudflared tunnel directly instead.", - "type": "string" -} - changed
Input schema / properties / goal / descriptionPrevious value: -"What the page is trying to achieve, e.g. \"get visitors to sign up for the waitlist\"."New value: +"What the page is trying to achieve, e.g. \"get visitors to sign up for the waitlist\". Providing a goal helps personas evaluate the page against a specific conversion objective." - added
Input schema / properties / goal / maxLengthAdded value: +500 - added
Input schema / properties / url / maxLengthAdded value: +2000
- Changed
mimiq.test_text4 fields changed- changed
Input schema / properties / audience / descriptionPrevious value: -"Target audience for the content."New value: +"Target audience. E.g. \"developers evaluating CI/CD tools\". If omitted, defaults to \"likely audience for this content\"." - added
Input schema / properties / audience / maxLengthAdded value: +500 - added
Input schema / properties / goal / maxLengthAdded value: +500 - added
Input schema / properties / text / maxLengthAdded value: +20000
6 tool updates
- First observed
mimiq.ask_audience - First observed
mimiq.test_component - First observed
mimiq.test_copy - First observed
mimiq.test_flow - First observed
mimiq.test_page - First observed
mimiq.test_text
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Browser-based QA for AI-built software. Test pages with real browsers via agents.
Deploy AI user personas to validate user journeys at scale. Find UX friction before real users do.
- ishOAuthio.ishlabs
Simulated people experience what you are making and report what they noticed and felt.
- RapidlyOAuthco.rapidly
Test the idea before you build it. Rapidly works inside your AI agent.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceDeploys AI user personas to validate user journeys at scale, surfacing UX friction before real users encounter it.1MIT
- AlicenseAqualityCmaintenanceAI-native browser testing, directly from your coding agent.3MIT
- FlicenseNot gradedqualityDmaintenanceBrowser-based QA testing for AI-built software. Agents open real browsers (via Selenium), navigate pages, fill forms, click buttons, and report findings. Two modes: targeted tests (30-90s) and full-site discovery scans (3-15min).-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.5/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: ask_audience is for surveys with options, test_component for UI elements, test_copy for written content variants, test_flow for multi-step interactions, test_page for full web pages, and test_text for general text content. The descriptions explicitly differentiate use cases, such as test_page for landing pages versus test_flow for complex journeys, eliminating ambiguity.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with snake_case, starting with 'test_' or 'ask_' followed by a descriptive noun (e.g., test_page, ask_audience). This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
Tool Count5/5
With 6 tools, the server is well-scoped for synthetic user testing, covering key areas like surveys, UI components, copy, flows, pages, and text. Each tool serves a specific, non-overlapping function, making the count appropriate without being too sparse or bloated for the domain.
Completeness5/5
The tool set provides comprehensive coverage for synthetic user testing, including surveys, component-level feedback, copy testing, flow analysis, page evaluation, and general text reactions. There are no obvious gaps; it supports a full lifecycle from individual elements to complex interactions, ensuring agents can handle various testing scenarios without dead ends.