Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tenable Docs MCP

MCPB · TENABLE-DOCS-MCP_1.0.1.MCPB · 2 COMPONENTS

Cited answers from Tenable's product documentation, in every product, version, and language

+4 this week 55 Trust /100

Last scanned (19 hours ago)

Scores higher than 88% of MCPB servers

Category Code Search and Documentation

Trust breakdown (7 categories)

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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).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 6 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.

What we tested

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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  • 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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).

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 →

Changelog

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 +1
    • Stability: unverified → 0.07 ▲ functional
  • 13 Nov 26 51

    First indexed and scored.

Diagnostics

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 mcpb/https://github.com/lanz/tenable-docs-mcp/releases/download/v1.0.1/tenable-docs-mcp_1.0.1.mcpb

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 mcpb
Reason Verified
Discovered via GitHub artifact attestations
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 3892490337
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:ddf1c42ba7c601689790b0c79f81edea10848117e8bbf685ac7af638a5545785

Background: How many MCP packages publish verified provenance →

MCP tools · 18 exposed · ~2,897 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
depthinteger–how many levels of the table of contents to show, from 1 to 10 (default 3)
guidestringyesa guide's path (nessus, security-center/director, nessus/10_8) or the URL of any page in it
languagestring–the site code of the guide's language, when guide is a path (default en)
NameTypeReqDescription
entriesnull|arrayyesthe table of contents in reading order, each entry with its depth
guidestringyes–
languagestringyes–
namestringyes–
root_urlstringyes–
totalintegeryesevery 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.

NameTypeReqDescription
from_versionstringyesthe earlier version, such as 6.5
headingstring–with url: only the section with this heading, with every line that changed rather than the first few
productstring–the setting's product, by any of its names (with setting)
settingstring–a setting's name, to compare instead of a page
to_versionstring–the later version (default: the current one)
urlstring–a docs page, in any version: it's compared with the same page in the other version
NameTypeReqDescription
fromobjectyes–
messagestring––
sectionsnull|array–the sections that differ, in the later version's order, then the removed ones
settingstring––
setting_changesnull|array–how the setting's row differs
toobjectyes–
unchanged_sectionsinteger––
versions_availablenull|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).

NameTypeReqDescription
languagestring–also look in this language's glossary (default: English only)
termstringyesa term, abbreviation, or product name, such as VPR, plugin family, or Tenable.io
NameTypeReqDescription
definitionsnull|arrayyes–
messagestring––
productnull|object–set when the term is a product's name, current or retired
synonymsnull|array––
termstringyes–

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.

NameTypeReqDescription
limitinteger–how many settings to return, from 1 to 20 (default 5)
productstring–only this product, by any of its names
querystringyesthe setting's name or what it does, such as max simultaneous hosts or session timeout, with the product if known
versionstring–the product version, such as 6.3 (default: the one the query names, or the current one)
NameTypeReqDescription
for_productstring–for Tenable Core, the product it runs that the filter applied
messagestring––
notesnull|array––
productstring–the product filter applied
settingsnull|arrayyes–

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.

NameTypeReqDescription
go_versionstringyes–
indexobjectyes–
notestring––
serverstringyes–
updatenull|object–set when a newer release of this server is available: tell the user, with its link
updatesobjectyes–
versionstringyes–

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.

NameTypeReqDescription
languagesnull|arrayyes–
productsnull|arrayyes–

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.

NameTypeReqDescription
helpfulbooleanyeswhether the user found the page helpful, from what they said
urlstringyesthe docs page the feedback is about
NameTypeReqDescription
pagestringyes–
sentstring–exactly what was sent: the user's own feedback, as they wrote it in the form
statusstringyessent, 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_bystring–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.

NameTypeReqDescription
guidestring–a guide's path, such as nessus or security-center/6_8, for its pages; give url or guide
languagestring–the site code of the guide's language (default en)
urlstring–a page, for its headings
NameTypeReqDescription
itemsnull|arrayyes–
titlestringyes–
urlstring––
wordsintegeryesthe 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.

NameTypeReqDescription
max_charsinteger–the most characters to return in one part, from 1000 to 30000 (default 8000)
partinteger–which part of a long section or page to read, from 1 (default 1)
urlstringyesa docs page or section link, as search_docs returns it; a link with #anchor reads that section, one without reads the whole page
NameTypeReqDescription
current_urlstring–the current version of this page, when this one is older
english_urlstring–the current English page, to cite for a translation or an older version
guide_typestring––
headingstring–the section read; empty for a whole page
languagestringyes–
last_modifiedstring––
locationstringyeswhere the page is in its guide's table of contents
markdownstringyesthe content, starting with a context header
nextnull|object–the section or page after this one
other_languagesnull|array––
other_versionsnull|array––
partintegeryes–
partsintegeryeshow many parts the content has; read the next with part
previousnull|object–the section or page before this one
productstring––
required_rolesnull|array––
titlestringyes–
urlstringyesthe link to cite for what was read
versionstring–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.

NameTypeReqDescription
guidestring–a guide's path (nessus, security-center/6_8), to refresh its table of contents and every page; give urls or guide
languagestring–the guide's language (default en)
urlsnull|array–pages to refresh, at most 500
NameTypeReqDescription
checkedintegeryes–
failednull|array––
removedintegeryes–
skippedintegeryes–
toc_updatedboolean––
unchangedintegeryes–
updatedintegeryes–

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.

NameTypeReqDescription
urlstringyesa docs page
NameTypeReqDescription
current_urlstring–the current version of this page, when this one is older
english_urlstring–the current English page, to cite for a translation or an older version
links_innull|array–docs pages that link to this page
links_outnull|array–docs pages this page links to
nextnull|object––
other_languagesnull|array––
other_versionsnull|array––
parentnull|object–the entry above this page in the table of contents
previousnull|object––
productstring––
same_titlenull|array–pages with the same title in other products or guides
titlestringyes–
urlstringyes–

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.

NameTypeReqDescription
fullboolean–return each entry's full text instead of a summary
languagestring–the release notes' language (default en)
limitinteger–how many entries to return, from 1 to 50 (default 10)
productstring––
querystring–words the entries must contain, such as a feature or a fixed issue
sincestring–only entries on or after this date, as YYYY-MM-DD, YYYY-MM, or YYYY
untilstring–only entries on or before this date, as YYYY-MM-DD, YYYY-MM, or YYYY
versionstring–only entries for this version or its patch releases (10.8 matches 10.8.1)
NameTypeReqDescription
entriesnull|arrayyesnewest first
languagestringyes–
messagestring––
productstring––

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.

NameTypeReqDescription
languagestring––
notestring–what was searched and found, such as only the 6.3 docs cover it; kept on this computer only
productstring––
questionstringyesthe user's question, as asked, without personal or customer details
urlstring–the docs page that came closest to answering, if any
NameTypeReqDescription
filestringyes–
recordedbooleanyes–
sentstring–exactly what was sent, as the user approved it in the form
sent_to_tenablestring–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
totalintegeryeshow many questions are recorded
written_bystring–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.

NameTypeReqDescription
languagestring––
productstring––
taskstringyeswhat the user wants to do, such as create a scan or add users
versionstring––
NameTypeReqDescription
answersnull|arrayyespages about the task that state the roles it needs, best first
closest_pages_without_rolesnull|array–when no page states a role: the pages that best match the task
messagestring––
notesnull|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".

NameTypeReqDescription
kindstring–ports, hardware, operating-systems, browsers, dependencies, or other (default: all, or what the query asks about)
limitinteger–how many rows to return, from 1 to 100 (default 30)
productstring–the product, by any of its names
querystring–words to look for, such as 443, RHEL, or 10,000 hosts; the product and kind can be named here too
versionstring––
NameTypeReqDescription
for_productstring–for Tenable Core, the product it runs that the filter applied
kindstring––
messagestring––
notesnull|array––
productstring––
requirementsnull|arrayyes–

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.

NameTypeReqDescription
guidestring–only this guide, by its path on the site, such as nessus or security-center/director (see browse_guide and list_products)
guide_typestring–only this guide type: User Guide, API Guide, Reference Guide, Integration Guide, Release Notes, Best Practices Guide, Migration Guide, Cyber Exposure Study, or Whitepaper
languagestring–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
limitinteger–how many results to return, from 1 to 25 (default 8)
productstring–only this product, by any of its names (retired ones such as Tenable.io and Tenable.sc work too)
querystringyeswhat to look for, in the user's words and language: a task, setting, message, or feature, with the product and version if known
release_notesboolean–only release notes
required_rolestring–only pages that say they need this role or permission, such as Administrator
versionstring–only this product version, such as 6.3 (default: the version the query names, or the current one)
NameTypeReqDescription
languagestringyesthe docs' language searched
messagestring––
notesnull|array––
other_productsnull|array–products that do have matches, when the product filter excluded them
relaxedboolean–set when no section had every word of the query
requested_languagestringyesthe language asked for or detected; it differs from language when the results fell back to English
resultsnull|arrayyes–
suggestionsnull|array–other spellings of the query to try, when nothing matched
versionstring–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.

NameTypeReqDescription
base_urlstring–the page the text will be published as, to resolve relative links (for a draft topic)
check_liveboolean–also check the live docs sites, for anchors that aren't headings and pages the index doesn't have
textstringyesthe answer or draft to check, in Markdown, HTML, or plain text
NameTypeReqDescription
linksnull|arrayyes–
problemsintegeryes–
skippedobjectyes–
warningsintegeryesolder 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.

NameTypeReqDescription
guidestring–only this guide, by its path, such as nessus or security-center/6_8
languagestring–the docs' language, as a site code (default en)
limitinteger–how many pages to list, from 1 to 100 (default 20)
productstring–only this product, by any of its names
sincestringyesthe start of the period: a date (2026-10-01 or 2026-10), or a number of days back (30d)
NameTypeReqDescription
changesnull|arrayyesnewest first
datednull|array–for the part of the period before the history begins: pages the sitemap dates in it, without what changed
history_sincestring–when this index's change history begins; it only knows changes from then on
messagestring––
moreboolean–there are more; narrow the period, product, or guide, or raise limit
sincestringyes–

No examples provided.

Install

How do I install the Tenable Docs MCP server?

Tenable Docs MCP ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, ddf1c42ba7c601689790b0c79f81edea10848117e8bbf685ac7af638a5545785; the commands to do that are on this page. If it does not match, do not open it.

mcpb · tenable-docs-mcp_1.0.1.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

ddf1c42ba7c601689790b0c79f81edea10848117e8bbf685ac7af638a5545785

macOS / Linux

echo "ddf1c42ba7c601689790b0c79f81edea10848117e8bbf685ac7af638a5545785  tenable-docs-mcp_1.0.1.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\tenable-docs-mcp_1.0.1.mcpb).Hash -eq "ddf1c42ba7c601689790b0c79f81edea10848117e8bbf685ac7af638a5545785"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

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 MCPB bundle (https://github.com/lanz/tenable-docs-mcp/releases/download/v1.0.1/tenable-docs-mcp_1.0.1.mcpb).

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.

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 an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.