MCP tool reference · #473 of 563 by publishers
explain_finding
Exposed by 9 servers from 8 publishers, read from the live servers by the Serverdex check; most of them sit in Cloud & DevOps; 33.3% of them take a id parameter; the most-starred is VibeRaven (65 stars).
explain_finding(id: string, …)Parameters
share = % of the 9 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| id | string | 33.3% | 66.7% | d1: decision id, f1: finding id, or report id |
| code | string | 22.2% | 50% | A finding id from a Store Canary result, for example checkout or seo_noindex. |
| algorithm | string | 11.1% | 0% | The classical algorithm family involved (e.g. RSA, ECDH, ECDSA). |
| checkType | string | 11.1% | 100% | Check type (e.g., 'SPF', 'DMARC'). |
| details | string | 11.1% | 0% | Additional detail from check result. |
| domain | string | 11.1% | 0% | Bare domain; alone it explains the top finding |
| finding_id | string | 11.1% | 100% | Finding id exactly as shown in an audit report, for example access.blocked or llms.missing. |
| findingId | string | 11.1% | 100% | The rule/finding ID (e.g., MAN-001, SRC-003, SEC-002) |
| format | string | 11.1% | 0% | Output verbosity. |
| gap_id | string | 11.1% | 100% | The finding id as printed by VibeRaven, for example rls_disabled. |
| language | — | 11.1% | 0% | Report language as a code such as en, de, fr, es, ja or zh. Defaults to the account language (English without a key); 60 languages are supported. |
| path | string | 11.1% | 0% | — |
Source: the input schema each server returns for explain_finding, aggregated over the 9 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with explain_finding
9 of 9 · 8 publishers · 9 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes explain_finding |
|---|---|---|---|---|---|---|
| 1 | VibeRavenohad6k · Databases | ohad6k | Databases | 65 | yes | explain_finding({"gap_id":"rls_disabled"}) Use after a check returns a finding id, such as rls_disabled or env_var_drift, to understand and fix that VibeRaven 1.10.0 finding. Returns detection scope, impact, fix guidance and coverage limits quoted from viberaven.dev with source links. Unknown ids return found: false and known ids. For a raw error without a finding id, use search_guides. Limits: ex |
| 2 | quantakrypto pqc-toolsquantakrypto · Databases | quantakrypto | Databases | 16 | yes | Explain a quantakrypto finding and its post-quantum remediation. Provide a ruleId (e.g. 'forge-rsa-keygen', 'elliptic-ec', 'node-rsa', 'pem-ec-private-key') and/or an algorithm (e.g. 'RSA', 'ECDSA'). The ruleId is resolved against the core detector set, so library and config rules explain correctly. |
| 3 | BlackVeil DNS & Email Security Scannermadaburns · Security & Identity | madaburns | Security & Identity | 9 | yes | Explain a finding with impact and remediation. |
| 4 | Android Security Analyzerako2345 · Developer Tools | ako2345 | Developer Tools | 3 | yes | Explains a specific security finding by its rule ID. Returns why it is a risk, how to fix it, and false positive considerations. |
| 5 | Sighttruekaitzyy-dev · Cloud & DevOps | kaitzyy-dev | Cloud & DevOps | 1 | yes | Given a finding id, return what was measured, when, by whom, and the address it can be checked at. For an agent quoting a figure into a review. Requires a key; see https://sighttrue.com/pricing. |
| 6 | Readoutkaitzyy-dev · Cloud & DevOps | kaitzyy-dev | Cloud & DevOps | 1 | yes | Given a finding id, return what was measured, when, by whom, and the address it can be checked at. For an agent quoting a figure into a review. Requires a key; see https://sighttrue.com/pricing. |
| 7 | AISeeWhyaiseewhy · Search & Web | aiseewhy | Search & Web | — | yes | Explain a finding id (e.g. access.blocked, robots.disallowed, schema.software_no_offers) in the given language: what it means, why it matters for AI search and how to fix it. |
| 8 | CrawlCheckemmanuelorta · Search & Web | emmanuelorta | Search & Web | — | yes | Why CrawlCheck decided a finding: the rule and its revision, the exact fetches it compared (identity, status, bytes, sha256), when the condition held on the site, and a Merkle proof that the decision is inside the signed manifest. Give id (a d1: decision or f1: finding id from a report), or domain alone for its top finding, or domain plus code for a named finding. Free, no key; read-only. A findin |
| 9 | Store Canaryerikras · E-commerce & Retail | erikras | E-commerce & Retail | — | yes | Explain a finding code returned by any Store Canary tool (for example ssl_hsts or exposure_debug_log) in plain words, with a suggested fix. Makes no network requests. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.