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.

Woodpecker: NYC HPD registration lookup

REMOTE · WOODPECKER.HELP

NYC building HPD registration status, open filing violations and Woodpecker's yearly price.

Available components

+4 this week 77 Trust /100

Last scanned (14 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

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. 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
  • 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
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 574 tokens (~95/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

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 →

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 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 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.

  • 17 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.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.07 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 12 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Nov 26 72

    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 · Probed https://woodpecker.help/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=woodpecker.help CN=YR1,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 RSA 2048 SHA256-RSA 691ef585a931fe30f09070a205ea76983c3
SANs: woodpecker.help
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of woodpecker.help. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
help. DS published 10505, 58472 13, 13 Verified
woodpecker.help. 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://*.js.stripe.com https://checkout.stripe.com https://www.googletagmanager.com https://*.googleadservices.com https://googleads.g.doubleclick.net https://bat.bing.com https://www.clarity.ms https://*.clarity.ms https://app.cal.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://*.stripe.com https://*.google.com https://*.doubleclick.net https://www.googletagmanager.com https://*.googleadservices.com https://bat.bing.com https://bat.bing.net https://*.clarity.ms https://c.bing.com; font-src 'self'; connect-src 'self' https://*.supabase.co https://api.stripe.com https://checkout.stripe.com https://merchant-ui-api.stripe.com https://m.stripe.network https://q.stripe.com https://*.google.com https://www.googletagmanager.com https://*.googleadservices.com https://*.doubleclick.net https://pagead2.googlesyndication.com https://bat.bing.com https://bat.bing.net https://*.clarity.ms https://c.bing.com https://app.c
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://woodpecker.help/mcp Verified 200
http (plaintext) http://woodpecker.help/mcp HTTPS enforced 308 https://woodpecker.help/mcp
MCP tools · 6 exposed · ~415 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
explain_hpd_filing_requirements ~67

HPD's rules in plain words: who must file the yearly property registration, the May 21 to September 1 window, who files the December bed bug report, what happens without a valid registration, and who signs. Sourced from HPD's own pages.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_nyc_building ~60

Returns the same facts as lookup_nyc_building for one building, by its HPD building id (the number in Woodpecker's /b/ links and on HPD Online).

NameTypeReqDescription
hpd_building_idintegeryes–

No output schema declared.

No examples provided.

get_woodpecker_price ~55

The flat yearly price for a building with a given number of apartments, what the plan includes, and the renewal price. Buildings with more than 20 apartments are quoted by email.

NameTypeReqDescription
apartmentsintegeryes–

No output schema declared.

No examples provided.

lookup_nyc_building ~126

Finds a New York City residential building in HPD's records by borough, house number and street, and returns its registration status (valid, expired or missing), open filing violations, apartment count and Woodpecker's yearly price for it. Use when the user gives an address.

NameTypeReqDescription
boroughstringyesBrooklyn, Queens, Bronx, Manhattan or Staten Island
house_numberstringyesHouse number as on the building, like 787 or 100-02
streetstringyesStreet name, like East 56 Street or Bushwick Avenue

No output schema declared.

No examples provided.

open_hpd_filing_violations_by_borough ~51

How many NYC buildings currently have an open HPD violation for a missing property registration or a missing annual bed bug report, by borough, counted from the city's open data.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

start_woodpecker_order ~56

Returns the link where the owner of a given building sees the city's record and the price and pays by card. Nothing is created until the owner pays on that page.

NameTypeReqDescription
hpd_building_idintegeryes–

No output schema declared.

No examples provided.

Install

How do I install the Woodpecker: NYC HPD registration lookup MCP server?

Woodpecker: NYC HPD registration lookup is a hosted endpoint at https://woodpecker.help/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 · woodpecker.help

# add to Claude Code
claude mcp add --transport http help-woodpecker-nyc-hpd 'https://woodpecker.help/mcp'
Common questions

What is the Woodpecker: NYC HPD registration lookup MCP server?

Woodpecker: NYC HPD registration lookup is an MCP server listed in the public MCP registry as help.woodpecker/nyc-hpd. NYC building HPD registration status, open filing violations and Woodpecker's yearly price. This page covers its hosted endpoint (https://woodpecker.help/mcp).

Is the Woodpecker: NYC HPD registration lookup MCP server safe to use?

Woodpecker: NYC HPD registration lookup scores 77 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 Woodpecker: NYC HPD registration lookup MCP server expose?

Woodpecker: NYC HPD registration lookup exposes 6 tools: lookup_nyc_building, get_nyc_building, get_woodpecker_price, explain_hpd_filing_requirements, open_hpd_filing_violations_by_borough, start_woodpecker_order. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.

Does the Woodpecker: NYC HPD registration lookup MCP server require authentication?

No. We connected to Woodpecker: NYC HPD registration lookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Woodpecker: NYC HPD registration lookup MCP server still maintained?

Woodpecker: NYC HPD registration lookup 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 Woodpecker: NYC HPD registration lookup MCP server?

VerifyMCP ran 13 checks on Woodpecker: NYC HPD registration lookup, 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.