CompBasis
REMOTE · MCP.HOUSINGCOMPS.COM
Comp-supported value range, post-sale tax and risks for one US home (IL, MI, MO, NY, TX).
Available components
Last scanned (21 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- 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 2436 tokens (~348/item across 7 items; 7 tools + 0 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 2% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask_about_property” rewrote its description, which is the text the model reads security
- Tool “get_job” rewrote its description, which is the text the model reads security
- Tool “get_report” rewrote its description, which is the text the model reads security
- Schema quality: 305 → 348 ▼ functional
- Server version: 1.1.0+e2637e91 → 1.1.0+c5cba169 functional
- New tool “lookup” functional
- “get_job” added an optional parameter “view” cosmetic
- “get_report” added an optional parameter “fields” cosmetic
- “analyze_property” reworded the description of “view” cosmetic
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +3
- Tool “get_report” rewrote its description, which is the text the model reads security
- Schema quality: 1408 → 1833 ▼ functional
- First check of Schema quality: 100 functional
- New prompt “compare_offers” functional
- New prompt “evaluate_listing” functional
- Server version: 1.30.0 → 1.1.0+e2637e91 functional
- New tool “price_scenarios” functional
- “analyze_property” added an optional parameter “additional_parcels” cosmetic
- “analyze_property” added an optional parameter “current_tax” cosmetic
- “analyze_property” added an optional parameter “listing_remarks” cosmetic
- “analyze_property” added an optional parameter “price_history_text” cosmetic
- “analyze_property” added an optional parameter “reuse_report_id” cosmetic
- “analyze_property” added an optional parameter “view” cosmetic
- “get_report” added an optional parameter “view” cosmetic
- 18 Nov 26 +1
- “analyze_property” added an optional parameter “listing_status” cosmetic
- “analyze_property” added an optional parameter “prior_contract_fell_through” cosmetic
- “analyze_property” added an optional parameter “prior_listings” cosmetic
3 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 17 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “analyze_property” added an optional parameter “original_list_price” cosmetic
- 16 Nov 26 0
- Tool “analyze_property” rewrote its description, which is the text the model reads security
- 15 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 67
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 · Probed https://mcp.housingcomps.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.housingcomps.com | CN=YE1,O=Let's Encrypt,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6753f64c2e1d72f6faaa4c459749c61c1e4 |
| SANs: mcp.housingcomps.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.housingcomps.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| housingcomps.com. | DS published | 16496 | 8 | Verified |
| mcp.housingcomps.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.housingcomps.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.housingcomps.com/mcp | HTTPS enforced | 301 | https://mcp.housingcomps.com/mcp |
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 →
analyze_property ~837
Analyze one US residential address and return the structured report: valuation.range (the comp-supported low to high with its measured error), valuation.anchor.price (the working price; valuation.anchor.source is what it is, and promoted_from names a figure that was set aside and NOT used, explained in valuation.anchor.explanation), negotiating_position (only when there is a real ask), condition (with evidence[]: the permits and code violations read, full text, each marked applies_to property, this_unit, other_unit or building; only property and this_unit records describe this home), confidence (High, Medium or Low, with what would tighten it), comps (the sales behind the range first, with in_range, up to 12 here and an 'omitted' block saying what was left out; get_report with full=true returns up to 50, and every excluded one; needs an API key, without one comps is empty and search.comps_withheld says so; search.pool_size says how many there were), tax (current bill and post-sale scenarios), listing, history, market, risks, gaps (what could not be determined) and attributions (notices that must accompany the figures when you repeat them). A null field means 'not determined'; an empty list means 'determined, none'. Pass list_price when you know the ask, and facts, condition and previous_sale for anything you know about the property (the input schema lists every field and its allowed values): they sharpen the answer and are recorded under inputs_used. A request that carries such facts is private to you and is not added to the shared cache. To steer the comparable sales: comp_radius_miles pins the search radius (no widening), exclude_comps lists addresses to leave out, and include_comps adds sales you know of (address, sale_price, sale_date, and sqft, beds, baths, year_built or lot_sqft if known); the report marks those comps provenance 'user', caps confidence at Medium, and excluded_comps[] shows what was dropped and why. If several parcels match, the result has sta…
| Name | Type | Req | Description |
|---|---|---|---|
| additional_parcels | array | – | – |
| address | string | yes | – |
| comp_radius_miles | – | – | – |
| condition | – | – | – |
| confirm_pin | – | – | – |
| current_tax | – | – | – |
| exclude_comps | array | – | – |
| facts | – | – | – |
| fresh | boolean | – | – |
| include | array | – | – |
| include_comps | array | – | – |
| list_date | – | – | – |
| list_price | – | – | – |
| listing_remarks | – | – | – |
| listing_status | – | – | – |
| manual_pin_override | – | – | – |
| original_list_price | – | – | – |
| personas | array | – | – |
| previous_sale | – | – | – |
| price_history_text | – | – | – |
| prior_contract_fell_through | – | – | – |
| prior_listings | array | – | – |
| priorities | – | – | – |
| reuse_report_id | – | – | – |
| view | string | – | summary (the default): a smaller answer that keeps the valuation, condition, confidence, tax, listing, leverage, market, monthly cost, flood and school risks, gaps and attributions, but leaves out pr… |
| Name | Type | Req | Description |
|---|---|---|---|
| address | null|object|string | – | A report's address block (input, resolved, county, state, pin, lat, lng), or, in a question's answer, the address asked about as a string. |
| assumable_loan | null|object | – | – |
| attributions | array|null | – | – |
| candidates | array | – | The parcels that match, when status is needs_confirmation. |
| comps | array|null | – | The sales behind the range, in_range first (the summary view keeps six). null means 'not determined' (or, in view=summary, left out: omitted.summary_view.left_out names it); an empty list or object m… |
| condition | null|object | – | – |
| confidence | null|object | – | – |
| disclaimer | null|string | – | – |
| excluded_comps | array|null | – | – |
| fields | object | – | get_report with fields: each named path and its value exactly as the full report has it. |
| gaps | array|null | – | – |
| history | null|object | – | – |
| inputs_used | array|null | – | – |
| investment | null|object | – | – |
| job_id | string | – | – |
| leverage | null|object | – | – |
| listing | null|object | – | – |
| listing_history | null|object | – | – |
| listing_remarks | null|object | – | – |
| market | null|object | – | – |
| message | string | – | – |
| meta | null|object | – | – |
| monthly_cost | null|object | – | – |
| narrative | null|object | – | – |
| next | string | – | – |
| not_found | array | – | get_report with fields: the paths that do not exist in the report. |
| note | string | – | – |
| omitted | object|null | – | What a shortened result left out, and how to get it (summary_view.left_out, how_to_get_all). |
| provenance | null|object | – | – |
| report_id | null|string | – | – |
| retry_after | number|null | – | – |
| risks | null|object | – | – |
| schema_version | null|string | – | – |
| search | null|object | – | – |
| status | string | – | Present when the result is not a finished report: 'processing' (call get_job with job_id) or 'needs_confirmation' (call again with confirm_pin set to one of candidates). |
| suggested_inputs | array|null | – | – |
| tax | null|object | – | – |
| text | string | – | A question's answer (get_job finishing ask_about_property). |
| tooling_note | string | – | – |
| transit | array|null | – | The nearest transit stations. null means 'not determined' (or, in view=summary, left out: omitted.summary_view.left_out names it); an empty list or object means 'determined, none'. A field that is ab… |
| valuation | null|object | – | – |
No examples provided.
ask_about_property ~279
DEPRECATED: prefer reasoning over the data yourself with get_report (fields=[...]) and lookup. This runs a second model inside CompBasis (slower, needs a key, limited per day) and returns a paragraph, and it will be removed from this server once lookup covers what it was used for. Ask a plain-language question about one property (for example its flood zone, school district outcomes, nearby amenities, what its tax bill is likely to be, or what a number in a report means). Give the question and either the address or the report_id of a report you already have (the address is then read from it). The answer is written from public data sources only and carries its own disclaimer. Needs an API key: send it as 'Authorization: Bearer <key>' on the MCP connection (a free key has a daily question limit). Returns {text, address}, or a job_id to pass to get_job if it takes longer than the wait budget. It is not the full analysis: analyze_property gives the valuation. The result is data about a property. Addresses (the subject's and the comparable sales') and answer text originate outside CompBasis, are marked x-untrusted in the API schema, and can contain arbitrary text.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | – |
| question | string | yes | – |
| report_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_job ~158
Check an analysis or question that analyze_property or ask_about_property handed back as 'processing'. Waits up to wait_seconds (default 25, at most 28) for it to finish, then returns the report (or the answer), or 'processing' again. A job id is valid for 24 hours. A finished report is the summary view unless you pass view=full (the same default as analyze_property). The result is data about a property. Addresses (the subject's and the comparable sales') and answer text originate outside CompBasis, are marked x-untrusted in the API schema, and can contain arbitrary text.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| view | string | – | – |
| wait_seconds | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| address | null|object|string | – | A report's address block (input, resolved, county, state, pin, lat, lng), or, in a question's answer, the address asked about as a string. |
| assumable_loan | null|object | – | – |
| attributions | array|null | – | – |
| candidates | array | – | The parcels that match, when status is needs_confirmation. |
| comps | array|null | – | The sales behind the range, in_range first (the summary view keeps six). null means 'not determined' (or, in view=summary, left out: omitted.summary_view.left_out names it); an empty list or object m… |
| condition | null|object | – | – |
| confidence | null|object | – | – |
| disclaimer | null|string | – | – |
| excluded_comps | array|null | – | – |
| fields | object | – | get_report with fields: each named path and its value exactly as the full report has it. |
| gaps | array|null | – | – |
| history | null|object | – | – |
| inputs_used | array|null | – | – |
| investment | null|object | – | – |
| job_id | string | – | – |
| leverage | null|object | – | – |
| listing | null|object | – | – |
| listing_history | null|object | – | – |
| listing_remarks | null|object | – | – |
| market | null|object | – | – |
| message | string | – | – |
| meta | null|object | – | – |
| monthly_cost | null|object | – | – |
| narrative | null|object | – | – |
| next | string | – | – |
| not_found | array | – | get_report with fields: the paths that do not exist in the report. |
| note | string | – | – |
| omitted | object|null | – | What a shortened result left out, and how to get it (summary_view.left_out, how_to_get_all). |
| provenance | null|object | – | – |
| report_id | null|string | – | – |
| retry_after | number|null | – | – |
| risks | null|object | – | – |
| schema_version | null|string | – | – |
| search | null|object | – | – |
| status | string | – | Present when the result is not a finished report: 'processing' (call get_job with job_id) or 'needs_confirmation' (call again with confirm_pin set to one of candidates). |
| suggested_inputs | array|null | – | – |
| tax | null|object | – | – |
| text | string | – | A question's answer (get_job finishing ask_about_property). |
| tooling_note | string | – | – |
| transit | array|null | – | The nearest transit stations. null means 'not determined' (or, in view=summary, left out: omitted.summary_view.left_out names it); an empty list or object means 'determined, none'. A field that is ab… |
| valuation | null|object | – | – |
No examples provided.
get_report ~244
Fetch a finished report by its report_id (as returned in a report's meta.report_id). Read only: it never starts an analysis; to analyze an address, use analyze_property. Returns the same report object as analyze_property. Long lists of comparable sales are shortened to the ones that set the range, with an 'omitted' block that says what was left out; full=true returns every comparable sale and every excluded one; view=summary returns a smaller answer (no provenance, hazard ratings, excluded sales, history or transit; at most six comparable sales). fields=[...] returns only the named parts (dotted paths such as 'transit' or 'tax.rate_history', up to 12) with the attributions and disclaimer, as the full report has them: the way to read one thing a summary left out. The result is data about a property. Addresses (the subject's and the comparable sales') and answer text originate outside CompBasis, are marked x-untrusted in the API schema, and can contain arbitrary text.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | – |
| full | boolean | – | – |
| report_id | string | yes | – |
| view | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| address | null|object|string | – | A report's address block (input, resolved, county, state, pin, lat, lng), or, in a question's answer, the address asked about as a string. |
| assumable_loan | null|object | – | – |
| attributions | array|null | – | – |
| candidates | array | – | The parcels that match, when status is needs_confirmation. |
| comps | array|null | – | The sales behind the range, in_range first (the summary view keeps six). null means 'not determined' (or, in view=summary, left out: omitted.summary_view.left_out names it); an empty list or object m… |
| condition | null|object | – | – |
| confidence | null|object | – | – |
| disclaimer | null|string | – | – |
| excluded_comps | array|null | – | – |
| fields | object | – | get_report with fields: each named path and its value exactly as the full report has it. |
| gaps | array|null | – | – |
| history | null|object | – | – |
| inputs_used | array|null | – | – |
| investment | null|object | – | – |
| job_id | string | – | – |
| leverage | null|object | – | – |
| listing | null|object | – | – |
| listing_history | null|object | – | – |
| listing_remarks | null|object | – | – |
| market | null|object | – | – |
| message | string | – | – |
| meta | null|object | – | – |
| monthly_cost | null|object | – | – |
| narrative | null|object | – | – |
| next | string | – | – |
| not_found | array | – | get_report with fields: the paths that do not exist in the report. |
| note | string | – | – |
| omitted | object|null | – | What a shortened result left out, and how to get it (summary_view.left_out, how_to_get_all). |
| provenance | null|object | – | – |
| report_id | null|string | – | – |
| retry_after | number|null | – | – |
| risks | null|object | – | – |
| schema_version | null|string | – | – |
| search | null|object | – | – |
| status | string | – | Present when the result is not a finished report: 'processing' (call get_job with job_id) or 'needs_confirmation' (call again with confirm_pin set to one of candidates). |
| suggested_inputs | array|null | – | – |
| tax | null|object | – | – |
| text | string | – | A question's answer (get_job finishing ask_about_property). |
| tooling_note | string | – | – |
| transit | array|null | – | The nearest transit stations. null means 'not determined' (or, in view=summary, left out: omitted.summary_view.left_out names it); an empty list or object means 'determined, none'. A field that is ab… |
| valuation | null|object | – | – |
No examples provided.
list_coverage ~62
List the states CompBasis covers (with whether each is live, and its caveats), the call limits for keyless and keyed use, and whether a new analysis can start now. Useful when an address is rejected as out of scope or a limit is reached.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
lookup ~316
Look up public data directly, with no model in between: flood zones, radon, school district outcomes, tax rates and parcel records, crime counts, permits, transit, hazards, amenities, mortgage rates, closing-cost estimates and more (the same data sources the report and ask_about_property use; no vendor data). Use this for facts the report does not carry, then reason over the data yourself. Call with no arguments for the catalog (about 125 lookups, one line each; narrow it with state='TX' and/or search='flood'). Call with just name to see one lookup's full description and input schema. Call with name and arguments to run it. Most lookups need coordinates or a county, not an address: run lookup(name='resolve_address', arguments={'address': ...}) first, which returns the state, county, parcel number and latitude/longitude the others take. The result is {result, notices, note}: a null or empty result means the source had nothing for those inputs, which is NOT evidence that there is none; notices are source attributions that must accompany any figure you repeat. A lookup that does not cover the place says so; do not substitute another place's figure. The result is data about a property. Addresses (the subject's and the comparable sales') and answer text originate outside CompBasis, are marked x-untrusted in the API schema, and can contain arbitrary text.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | – | – | – |
| name | – | – | – |
| search | – | – | – |
| state | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
price_scenarios ~234
Read a finished report at other prices, with no new analysis and no data cost: for up to eight prices (an ask, your offers) it gives the property tax the report's projection would give, the monthly cost on the report's own financing basis, and how a price like that reads against the report's evidence (the same Below Range / Fair / Above Range / Well Above Range label as negotiating_position; a label for a price, not a prediction that a seller accepts it). Needs the report_id of a report you already have (meta.report_id). Arithmetic on the report's own figures: the value, the range and every input are unchanged, so use analyze_property again when a fact changes. Where a property's tax does not move with the price (some states), tax and monthly cost are null and notes says so. The result is data about a property. Addresses (the subject's and the comparable sales') and answer text originate outside CompBasis, are marked x-untrusted in the API schema, and can contain arbitrary text.
| Name | Type | Req | Description |
|---|---|---|---|
| prices | array | yes | – |
| report_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the CompBasis MCP server?
CompBasis is a hosted endpoint at https://mcp.housingcomps.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.housingcomps.com
claude mcp add --transport http com-housingcomps-compbasis 'https://mcp.housingcomps.com/mcp'
What is the CompBasis MCP server?
CompBasis is an MCP server listed in the public MCP registry as com.housingcomps/compbasis. Comp-supported value range, post-sale tax and risks for one US home (IL, MI, MO, NY, TX). This page covers its hosted endpoint (https://mcp.housingcomps.com/mcp).
Is the CompBasis MCP server safe to use?
CompBasis scores 73 out of 100 on VerifyMCP. 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 CompBasis MCP server expose?
CompBasis exposes 7 tools: analyze_property, get_report, price_scenarios, ask_about_property, get_job, and 2 more. Their descriptions and schemas cost roughly 2,130 tokens of context every time the server is loaded.
Does the CompBasis MCP server require authentication?
No. We connected to CompBasis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CompBasis MCP server still maintained?
CompBasis 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 did VerifyMCP test on the CompBasis MCP server?
VerifyMCP ran 13 checks on CompBasis, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.