io.github.peterskotte123/lowball
NPM · @LOWBALL/MCP
What to offer on a Zillow rental: nearby asks, real days listed, cuts, a message. Not affiliated.
Available components
Last scanned (14 hours ago)
Scores higher than 51% of npm servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 565 tokens (~188/item across 3 items; 3 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 Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 54% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 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.
- 12 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.
- 10 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.
- 9 Nov 26 +5
- Source repository: unverified → pass ▲ security
- 8 Nov 26 −4
- Provenance: pass → unverified ▼ security
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 · Analysed npm/@lowball/mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_rent ~190
Check a Zillow rental listing before you apply: what similar rentals nearby ask, how long it has really been listed (Zillow's counter resets on a relist), whether and how much it has been cut, what empty weeks cost the landlord, an offer, a likely settling point, and a message to send. Takes a Zillow listing link or its numeric id. Works best in San Diego County; elsewhere it uses the listings Lowball has seen nearby. Estimates, never a guarantee. Not affiliated with Zillow. Docs: https://github.com/peterskotte123/lowball-plugin#readme
| Name | Type | Req | Description |
|---|---|---|---|
| autopay | boolean | – | Add an autopay line to the message. |
| lease_months | integer | – | Lease term to put in the message. Default 12. |
| url | string | yes | A zillow.com/homedetails/... link, or the numeric zpid from it. |
No output schema declared.
No examples provided.
renewal ~189
Price a lease renewal increase: compares the proposed rent with what similar rentals nearby ask and what the landlord loses if the tenant leaves, and returns a counter and the reasons. Takes current rent, proposed rent, and ZIP; bedrooms, tenure in years, and any free months sharpen it.
| Name | Type | Req | Description |
|---|---|---|---|
| baths | number | – | – |
| beds | number | – | – |
| current_rent | number | yes | – |
| is_complex | boolean | – | – |
| months_free | number | – | Free months on the lease now ending. |
| new_months_free | number | – | Free months offered to new renters today. |
| new_rent | number | – | Rent asked of new renters for the same unit today. |
| proposed_rent | number | yes | – |
| sqft | number | – | – |
| type | string | – | – |
| years | number | – | Years the tenant has lived there. |
| zip | string | yes | – |
No output schema declared.
No examples provided.
score_rental ~186
Same check as check_rent, for a rental you describe yourself (when the Zillow lookup is capped, the listing is off Zillow, or you only know the numbers). Needs the monthly rent and a US ZIP; bedrooms, bathrooms, square feet, days listed and property type sharpen it.
| Name | Type | Req | Description |
|---|---|---|---|
| baths | number | – | – |
| beds | number | – | Bedrooms (0 for a studio). |
| days | integer | – | Days the listing has been up. |
| is_complex | boolean | – | True for a unit in a managed apartment building. |
| lease_months | integer | – | – |
| price | number | yes | Monthly rent asked, in dollars. |
| sqft | number | – | – |
| type | string | – | SINGLE_FAMILY, CONDO, TOWNHOUSE, APARTMENT, or MULTI_FAMILY. |
| zip | string | yes | 5-digit US ZIP code. |
No output schema declared.
No examples provided.
How do I install the io.github.peterskotte123/lowball MCP server?
io.github.peterskotte123/lowball runs locally as an npm package, launched with npx -y @lowball/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @lowball/mcp
claude mcp add peterskotte123-lowball -- npx -y @lowball/mcp
What is the io.github.peterskotte123/lowball MCP server?
io.github.peterskotte123/lowball is an MCP server listed in the public MCP registry as io.github.peterskotte123/lowball. What to offer on a Zillow rental: nearby asks, real days listed, cuts, a message. Not affiliated. This page covers its npm package (@lowball/mcp).
Is the io.github.peterskotte123/lowball MCP server safe to use?
io.github.peterskotte123/lowball scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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.peterskotte123/lowball MCP server expose?
io.github.peterskotte123/lowball exposes 3 tools: check_rent, score_rental, renewal. Their descriptions and schemas cost roughly 565 tokens of context every time the server is loaded.
Is the io.github.peterskotte123/lowball MCP server still maintained?
io.github.peterskotte123/lowball 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 licence is the io.github.peterskotte123/lowball MCP server under?
io.github.peterskotte123/lowball declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.peterskotte123/lowball MCP server?
VerifyMCP ran 16 checks on io.github.peterskotte123/lowball, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.