Vibeking
com.vibekingdevelopmentPublished by vibekingdevelopment.comOfficial publisherv0.3.0Updated Oct 24, 2026
Website monitoring for SEO, AI visibility and ads: issues, fix tasks, rankings, reports and fixes.
Overview
A remote MCP server for website monitoring across SEO, AI visibility and ads, exposing issues, fix tasks, rankings and reports.
- What you can do
- Vibeking is a hosted MCP endpoint that gives an assistant access to website monitoring data covering SEO, AI visibility and advertising. According to its registry description, it surfaces issues, fix tasks, rankings, reports and fixes. No individual tools are listed in the manifest, so the exact operations available are not documented here.
- When to use it
- Consider it when an assistant should read or act on website monitoring results — SEO problems, visibility in AI answers, ad performance, ranking changes — and turn them into fix tasks or reports. It is less relevant if you only need general web search or browsing.
- Requirements
- It runs as a remote streamable HTTP endpoint at the provider's site, so no local runtime or package install is needed. The manifest declares no authentication, no environment variables and no headers, but the provider may still require an account or credentials in practice.
Installation
In SourceWeft
- Open Vibeking in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/com.vibekingdevelopment%2Fvibeking/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. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"vibeking": {
"type": "http",
"url": "https://vibekingdevelopment.com/mcp"
}
}
}Tools
0Version history
1- v0.3.0LatestSep 27, 2026
Score
67% 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
- 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
- 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.