FX Context
REMOTE · FX.COCO-PIER.COM
FX macro context: CPI, NFP, PCE, ISM PMIs, Fed, ECB, BoE, BoJ, historical analogs, FX reactions.
Available components
Last scanned (17 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3070 tokens (~511/item across 6 items; 6 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 10 Nov 26 +1
- Stability: 0.97 → pass security
- 9 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 11 Oct 26 0
- Tool “get_event_context” rewrote its description, which is the text the model reads security
- Tool “get_historical_analogs” rewrote its description, which is the text the model reads security
- Tool “get_historical_reaction_context” rewrote its description, which is the text the model reads security
- Tool “get_market_reaction” rewrote its description, which is the text the model reads security
- Tool “get_upcoming_risks” rewrote its description, which is the text the model reads security
- Schema quality: 451 → 511 ▼ functional
- Server version: 0.9.0 → 1.0.1 functional
- “get_event_context” reworded the description of “eventType” cosmetic
- “get_historical_analogs” reworded the description of “eventType” cosmetic
- “get_historical_reaction_context” reworded the description of “eventType” cosmetic
- “get_market_reaction” reworded the description of “dateOrPeriod” cosmetic
- “get_market_reaction” reworded the description of “targetType” cosmetic
- 9 Oct 26 0
- Schema quality: 381 → 451 ▼ functional
- Server version: 0.8.0 → 0.9.0 functional
- 3 Oct 26 0
- Tool “get_event_context” rewrote its description, which is the text the model reads security
- Schema quality: 325 → 381 ▼ functional
- Server version: 0.7.0 → 0.8.0 functional
- “get_event_context” reworded the description of “eventType” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://fx.coco-pier.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=coco-pier.com | CN=YE1,O=Let's Encrypt,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6a3fab6c14424ad822caf3c7e8c2b4fd829 |
| SANs: *.coco-pier.com, coco-pier.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 insecure
Validation of fx.coco-pier.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| coco-pier.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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://fx.coco-pier.com/mcp | Verified | 200 | |
| http (plaintext) | http://fx.coco-pier.com/mcp | Inconclusive | 405 |
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 →
get_central_bank_changes ~225
Compare a central bank monetary-policy statement with its immediately preceding comparable statement and return the material changes in policy language, economic assessment, risk balance, and forward guidance. Specify a central bank such as FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ). Optionally specify currentStatementDate in YYYY-MM-DD format to compare a historical statement. If the date is omitted, the latest available statement is compared with the previous one. Returns structured, source-grounded policy changes including direction, materiality, and previous/current evidence. This tool does not provide trading recommendations or predict market movements.
| Name | Type | Req | Description |
|---|---|---|---|
| centralBank | string | yes | Canonical central bank identifier: FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ). |
| currentStatementDate | string | – | Optional publication date in YYYY-MM-DD format (e.g. 2024-07-31). If omitted, the latest available statement is compared with the previous one. |
| Name | Type | Req | Description |
|---|---|---|---|
| centralBank | string | yes | – |
| changes | array | yes | – |
| currentPolicyAction | string | yes | – |
| currentPolicyBias | string | yes | – |
| currentSourceUri | string | yes | – |
| currentStatementDate | string | yes | – |
| currentStatementId | string | yes | – |
| degraded | boolean | – | – |
| discardedChangeCount | integer | – | – |
| freshness | object | – | – |
| overallShift | string | yes | – |
| previousSourceUri | string | yes | – |
| previousStatementDate | string | yes | – |
| previousStatementId | string | yes | – |
No examples provided.
get_event_context ~718
Get the official actual values, pre-release market consensus, and surprise for a specific U.S. macro data release: CPI (US_CPI), Nonfarm Payrolls / jobs report (US_NONFARM_PAYROLLS), PCE inflation (US_PCE), or the ISM Manufacturing / Services PMI (US_ISM_MANUFACTURING / US_ISM_SERVICES). WHEN TO CALL: whenever the user asks what a release printed or how it compared with expectations, even if they do not mention FX Context. Do not answer these from memory; recent releases are not in your training data. Examples: - "What's the latest US PCE?" -> US_PCE - "Was core PCE hotter than expected?" -> US_PCE - "Did CPI beat expectations?" -> US_CPI - "What was the latest NFP?" / "How many jobs were added last month?" -> US_NONFARM_PAYROLLS - "Give me the latest US inflation release." -> US_CPI and/or US_PCE - "What's the latest ISM Manufacturing PMI?" -> US_ISM_MANUFACTURING - "Did ISM Services beat expectations?" -> US_ISM_SERVICES - "What were the actual and consensus values?" / "What was the surprise?" -> the release under discussion Omit referencePeriod for the latest release. For a specific release, pass the month the data covers (YYYY-MM), not the month it was published. WHEN NOT TO CALL: general or educational questions that need no specific release data, e.g. "What is PCE?", "What does NFP stand for?", "Why does CPI matter for FX?", "Explain inflation.", "What is the difference between CPI and PCE?". Use get_upcoming_risks for upcoming release dates, get_market_reaction for price moves after a release, and get_central_bank_changes for central-bank decisions. RESULT: per-metric official actuals (headline/core, MoM/YoY; ISM: headline PMI index) with publisher provenance; when valid, pre-release consensus and a deterministic actual-minus-consensus surprise. Each observation has consensusStatus (AVAILABLE, NOT_FOUND, NOT_CAPTURED, NOT_AVAILABLE, EXCLUDED_POST_RELEASE, NOT_APPLICABLE) explaining any missing consensus, and revisionStatus (REVISED, UNCHANGED, NOT_CAPTURE…
| Name | Type | Req | Description |
|---|---|---|---|
| eventType | string | yes | Canonical financial event type. Supported values: US_CPI (Consumer Price Index; headline and core CPI) US_NONFARM_PAYROLLS (NFP / jobs report; payrolls, unemployment rate, average hourly earnings) U… |
| referencePeriod | string | – | Optional reference period in YYYY-MM format (e.g. 2026-08). If omitted, the latest available event of that type is returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| affectedCurrencies | array | yes | – |
| category | string | yes | – |
| eventId | string | yes | – |
| eventType | string | yes | – |
| jurisdiction | string | yes | – |
| observations | array | yes | – |
| referencePeriod | string | – | – |
| releasedAt | string | – | – |
| scheduledAt | string | yes | – |
| source | – | yes | – |
| status | string | yes | – |
No examples provided.
get_historical_analogs ~657
Find and return individual historical macroeconomic releases whose surprise profiles are most similar to a selected target event. Use this CASE-RETRIEVAL tool when the user wants to identify, rank, inspect, or compare specific historical analog events. It returns the matched events themselves, including event identity, similarity characteristics, surprise profile, and each event's observed post-release reaction. Supported event types: US_CPI and US_NONFARM_PAYROLLS across EURUSD, GBPUSD, and USDJPY. US_PCE is recognized but not yet publicly available: the historical PCE calibration corpus currently has too few usable periods, and a request for US_PCE returns a structured INSUFFICIENT_HISTORICAL_CALIBRATION error (with usable/required event counts) instead of analog results until the corpus grows. ISM is not currently available here: US_ISM_MANUFACTURING and US_ISM_SERVICES have no verified pre-release consensus yet, so they return INSUFFICIENT_HISTORICAL_CALIBRATION rather than analogs. For ISM, use get_event_context for actuals and get_market_reaction for price moves. Similarity methodology is event-specific: US_CPI uses headline/core surprise distance; US_NONFARM_PAYROLLS uses target-relative robust scale normalization (nfp-historical-analog-v1); US_PCE (once activated) uses the same raw surprise -distance approach as US_CPI (pce-historical-analog-v1). Target period: if referencePeriod is omitted, the target is the most recent event of the requested type. Surprises are never estimated, so if that event has no verified pre-release consensus (common right after a new NFP release) the tool fails with NO_VERIFIED_PRE_RELEASE_EXPECTATION. The error details include targetReferencePeriod, latestReleasedPeriod, latestPeriodWithVerifiedExpectation and a hint; to analyze that prior period, retry with referencePeriod=YYYY-MM. Tell the user the newest release could not be analyzed rather than presenting the prior period as the latest. Every "cannot compute" error has…
| Name | Type | Req | Description |
|---|---|---|---|
| eventType | string | yes | Canonical target event type: US_CPI, US_NONFARM_PAYROLLS, US_PCE, US_ISM_MANUFACTURING, or US_ISM_SERVICES. |
| instrument | string | – | Optional trading instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD. |
| maxAnalogs | integer | – | Optional maximum number of individual analogs to return (range 3 to 30, default 10). |
| referencePeriod | string | – | Optional reference period in YYYY-MM format (e.g. 2024-06 or 2026-08). If omitted, the most recent event is the target. Use it to analyze a prior period when the latest event has no verified pre-rele… |
| Name | Type | Req | Description |
|---|---|---|---|
| analogs | array | yes | – |
| coverage | object | yes | – |
| eventType | string | yes | – |
| instrument | string | yes | – |
| methodology | object | yes | – |
| methodologyVersion | string | yes | – |
| reactionStatistics | array | yes | – |
| referencePeriod | string | yes | – |
| targetSurprise | – | yes | – |
No examples provided.
get_historical_reaction_context ~628
Summarize the aggregate post-event reaction pattern across historical macroeconomic events similar to a selected target release. Use this AGGREGATE-PATTERN tool when the user wants to understand what the historical analog sample collectively showed rather than inspect individual analog events. It summarizes historical outcomes using statistics and behavioral patterns across standardized post-event windows (M5, M15, H1, H4, H24) such as mean, median, quantiles, directional consistency, reaction-path classification (e.g. IMMEDIATE_CONTINUATION, INITIAL_REVERSAL, FADE, DELAYED_REACTION), persistence, and sample-size-based confidence. Supported event types: US_CPI and US_NONFARM_PAYROLLS across EURUSD, GBPUSD, and USDJPY. ISM is not currently available here: US_ISM_MANUFACTURING and US_ISM_SERVICES have no verified pre-release consensus yet, so they return a structured INSUFFICIENT_HISTORICAL_CALIBRATION error rather than aggregate statistics. Similarity methodology is event-specific: US_CPI uses headline/core surprise distance; US_NONFARM_PAYROLLS uses target-relative robust scale normalization (nfp-historical-analog-v1). Target period: if referencePeriod is omitted, the target is the most recent event of the requested type. Surprises are never estimated, so if that event has no verified pre-release consensus (common right after a new NFP release) the tool fails with NO_VERIFIED_PRE_RELEASE_EXPECTATION. The error details include targetReferencePeriod, latestReleasedPeriod, latestPeriodWithVerifiedExpectation and a hint; to analyze that prior period, retry with referencePeriod=YYYY-MM. Tell the user the newest release could not be analyzed rather than presenting the prior period as the latest. Every "cannot compute" error has the same shape: "CODE: reason [hint] details={json}", where the JSON always contains code, eventType and hint. Do NOT use this tool when the user's primary goal is to identify, rank, enumerate, or inspect specific historical analog events.…
| Name | Type | Req | Description |
|---|---|---|---|
| eventType | string | yes | Canonical target event type: US_CPI, US_NONFARM_PAYROLLS, US_ISM_MANUFACTURING, or US_ISM_SERVICES. |
| instrument | string | – | Optional trading instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD. |
| limit | integer | – | Optional maximum number of similar historical events to include in aggregate analysis (range 3 to 30, default 10). |
| referencePeriod | string | – | Optional reference period in YYYY-MM format (e.g. 2024-06 or 2026-08). If omitted, the most recent event is the target. Use it to analyze a prior period when the latest event has no verified pre-rele… |
| Name | Type | Req | Description |
|---|---|---|---|
| aggregatePattern | object | yes | – |
| analogs | array | yes | – |
| coverage | object | yes | – |
| eventType | string | yes | – |
| instrument | string | yes | – |
| reactionStatistics | object | yes | – |
| referencePeriod | string | yes | – |
| targetSurpriseProfile | – | yes | – |
No examples provided.
get_market_reaction ~487
Retrieve deterministic post-event market reaction metrics for an economic release or monetary policy statement. Specify the targetType, such as US_CPI, US_PCE (alias PCE), US_NONFARM_PAYROLLS (alias NFP), US_ISM_MANUFACTURING (alias ISM_MANUFACTURING), US_ISM_SERVICES (alias ISM_SERVICES), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ). Optionally specify dateOrPeriod: - For US_CPI, US_PCE, US_NONFARM_PAYROLLS, and the ISM PMIs: reference period in YYYY-MM format (e.g. 2024-07). If omitted, the latest event is resolved. - For FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND, or BANK_OF_JAPAN: statement date in YYYY-MM-DD format (e.g. 2024-08-01). If omitted, the latest statement is resolved. Optionally specify instrument: EURUSD, GBPUSD, or USDJPY (defaults to EURUSD). Returns deterministic price action metrics across 5 standardized post-event windows (M5, M15, H1, H4, H24) including startPrice, endPrice, returnPct, high, low, maxUpMovePct, maxDownMovePct, and rangePct. All calculations are strictly deterministic and mathematical. This tool does not provide trading recommendations or predictive signals.
| Name | Type | Req | Description |
|---|---|---|---|
| dateOrPeriod | string | – | Optional reference period (YYYY-MM for US_CPI, US_PCE, US_NONFARM_PAYROLLS, and the ISM PMIs) or statement date (YYYY-MM-DD for central banks). If omitted, the latest event is returned. |
| instrument | string | – | Optional trading instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD. |
| targetType | string | yes | Canonical target event type: US_CPI, US_PCE (alias PCE), US_NONFARM_PAYROLLS (alias NFP), US_ISM_MANUFACTURING (alias ISM_MANUFACTURING), US_ISM_SERVICES (alias ISM_SERVICES), FEDERAL_RESERVE, ECB, B… |
| Name | Type | Req | Description |
|---|---|---|---|
| calculatedAt | string | yes | – |
| coverageStatus | string | – | – |
| eventTime | string | yes | – |
| freshness | object | – | – |
| instrument | string | yes | – |
| isComplete | boolean | yes | – |
| isSettled | boolean | yes | – |
| marketDataSource | string | yes | – |
| reactionCoverage | object | – | – |
| reactionId | string | yes | – |
| targetDescription | string | yes | – |
| targetId | string | yes | – |
| targetType | string | yes | – |
| windows | array | yes | – |
No examples provided.
get_upcoming_risks ~355
Retrieve known scheduled macroeconomic and central-bank risks that may affect a supported FX instrument within a future time window. Use this tool when the user asks what could move EURUSD, GBPUSD, or USDJPY, what macro risks are coming up, what is happening in the next 24 hours, this week, or over the next month, what upcoming macro risks or scheduled events exist, or when the next CPI, next NFP, next PCE, next ISM, next Fed, next ECB, next BoE, or next BoJ event occurs. The supported risks are U.S. CPI releases, U.S. Nonfarm Payrolls releases, U.S. PCE inflation releases, ISM Manufacturing and Services PMI releases, Federal Reserve monetary-policy decisions, ECB monetary-policy decisions, Bank of England monetary-policy decisions, and Bank of Japan monetary-policy decisions. The horizon can extend up to 720 hours (30 days). scheduleCoverage reports, for each supported event type, the latest known scheduled date and whether the known calendar covers the whole window. If scheduleCoverageComplete is false, some event types may have additional events in the window that are not yet known; say so instead of treating the list as complete. Results are based on official release calendars and contain scheduled events only. This tool does not predict market direction, include unscheduled news, or provide trading recommendations. If no supported scheduled event exists within the requested horizon, an empty risk list is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| horizonHours | integer | – | Future time window in hours. Defaults to 24. Maximum is 720 (30 days). |
| instrument | string | – | FX instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | – |
| horizonHours | integer | yes | – |
| instrument | string | yes | – |
| risks | array | yes | – |
| scheduleCoverage | array | yes | – |
| scheduleCoverageComplete | boolean | yes | – |
| windowEnd | string | yes | – |
No examples provided.
How do I install the FX Context MCP server?
FX Context is a hosted endpoint at https://fx.coco-pier.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 · fx.coco-pier.com
claude mcp add --transport http com-coco-pier-fx-context 'https://fx.coco-pier.com/mcp'
What is the FX Context MCP server?
FX Context is an MCP server listed in the public MCP registry as com.coco-pier/fx-context. FX macro context: CPI, NFP, PCE, ISM PMIs, Fed, ECB, BoE, BoJ, historical analogs, FX reactions. This page covers its hosted endpoint (https://fx.coco-pier.com/mcp).
Is the FX Context MCP server safe to use?
FX Context scores 79 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 FX Context MCP server expose?
FX Context exposes 6 tools: get_central_bank_changes, get_event_context, get_historical_analogs, get_historical_reaction_context, get_market_reaction, get_upcoming_risks. Their descriptions and schemas cost roughly 3,070 tokens of context every time the server is loaded.
Does the FX Context MCP server require authentication?
No. We connected to FX Context without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FX Context MCP server still maintained?
FX Context 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 FX Context MCP server?
VerifyMCP ran 12 checks on FX Context, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about FX Context: HTTPS. 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.