shelf-smoke — url smoke / headless QA
co.kymac.shelfPublished by shelf.kymac.coOfficial publisherv0.3.0Updated Oct 24, 2026
url smoke / headless QA: desktop+phone → pass/fail JSON. MCP shelf.kymac.co
Overview
Runs URL smoke and headless QA checks across desktop and phone viewports, returning pass/fail JSON.
- What you can do
- This remote MCP server performs smoke testing and headless quality checks on web URLs. According to the registry description, it tests a page across desktop and phone viewports and returns pass/fail results as JSON. No individual tools are listed in the manifest, so the exact tool names and parameters are not documented here.
- When to use it
- Worth adding when an assistant needs to verify that a web page loads and behaves correctly on both desktop and mobile before or after a deployment. Useful for quick smoke checks in a QA or release workflow rather than deep functional testing.
- Requirements
- A remote streamable HTTP endpoint at shelf.kymac.co; nothing is installed locally. Authentication is required: an Authorization header carrying a Bearer token, or an X-API-Key header as an alternative. Keys are minted via a POST /keys endpoint, and the environment variable SHELF_SMOKE_API_KEY is also accepted for stdio use. Network access to the endpoint is needed.
Installation
In SourceWeft
- Open shelf-smoke — url smoke / headless QA in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/co.kymac.shelf%2Fshelf-smoke/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"shelf-smoke-url-smoke-headless-qa": {
"type": "http",
"url": "https://shelf.kymac.co/mcp"
}
}
}Tools
0Version history
2- v0.3.0LatestSep 17, 2026
- v0.1.3Sep 17, 2026
Score
28% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.