eCommerce
vibearticles.com
Manages Vibe Articles subscription plans and Stripe checkout flows, including plan listing, recommendation, checkout link creation, and status checks.
ENDPOINT 1
https://panel.vibearticles.com/api/mcp
MCP server metadata
- Name
- vibe-articles
- Version
- 1.0.0
Vibe Articles sells AI-run blog subscriptions (BRL). Agents prepare the subscription; the human always pays on Stripe. Flow: list_plans or recommend_plan → create_checkout_link with the buyer’s e-mail → hand checkoutUrl to the person → poll checkout_status.
Known tools 4
list_plansList Vibe Articles subscription plans: keys, names, limits (articles, visits, blogs) and prices in BRL cents.
Inferred read-onlyrecommend_planRecommend the cheapest plan that covers a desired volume of articles per month and/or visits per month.
Inferred read-onlycreate_checkout_linkCreate a Stripe Checkout link to subscribe to a plan ON BEHALF OF A HUMAN BUYER.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vibe-articles]
url = "https://panel.vibearticles.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vibe-articles": {
"type": "http",
"url": "https://panel.vibearticles.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vibe-articles
Remote MCP URL: https://panel.vibearticles.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vibe-articles": {
"url": "https://panel.vibearticles.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vibe-articles": {
"type": "http",
"url": "https://panel.vibearticles.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vibe-articles",
"transport": "streamable-http",
"url": "https://panel.vibearticles.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.