Opportunity Zones (opportunityzones.help)
REMOTE · WWW.OPPORTUNITYZONES.HELP
Opportunity Zone address and tract lookup (2018 zones and the 2027 round), state data, program.
Available components
Last scanned (42 minutes ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability62
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1409 tokens (~108/item across 13 items; 13 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 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.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 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 5 Nov 2026 · Probed https://www.opportunityzones.help/api/oz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.opportunityzones.help | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1c5addbd8e66f94a0e587ad03b6cd83d |
| SANs: www.opportunityzones.help | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.opportunityzones.help. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| help. | present | 10505, 58472 | 13, 13 | Verified |
| opportunityzones.help. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.opportunityzones.help/api/oz/mcp | Verified | 200 | |
| http (plaintext) | http://www.opportunityzones.help/api/oz/mcp | HTTPS enforced | 301 | https://www.opportunityzones.help/api/oz/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 →
calc_180_day_deadline 180-day investment deadline ~117
Last day to invest a gain in a QOF, with every start date the taxpayer may choose (direct, pass-through K-1, section 1231, RIC/REIT dividend, installment) and whether the window reaches OZ 2.0 (Jan 1, 2027).
| Name | Type | Req | Description |
|---|---|---|---|
| dividend_date | string | – | – |
| entity_return_due | string | – | – |
| entity_year_end | string | – | – |
| kind | string | – | – |
| sale_date | string | yes | YYYY-MM-DD |
No output schema declared.
No examples provided.
calc_2026_inclusion OZ 1.0 Dec 31, 2026 inclusion estimate ~101
Amount of deferred gain included on Dec 31, 2026 for a pre-2027 QOF investment, with the 10%/15% basis step-up where the holding period was met, and an estimated tax at the user's rate.
| Name | Type | Req | Description |
|---|---|---|---|
| deferred_gain | number | yes | – |
| fmv_12_31_2026 | number | – | – |
| invest_date | string | yes | – |
| rate_pct | number | – | – |
No output schema declared.
No examples provided.
calc_90_percent_test QOF 90% asset test ~221
Averages the two semiannual testing dates and, if the fund falls short, computes the Form 8996 Part IV penalty month by month (pass month-end figures in monthly for an exact figure; otherwise testing-date figures are applied to each half-year and the result is flagged as an approximation) at an underpayment rate the caller supplies.
| Name | Type | Req | Description |
|---|---|---|---|
| d1_qozp | number | – | – |
| d1_total | number | – | – |
| d2_qozp | number | yes | – |
| d2_total | number | yes | – |
| monthly | array | – | Optional month-end figures for Form 8996 Part IV: [{total, qozp, rate_pct}] |
| months | number | – | Months the entity was a QOF this year, 1-12 (default 12) |
| single_date | boolean | – | true if only the year-end test applies (first year under 6 months); otherwise d1_* are required |
| underpayment_rate_pct | number | – | IRS underpayment rate for the period, percent |
No output schema declared.
No examples provided.
calc_oz2_benefit OZ 2.0 benefit vs paying tax now ~123
Models an OZ 2.0 investment (5-year deferral, 10% or rural 30% step-up, 10-year exclusion capped at year 30) against paying tax now and investing the remainder.
| Name | Type | Req | Description |
|---|---|---|---|
| discount_pct | number | – | – |
| gain | number | yes | – |
| growth_pct | number | yes | – |
| hold_years | number | yes | – |
| invest_date | string | – | – |
| rate_later_pct | number | – | – |
| rate_now_pct | number | yes | – |
| rural | boolean | – | – |
No output schema declared.
No examples provided.
calc_substantial_improvement Substantial improvement test ~82
How much must be added to a building's basis within 30 months (100%, or 50% in a zone made up entirely of rural areas).
| Name | Type | Req | Description |
|---|---|---|---|
| land_value | number | – | – |
| purchase_price | number | yes | – |
| rural | boolean | – | – |
| spent_so_far | number | – | – |
| start_date | string | – | – |
No output schema declared.
No examples provided.
check_qozb Qualified Opportunity Zone Business tests ~127
Checks the 70% tangible property, 50% gross income, 40% intangibles and 5% nonqualified financial property tests and the excluded-business list.
| Name | Type | Req | Description |
|---|---|---|---|
| gross_income_total | number | – | – |
| gross_income_zone | number | – | – |
| intangibles_total | number | – | – |
| intangibles_used_in_zone | number | – | – |
| nqfp | number | – | – |
| sin_business | boolean | – | – |
| tangible_qozbp | number | – | – |
| tangible_total | number | – | – |
| total_basis | number | – | – |
No output schema declared.
No examples provided.
get_financing_link Get an Opportunity Zone financing quote ~58
Link where a developer, sponsor or business owner can request debt financing for a project in an Opportunity Zone. Routed to Janover Capital LLC's desk; free, no obligation. Janover arranges loans; it does not sell fund interests.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_key_dates Opportunity Zone key dates ~34
The program calendar: OZ 1.0 inclusion date, OZ 2.0 start, designation periods, filing dates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_state Opportunity Zones in a state ~59
Counts of 2018 zones, rural zones, 2027-eligible tracts and their nomination/certification status for one state or territory, with the official source.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Two-letter code, FIPS code or name |
No output schema declared.
No examples provided.
get_tract One census tract's Opportunity Zone record ~154
Status for an 11-digit census tract GEOID. A 2010 GEOID is checked against the 2018 designations and a 2020 GEOID against the 2027 round; many GEOIDs exist in both vintages. If you already geocoded a property, pass geoid_2010 and geoid_2020 instead of geoid.
| Name | Type | Req | Description |
|---|---|---|---|
| geoid | string | – | 11-digit tract GEOID (state+county+tract) |
| geoid_2010 | string | – | The property's 2010 tract GEOID (for 2018 status) |
| geoid_2020 | string | – | The property's 2020 tract GEOID (for 2027 status) |
No output schema declared.
No examples provided.
lookup_address Is this address in an Opportunity Zone? ~112
Geocodes a US street address (Census Bureau geocoder, falling back to OpenStreetMap; tract assignment by the FCC Census Block API) and returns its 2018 Opportunity Zone status (2010 tract), its status for the 2027 designation round (2020 tract: eligible, nominated or certified, with source), the rural flags, and Census ACS tract statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | One-line US address, e.g. '2 Woodward Ave, Detroit, MI 48226' |
No output schema declared.
No examples provided.
lookup_coordinates Opportunity Zone status for a point ~33
Same as lookup_address for a latitude/longitude point.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
No output schema declared.
No examples provided.
plan_working_capital Working capital safe harbor timeline ~63
Spend-by dates for each cash infusion under the 31-month working capital safe harbor, and the 62-month outer limit available to start-up businesses.
| Name | Type | Req | Description |
|---|---|---|---|
| disaster | boolean | – | – |
| infusions | array | yes | – |
| startup | boolean | – | – |
No output schema declared.
No examples provided.
How do I install the Opportunity Zones (opportunityzones.help) MCP server?
Opportunity Zones (opportunityzones.help) is a hosted endpoint at https://www.opportunityzones.help/api/oz/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 · www.opportunityzones.help
claude mcp add --transport http help-opportunityzones-www-opportunityzones-help 'https://www.opportunityzones.help/api/oz/mcp'
What is the Opportunity Zones (opportunityzones.help) MCP server?
Opportunity Zones (opportunityzones.help) is an MCP server listed in the public MCP registry as help.opportunityzones.www/opportunityzones-help. Opportunity Zone address and tract lookup (2018 zones and the 2027 round), state data, program. This page covers its hosted endpoint (https://www.opportunityzones.help/api/oz/mcp).
Is the Opportunity Zones (opportunityzones.help) MCP server safe to use?
Opportunity Zones (opportunityzones.help) scores 69 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 Opportunity Zones (opportunityzones.help) MCP server expose?
Opportunity Zones (opportunityzones.help) exposes 13 tools: lookup_address, lookup_coordinates, get_tract, get_state, get_key_dates, and 8 more. Their descriptions and schemas cost roughly 1,284 tokens of context every time the server is loaded.
Does the Opportunity Zones (opportunityzones.help) MCP server require authentication?
No. We connected to Opportunity Zones (opportunityzones.help) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Opportunity Zones (opportunityzones.help) MCP server still maintained?
Opportunity Zones (opportunityzones.help) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.