Benchmarq
io.benchmarqPublished by benchmarq.ioOfficial publisherv1.0.0Updated Oct 24, 2026
200+ audits on AI visibility: AIO, AEO, GEO scores, site issues, competitor gaps and scan history.
Overview
A remote MCP server that gives an assistant access to Benchmarq's 200+ audits of AI visibility, including AIO, AEO and GEO scores, site issues and competitor G2
- What you can do
- Benchmarq exposes its AI visibility auditing service to an assistant over a remote streamable HTTP endpoint. According to the description, it covers more than 200 audits and reports AIO, AEO and GEO scores, site issues, competitor gaps and scan history. The manifest does not list individual tools, so the exact operations available are not documented here.
- When to use it
- Useful when you want an assistant to pull AI visibility scores, site issue findings, competitor gap analysis or past scan results into a conversation, for example while reviewing how a site performs in AI answer engines.
- Requirements
- A remote endpoint at mcp.benchmarq.io reached over streamable HTTP. Authentication is required: interactive clients use OAuth 2.1, while headless or CI access uses an API key sent in the Authorization header as a Bearer token. No local runtime or packages are needed.
Installation
In SourceWeft
- Open Benchmarq 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/io.benchmarq%2Fbenchmarq/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": {
"benchmarq": {
"type": "http",
"url": "https://mcp.benchmarq.io/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 11, 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.