io.github.pooriaarab/foreclosurelistings
REMOTE · FORECLOSURELISTINGS.FYI
Where foreclosure sales happen, and who can help, by place.
Available components
Last scanned (23 minutes ago)
Scores higher than 57% of remote servers
Reachable. Last reached 23 Oct 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 Security69
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 428 tokens (~71/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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 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 23 Oct 2026 · Probed https://foreclosurelistings.fyi/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=foreclosurelistings.fyi | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a87e01d4fb8e0b5413daf022e35923e0 |
| SANs: foreclosurelistings.fyi, admin.foreclosurelistings.fyi, *.admin.foreclosurelistings.fyi | ||||||
| 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 foreclosurelistings.fyi. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fyi. | present | 24340 | 8 | Verified |
| foreclosurelistings.fyi. | 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=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com https://js.stripe.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://neeed.directory; font-src 'self' data:; connect-src 'self' https://challenges.cloudflare.com https://api.stripe.com; frame-src https://challenges.cloudflare.com https://js.stripe.com; worker-src 'self' blob:; manifest-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self' https://checkout.stripe.com; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://foreclosurelistings.fyi/mcp | Verified | 200 | |
| http (plaintext) | http://foreclosurelistings.fyi/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_listing ~27
Get one published foreclosure resource by its slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The listing slug. |
No output schema declared.
No examples provided.
get_stats ~27
Get the number of published foreclosure resources, places and categories, and when the data last changed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_categories ~16
List categories with their foreclosure resource counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_places ~19
List countries, regions and cities that have foreclosure resources.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sources ~26
List where the foreclosure resource data comes from, with the license and refresh of each source.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_listings ~217
Search published foreclosure resources by text, place and category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug, from /categories. A parent slug also matches its children. |
| city | string | – | City slug, from /places. |
| country | string | – | ISO 3166-1 alpha-2 country code, any case. A country the directory does not cover, as listed in /places, gives 400. |
| cursor | string | – | `page.nextCursor` from the previous response. Opaque. Send the same filters and `limit`. |
| limit | integer | – | Items per page. |
| q | string | – | Search text, with at least one letter or digit. Matches name, categories, attributes, description and place. Typos fall back to close matches. |
| region | string | – | Region slug, from /places. |
| sort | string | – | `relevance` needs `q` and is the default with it. `name` is the default without `q`. `recent` is newest first. |
No output schema declared.
No examples provided.
How do I install the io.github.pooriaarab/foreclosurelistings MCP server?
io.github.pooriaarab/foreclosurelistings is a hosted endpoint at https://foreclosurelistings.fyi/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 · foreclosurelistings.fyi
claude mcp add --transport http pooriaarab-foreclosurelistings 'https://foreclosurelistings.fyi/mcp'
What is the io.github.pooriaarab/foreclosurelistings MCP server?
io.github.pooriaarab/foreclosurelistings is an MCP server listed in the public MCP registry as io.github.pooriaarab/foreclosurelistings. Where foreclosure sales happen, and who can help, by place. This page covers its hosted endpoint (https://foreclosurelistings.fyi/mcp).
Is the io.github.pooriaarab/foreclosurelistings MCP server safe to use?
io.github.pooriaarab/foreclosurelistings scores 68 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 io.github.pooriaarab/foreclosurelistings MCP server expose?
io.github.pooriaarab/foreclosurelistings exposes 6 tools: search_listings, get_listing, list_places, list_categories, get_stats, list_sources. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.
Does the io.github.pooriaarab/foreclosurelistings MCP server require authentication?
No. We connected to io.github.pooriaarab/foreclosurelistings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.pooriaarab/foreclosurelistings MCP server still maintained?
io.github.pooriaarab/foreclosurelistings is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.