Real sources.
Agent-ready answers.
Give your assistant access to the published VibeAlt catalogue. Every result keeps the AI-build evidence, replacement scope and limitations together.
Connect with MCP.
Use the Streamable HTTP endpoint below in an MCP-compatible client. This public read-only server requires no account or API key. Client support and connector setup vary.
https://vibealt.com/mcp/search_alternatives— search an incumbent name or workflow; optionally require documented original attribution.get_app— retrieve one published app by slug.get_software— retrieve a replacement guide and its alternatives.
The server uses the official MCP SDK, supports current request-envelope transport and stateless legacy Streamable HTTP. It accepts JSON-RPC over POST; it does not offer an old SSE-only endpoint.
Use the public API.
GET https://vibealt.com/api/v1/catalog.json
GET https://vibealt.com/api/v1/search/?q=Postman&limit=5OpenAPI description · llms.txt · Full Markdown catalogue
What agents can access.
Published editorial app records, public software criteria, original AI-build source links, documented capabilities and switching caveats. Accounts, private submissions, operator tools, comments and session data are excluded. There are no write tools, network-fetch tools or code-execution tools. Requests are size-bounded and the dynamic API is rate limited to 120 requests per minute per network address.
How to cite a result.
Link the VibeAlt profile and the primary evidence URL. Preserve the difference between a maker claim and a documented AI-attributed development record. Unknown facts stay unknown; do not turn a narrow replacement workflow into a claim of full feature parity. See our evidence method.