Tenable Docs MCP
OCI · GHCR.IO/LANZ/TENABLE-DOCS-MCP · 2 COMPONENTS
Cited answers from Tenable's product documentation, in every product, version, and language
Available components
Last scanned (23 hours ago)
Scores higher than 91% of OCI servers
Category Code Search and Documentation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to lanz/tenable-docs-mcp). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3161 tokens (~166/item across 19 items; 18 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 0
- Package version: 1.0.0 → 1.0.1 functional
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 51
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed oci/ghcr.io/lanz/tenable-docs-mcp@1.0.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | lanz/tenable-docs-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/lanz/tenable-docs-mcp/.github/workflows/release.yml@refs/tags/v1.0.1 |
| Rekor log index | 3892497971 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:f24966d7389f12659117e576faad12e9b3585358ab4540f71eef6a89f757e123 |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
browse_guide ~147
Show a guide's table of contents, with links, to see what it covers or find a page by its place. Give the guide's path (nessus, security-center/director, nessus/10_8) or any page's URL.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | how many levels of the table of contents to show, from 1 to 10 (default 3) |
| guide | string | yes | a guide's path (nessus, security-center/director, nessus/10_8) or the URL of any page in it |
| language | string | – | the site code of the guide's language, when guide is a path (default en) |
| Name | Type | Req | Description |
|---|---|---|---|
| entries | null|array | yes | the table of contents in reading order, each entry with its depth |
| guide | string | yes | – |
| language | string | yes | – |
| name | string | yes | – |
| root_url | string | yes | – |
| total | integer | yes | every entry in the table of contents, shown or not |
No examples provided.
compare_versions ~283
Compare a page, or a setting, between two versions of an on-premises product (Security Center, Nessus, OT Security, Identity Exposure on-premises, and others with versioned guides). For a page, it lists the sections that changed, were added, or were removed, with the lines that differ: a line that changed is shown once, with [-removed words-] and {+added words+}. For a setting, it shows how its default, values, and description changed. Give url (a page in any version) or setting, and from_version; to_version defaults to the current version. Each section shows its first few changed lines; give heading as well for every changed line in one section. Cite both urls.
| Name | Type | Req | Description |
|---|---|---|---|
| from_version | string | yes | the earlier version, such as 6.5 |
| heading | string | – | with url: only the section with this heading, with every line that changed rather than the first few |
| product | string | – | the setting's product, by any of its names (with setting) |
| setting | string | – | a setting's name, to compare instead of a page |
| to_version | string | – | the later version (default: the current one) |
| url | string | – | a docs page, in any version: it's compared with the same page in the other version |
| Name | Type | Req | Description |
|---|---|---|---|
| from | object | yes | – |
| message | string | – | – |
| sections | null|array | – | the sections that differ, in the later version's order, then the removed ones |
| setting | string | – | – |
| setting_changes | null|array | – | how the setting's row differs |
| to | object | yes | – |
| unchanged_sections | integer | – | – |
| versions_available | null|array | – | the versions the docs have, for choosing others |
No examples provided.
define_term ~93
Define a Tenable term or abbreviation from the docs' glossaries, and say what a product name refers to, including retired names (Tenable.io is now Tenable Vulnerability Management).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | also look in this language's glossary (default: English only) |
| term | string | yes | a term, abbreviation, or product name, such as VPR, plugin family, or Tenable.io |
| Name | Type | Req | Description |
|---|---|---|---|
| definitions | null|array | yes | – |
| message | string | – | – |
| product | null|object | – | set when the term is a product's name, current or retired |
| synonyms | null|array | – | – |
| term | string | yes | – |
No examples provided.
find_setting ~161
Look up a product setting: its default, what it does, the values it takes, and whether it's required, from the settings tables in the docs. Search by the setting's name or what it does, with the product if known. Cite the url it returns.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | how many settings to return, from 1 to 20 (default 5) |
| product | string | – | only this product, by any of its names |
| query | string | yes | the setting's name or what it does, such as max simultaneous hosts or session timeout, with the product if known |
| version | string | – | the product version, such as 6.3 (default: the one the query names, or the current one) |
| Name | Type | Req | Description |
|---|---|---|---|
| for_product | string | – | for Tenable Core, the product it runs that the filter applied |
| message | string | – | – |
| notes | null|array | – | – |
| product | string | – | the product filter applied |
| settings | null|array | yes | – |
No examples provided.
index_status ~52
Show this server's version and what its documentation index holds: each language's current and older-version pages, and when they were indexed. Use it first when a search returns nothing, to check whether the index is built.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| go_version | string | yes | – |
| index | object | yes | – |
| note | string | – | – |
| server | string | yes | – |
| update | null|object | – | set when a newer release of this server is available: tell the user, with its link |
| updates | object | yes | – |
| version | string | yes | – |
No examples provided.
list_products ~39
List the products and languages the documentation index covers, with page counts, each product's English guides and older versions, and when each language was last indexed.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| languages | null|array | yes | – |
| products | null|array | yes | – |
No examples provided.
open_feedback_form ~227
Show the user the docs feedback form for a page, the same form as at the bottom of each docs page, so they can tell Tenable's documentation team what they think of it. The feedback is the user's, not yours: use this only when the user asks to give feedback, and never to submit your own review of a page. You choose the page and whether the user found it helpful, from what they said. The user writes the comment, and an email if they want a reply, in the form, which their client shows them and you don't see; there's no argument for a comment, by design. If you noticed problems on the page, mention them to the user before opening the form; they decide what to write. Feedback is for the documentation, not for Tenable products. If the user's client can't show forms, nothing is sent; give them the page's link to use its feedback form.
| Name | Type | Req | Description |
|---|---|---|---|
| helpful | boolean | yes | whether the user found the page helpful, from what they said |
| url | string | yes | the docs page the feedback is about |
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | – |
| sent | string | – | exactly what was sent: the user's own feedback, as they wrote it in the form |
| status | string | yes | sent, declined, cancelled, no_form (this client can't show the feedback form), or rate_limited (too many sent recently); nothing is sent unless sent |
| written_by | string | – | who wrote the comment: always the user, in the form |
No examples provided.
outline ~116
List a page's headings, with links to each and their word counts, or a guide's pages from its table of contents. Use it to find the right section of a long page, or to see what a guide covers.
| Name | Type | Req | Description |
|---|---|---|---|
| guide | string | – | a guide's path, such as nessus or security-center/6_8, for its pages; give url or guide |
| language | string | – | the site code of the guide's language (default en) |
| url | string | – | a page, for its headings |
| Name | Type | Req | Description |
|---|---|---|---|
| items | null|array | yes | – |
| title | string | yes | – |
| url | string | – | – |
| words | integer | yes | the total words |
No examples provided.
read_doc ~168
Read a documentation section or page as Markdown, with a header saying where it is, the roles it needs, and when it changed. Pass a link from search_docs: with an #anchor it reads that section, without one the whole page. Long content comes in parts; previous and next point to the neighboring sections. Cite the url it returns.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | the most characters to return in one part, from 1000 to 30000 (default 8000) |
| part | integer | – | which part of a long section or page to read, from 1 (default 1) |
| url | string | yes | a docs page or section link, as search_docs returns it; a link with #anchor reads that section, one without reads the whole page |
| Name | Type | Req | Description |
|---|---|---|---|
| current_url | string | – | the current version of this page, when this one is older |
| english_url | string | – | the current English page, to cite for a translation or an older version |
| guide_type | string | – | – |
| heading | string | – | the section read; empty for a whole page |
| language | string | yes | – |
| last_modified | string | – | – |
| location | string | yes | where the page is in its guide's table of contents |
| markdown | string | yes | the content, starting with a context header |
| next | null|object | – | the section or page after this one |
| other_languages | null|array | – | – |
| other_versions | null|array | – | – |
| part | integer | yes | – |
| parts | integer | yes | how many parts the content has; read the next with part |
| previous | null|object | – | the section or page before this one |
| product | string | – | – |
| required_roles | null|array | – | – |
| title | string | yes | – |
| url | string | yes | the link to cite for what was read |
| version | string | – | the guide version; empty for the current one |
No examples provided.
refresh_index ~127
Update pages in the documentation index from the live docs sites: given pages, or every page of a guide and its table of contents. Unchanged pages cost little; pages the sites no longer publish are removed. Use it when a page seems out of date.
| Name | Type | Req | Description |
|---|---|---|---|
| guide | string | – | a guide's path (nessus, security-center/6_8), to refresh its table of contents and every page; give urls or guide |
| language | string | – | the guide's language (default en) |
| urls | null|array | – | pages to refresh, at most 500 |
| Name | Type | Req | Description |
|---|---|---|---|
| checked | integer | yes | – |
| failed | null|array | – | – |
| removed | integer | yes | – |
| skipped | integer | yes | – |
| toc_updated | boolean | – | – |
| unchanged | integer | yes | – |
| updated | integer | yes | – |
No examples provided.
related_pages ~67
Show what's around a docs page: its place in the table of contents (parent, previous, next), the pages it links to and that link to it, same-titled pages in other products, and the page in other languages and versions.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | a docs page |
| Name | Type | Req | Description |
|---|---|---|---|
| current_url | string | – | the current version of this page, when this one is older |
| english_url | string | – | the current English page, to cite for a translation or an older version |
| links_in | null|array | – | docs pages that link to this page |
| links_out | null|array | – | docs pages this page links to |
| next | null|object | – | – |
| other_languages | null|array | – | – |
| other_versions | null|array | – | – |
| parent | null|object | – | the entry above this page in the table of contents |
| previous | null|object | – | – |
| product | string | – | – |
| same_title | null|array | – | pages with the same title in other products or guides |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
release_notes ~206
List release-note entries, newest first, filtered by product, dates, version, and words they contain. Use it for what's new, when something changed, or which release fixed an issue.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | return each entry's full text instead of a summary |
| language | string | – | the release notes' language (default en) |
| limit | integer | – | how many entries to return, from 1 to 50 (default 10) |
| product | string | – | – |
| query | string | – | words the entries must contain, such as a feature or a fixed issue |
| since | string | – | only entries on or after this date, as YYYY-MM-DD, YYYY-MM, or YYYY |
| until | string | – | only entries on or before this date, as YYYY-MM-DD, YYYY-MM, or YYYY |
| version | string | – | only entries for this version or its patch releases (10.8 matches 10.8.1) |
| Name | Type | Req | Description |
|---|---|---|---|
| entries | null|array | yes | newest first |
| language | string | yes | – |
| message | string | – | – |
| product | string | – | – |
No examples provided.
report_gap ~198
Record a question the docs didn't answer, in a file on this computer that only the user can read. Then, if the user's client can show forms, the user is offered a form to send it to Tenable's documentation team: the question filled in for them to edit, with optional details and email. Nothing is sent unless they accept. Pass url, the docs page that came closest to answering, if any. The user can also summarize the file with `tenable-docs-mcp gaps export`. Leave out personal and customer details.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| note | string | – | what was searched and found, such as only the 6.3 docs cover it; kept on this computer only |
| product | string | – | – |
| question | string | yes | the user's question, as asked, without personal or customer details |
| url | string | – | the docs page that came closest to answering, if any |
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | – |
| recorded | boolean | yes | – |
| sent | string | – | exactly what was sent, as the user approved it in the form |
| sent_to_tenable | string | – | sent, declined, cancelled, no_form (this client can't show forms, so it wasn't offered), or rate_limited (too many sent recently, so it wasn't offered); empty when sending isn't available |
| total | integer | yes | how many questions are recorded |
| written_by | string | – | who approved what was sent: always the user, in the form |
No examples provided.
required_role ~97
Find who can do a task: the user roles and permissions the docs say it needs, by product. Describe the task in the user's words. When the docs don't state a role, it says so and lists the closest pages.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| product | string | – | – |
| task | string | yes | what the user wants to do, such as create a scan or add users |
| version | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| answers | null|array | yes | pages about the task that state the roles it needs, best first |
| closest_pages_without_roles | null|array | – | when no page states a role: the pages that best match the task |
| message | string | – | – |
| notes | null|array | – | – |
No examples provided.
requirements ~177
List a product's requirements from the requirements tables in the docs: ports and protocols, hardware, operating systems, browsers, and dependencies. Give the product and the kind, or a question such as "Nessus ports" or "Security Center hardware for 10,000 hosts".
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | ports, hardware, operating-systems, browsers, dependencies, or other (default: all, or what the query asks about) |
| limit | integer | – | how many rows to return, from 1 to 100 (default 30) |
| product | string | – | the product, by any of its names |
| query | string | – | words to look for, such as 443, RHEL, or 10,000 hosts; the product and kind can be named here too |
| version | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| for_product | string | – | for Tenable Core, the product it runs that the filter applied |
| kind | string | – | – |
| message | string | – | – |
| notes | null|array | – | – |
| product | string | – | – |
| requirements | null|array | yes | – |
No examples provided.
search_docs ~383
Search Tenable's product documentation (docs.tenable.com and its translated sites) for sections that answer a question. Returns ranked sections with links to cite, snippets, product, version, language, and the roles a task needs. Pass the user's question in their words and language; retired product names such as Tenable.io and Tenable.sc work. Read a result in full with read_doc before relying on it. Use the Tenable Developer Portal MCP for API questions.
| Name | Type | Req | Description |
|---|---|---|---|
| guide | string | – | only this guide, by its path on the site, such as nessus or security-center/director (see browse_guide and list_products) |
| guide_type | string | – | only this guide type: User Guide, API Guide, Reference Guide, Integration Guide, Release Notes, Best Practices Guide, Migration Guide, Cyber Exposure Study, or Whitepaper |
| language | string | – | the docs' language, as a site code (en, jp, zh-cn, zh-tw, kr, fr, de, es) or language tag (ja, ko); default: the query's language |
| limit | integer | – | how many results to return, from 1 to 25 (default 8) |
| product | string | – | only this product, by any of its names (retired ones such as Tenable.io and Tenable.sc work too) |
| query | string | yes | what to look for, in the user's words and language: a task, setting, message, or feature, with the product and version if known |
| release_notes | boolean | – | only release notes |
| required_role | string | – | only pages that say they need this role or permission, such as Administrator |
| version | string | – | only this product version, such as 6.3 (default: the version the query names, or the current one) |
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | yes | the docs' language searched |
| message | string | – | – |
| notes | null|array | – | – |
| other_products | null|array | – | products that do have matches, when the product filter excluded them |
| relaxed | boolean | – | set when no section had every word of the query |
| requested_language | string | yes | the language asked for or detected; it differs from language when the results fell back to English |
| results | null|array | yes | – |
| suggestions | null|array | – | other spellings of the query to try, when nothing matched |
| version | string | – | the product version searched; empty for current versions |
No examples provided.
verify_citations ~143
Check the docs links in an answer or a draft before relying on it: that each page exists and its anchor is on the page, which links go to older versions or translations (with the current English page to cite instead), and suggestions for broken links. Run it on an answer before sending it.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | the page the text will be published as, to resolve relative links (for a draft topic) |
| check_live | boolean | – | also check the live docs sites, for anchors that aren't headings and pages the index doesn't have |
| text | string | yes | the answer or draft to check, in Markdown, HTML, or plain text |
| Name | Type | Req | Description |
|---|---|---|---|
| links | null|array | yes | – |
| problems | integer | yes | – |
| skipped | object | yes | – |
| warnings | integer | yes | older versions, translations, anchors that aren't headings, moved pages, and links the index can't check |
No examples provided.
whats_changed ~213
List the docs pages that were added, updated, or removed since a date, newest first, with the sections each update changed and the lines that differ. Narrow it by product or guide. The index keeps a year of changes from the time it was first built; for earlier dates, it lists the pages the sitemap dates in the period, without what changed. For a product's release history, use release_notes.
| Name | Type | Req | Description |
|---|---|---|---|
| guide | string | – | only this guide, by its path, such as nessus or security-center/6_8 |
| language | string | – | the docs' language, as a site code (default en) |
| limit | integer | – | how many pages to list, from 1 to 100 (default 20) |
| product | string | – | only this product, by any of its names |
| since | string | yes | the start of the period: a date (2026-10-01 or 2026-10), or a number of days back (30d) |
| Name | Type | Req | Description |
|---|---|---|---|
| changes | null|array | yes | newest first |
| dated | null|array | – | for the part of the period before the history begins: pages the sitemap dates in it, without what changed |
| history_since | string | – | when this index's change history begins; it only knows changes from then on |
| message | string | – | – |
| more | boolean | – | there are more; narrow the period, product, or guide, or raise limit |
| since | string | yes | – |
No examples provided.
How do I install the Tenable Docs MCP server?
Tenable Docs MCP runs locally as a container image, launched with docker run --rm -i -e TDM_SITES -e TDM_INDEX_URL ghcr.io/lanz/tenable-docs-mcp:1.0.1. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/lanz/tenable-docs-mcp
claude mcp add lanz-tenable-docs-mcp -- docker run --rm -i -e TDM_SITES -e TDM_INDEX_URL ghcr.io/lanz/tenable-docs-mcp:1.0.1
This image reads TDM_SITES and TDM_INDEX_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.
What is the Tenable Docs MCP server?
Tenable Docs MCP is listed in the public MCP registry as io.github.lanz/tenable-docs-mcp. Cited answers from Tenable's product documentation, in every product, version, and language. This page covers its container image (ghcr.io/lanz/tenable-docs-mcp).
Is the Tenable Docs MCP server safe to use?
Tenable Docs MCP scores 55 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tenable Docs MCP server expose?
Tenable Docs MCP exposes 18 tools: browse_guide, compare_versions, define_term, find_setting, index_status, and 13 more. Their descriptions and schemas cost roughly 2,897 tokens of context every time the server is loaded.
Is the Tenable Docs MCP server still maintained?
Tenable Docs MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Tenable Docs MCP server under?
Tenable Docs MCP declares the GPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Tenable Docs MCP server?
VerifyMCP ran 12 checks on Tenable Docs MCP, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Tenable Docs MCP: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.