This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 16, 2026 · visdenda.com
40tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://visdenda.com/v1/mcp
Skill page: https://www.mcpbundles.com/skills/visdenda-mcp-ddc5d6cc1e
Explore capabilities (40)
read 23
write 2
Showing 25 of 40
Showing 25 of 40 tools from the public preview. Connect the server to inspect the full live tool list.
Get18
Other capabilities7
Check one URL, or verify a fix against the last audit
read
audit_url
Without siteId: a read-only three-check probe of any public URL (favicon, canonical self-reference with hreflang x-default, BreadcrumbList). With siteId: run that site's full applicable rule set on this one page and diff every rule against the site's most recent completed audit run, reporting fixed / regressed / still failing — use this after you change a page. Read-only on both paths: it never writes an audit run or flips finding state, so a full audit is still what commits a resolution. Requir
Description may be truncated on the public preview.
Check one URL, or verify a fix against the last audit — Without siteId: a read-only three-check probe of any public URL (favicon, canonical self-reference with hreflang x-default, BreadcrumbList). With siteId: run that site's full applicable rule set on this one page and diff every rule against the site's most recent completed audit run, reporting fixed / regressed / still failing — use this after you change a page. Read-only on both paths: it never writes an audit run or flips finding state, so a full audit is still what commits a resolution. Requir
Recent Google Search updates — Recent P0/P1 Google Search updates and how many active audit rules each one links to. This is change outside the site and outside its source code — use it to explain why a rule matters now. Requires the radar:read scope.
List sites under this key — Start here: the sites this key can read, with verification state and the latest audit run. Requires the audit:read scope.
Summarize all sites under this key — Every site this key can read with latest run status, open finding count and totals, attention-first. Use it to pick which site to inspect next. Requires the audit:read scope.
Project status at a glance — Start here for one site's state: latest and previous audit runs with coverage, the delta since the previous run (new failures, resolved, pages added/removed), highest-priority fixes with severity and sample URLs, recent P0/P1 radar updates that hit its failing rules, uptime/CWV/watchdog signals, and the archived GSC month. The delta comes from stored audit history, which no source repo can produce. Read-only, no live GSC or page fetch. Requires the audit:read scope.
Read audit findings — Read findings for a site (latest run by default, or one run by id) with server-side filters: status, severity, rule and page substring. Returns rule, page, status, detail, evidence key plus facet counts so the caller can see what else is in the run. Rule text is returned as authored. Requires the audit:read scope.
Prioritize what to fix
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Visdenda is an MCP server at visdenda.com. MCPBundles discovered 40 tools on the live endpoint.
How do I connect Visdenda to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does Visdenda provide?
Operate this server?
Request removal if you do not want Visdenda listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Visdenda?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
— Rank what to fix from a site's latest run: failing rules grouped by page count, each linked to a P0/P1 radar update when the rule came from one. No writes, no network. Requires the audit:read scope.
Read recent audit runs — A site's recent audit runs, newest first, with status, summary, coverage quality and trigger. Use it to pick a run, or to judge improvement across runs. Requires the audit:read scope.
Read audit trends — Pass rate and added/fixed/regressed across a site's last N runs — the 'is it getting better' view rather than just the latest run. Needs at least two completed runs. Requires the audit:read scope.
Read the open backlog — The open finding backlog with age buckets, resolutions in the last 30 days and the rules with the most open items — use it to judge whether the backlog is ageing or being cleared. Needs more than one completed run to mean anything. Requires the audit:read scope.
Read the site health score — The site's 0–100 health score with four explainable penalties (open findings, backlog age, audit freshness, coverage) and the raw inputs behind them. Computed from audit history, so a source repo cannot produce it; null means no completed audit yet. Requires the audit:read scope.
Compare two audit runs — Use this after you deploy a fix: diff two committed runs of the same site — added/fixed/regressed, per-run pass/fail totals, truncated change list. Both runs must already exist; for a single page that has not been re-audited, use audit_url with siteId instead (read-only, no audit run consumed). Requires the audit:read scope.
Explain one finding — Explain a single finding: the page, status and detail, plus the rule's title, category, documentation link and verification guidance as stored. Requires the audit:read scope.
Check one update against a site — Given a radar update and a site, return the active rules linked to that update plus that site's latest-run findings for those rules. It joins an external Google change to your own failures — neither side alone tells you whether the update hits you. Requires the audit:read scope.
Read the site tech fingerprint — Technology fingerprint (framework, router, rendering, i18n lib, hosting signals), from the 24h cache when fresh. If you can read the site's source repository, prefer the repo — it is authoritative and richer; use this for a site whose code you do not have. Requires the audit:read scope.
Read i18n maturity — Internationalization maturity level and gaps, derived from the tech fingerprint. If you can read the source repository, prefer the repo; use this for a site whose code you do not have. Requires the audit:read scope.
Read the GSC monthly archive — One month of Google Search Console data (clicks, impressions, CTR, position) from the stored archive; falls back to a live read with the key owner's credentials (paid plans only, daily-capped). Search performance exists only in GSC — it cannot be derived from the site or its code. Requires the audit:read scope.
GSC traffic overview — Clicks, impressions, CTR and average position for the last 7, 28 or 90 days with previous-period deltas. Live GSC data (final data lags ~3 days); paid plans, counts against the daily live-read cap. This is the only source for search performance — nothing in the site's code or HTML reveals it. Requires the audit:read scope.
Top GSC queries — Top search queries by clicks for the last 7, 28 or 90 days with impressions, CTR, position and previous-period deltas. Live GSC read on paid plans, daily-capped; not derivable from the site itself. Requires the audit:read scope.
Top GSC pages — Top landing pages by clicks for the last 7, 28 or 90 days with impressions, CTR, position and previous-period deltas. Live GSC read on paid plans, daily-capped; not derivable from the site itself. Requires the audit:read scope.
Rank fix opportunities — Rank pages worth fixing: latest-run fails weighted by archived-month clicks. Empty means no evidence, not no problems. The weighting needs GSC clicks, so this ranking cannot be reproduced from the repo. Requires the audit:read scope.
AI crawler and referral activity — Read what AI crawlers and AI referrals actually did on a site in the last 7, 28 or 30 days: hits by agent, previous-window delta, markdown negotiation, machine-file reads, AI referral hosts, and robots violations. Use this when the user asks whether AI bots visit, whether they are blocked, or whether AI sends traffic. Returns na with a reason when the site has no probe data; missing data is never treated as zero. Read-only. Requires the audit:read scope.
AI Overview presence and citations — Read the latest AI Overview check for the site's tracked queries: whether an AI Overview appeared and whether it cited the user's domain. Paid plans also get up to 90 days of sampled presence for up to 10 queries. Use this when the user asks whether they appear in Google AI Overviews or whether AI answers cite them. An empty trend means not sampled, not absent. Read-only. Requires the audit:read scope.
Run an audit now — Start a full audit for one verified site owned by this API key. This is the call that commits finding state (resolved / regressed) and feeds trends and health, and it consumes one audit run from the account's quota. Requires the audits:write scope. Writes need confirm:true plus a unique idempotencyKey; without confirm:true it returns a dry-run preview and changes nothing. Reusing the same idempotencyKey within 24h returns the first result.
Import sitemap pages — Fetch the site's sitemap and add new pages to its audit list, truncated at the plan's auditUrls limit. Requires the audits:write scope. Writes need confirm:true plus a unique idempotencyKey; without confirm:true the call returns a dry-run preview and changes nothing.
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 40 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Visdenda require?
Visdenda may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.