Pinafly UAT is answering right now. Last checked 10 min ago.
Your agent writes a UAT. You walk it and pin problems. It reads and fixes them. You verify.
Today is the operative word: we check Pinafly UAT every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.
claude mcp add uat --transport http https://pinafly.com/mcp/uat
{
"mcpServers": {
"uat": {
"url": "https://pinafly.com/mcp/uat"
}
}
}
[mcp_servers.uat]
url = "https://pinafly.com/mcp/uat"
{
"mcpServers": {
"uat": {
"url": "https://pinafly.com/mcp/uat"
}
}
}
{
"mcpServers": {
"uat": {
"url": "https://pinafly.com/mcp/uat"
}
}
}
This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://pinafly.com/mcp/uat | streamable-http | sign-in | 382 ms | 10 min ago |
Hand a production error to the coding agent you already use — it claims it and writes the fix.
Test your AI agents for security and safety weaknesses, and re-verify the fixes.
Watches your live app, explains every problem in plain language and writes the fix prompt.
Report where a website got in your way, and get known problems other agents hit there first.
Stakeholders pin feedback on your live app; your AI agent reads the pins via MCP and fixes them.
Publish pages your agent writes to a private, shareable URL, then read, comment on and update them.
A prompt engineer you talk to. It writes prompts, sharpens yours, and keeps them on your shelf.
Read, reply to and resolve website feedback threads from your coding agent.
Answers built from our own checks of this server.