Alpaca Trading API integration for Model Context Protocol (MCP)
Grove Hopper Property Tax Check is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Check any US address for property tax over-assessment: value, appeal deadline, exemptions. No login.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http grove-hopper-property-tax-check-mcp https://www.grovehopper.com/mcp
# 2 — ask your agent for something these tools do
# check_property_tax_assessment, get_property_tax_appeal_deadline, find_property_tax_exemptions and 2 more
Grove Hopper Property Tax Check costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http grove-hopper-property-tax-check-mcp https://www.grovehopper.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Use this when someone asks "is my property tax too high", "is my home over-assessed", "what is my home assessed at", or wants to know if they can appeal the property tax assessment on a specific US address. Works for any US address. Takes a full street address, confirms the property and county, and returns the assessed value with its tax year and source link (read from the official county record w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Full US street address with city and state, for example "745 N 24th St, Philadelphia, PA 19130". |
Use this when someone asks for the "property tax appeal deadline", "when is the last day to appeal my property tax assessment", or where and how to file a property tax appeal. Works for any US address or county. Give a street address, or a county and state. Returns the exact deadline date with days left, the board or office that hears the appeal, the filing method, form and steps, and source links
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | Street address with city and state. Optional if county and state are given. Needed to resolve a township or town. |
| county | string | no | County name, for example "Cook County". Optional if an address is given. |
| state | string | no | US state name or two-letter code, for example "IL". |
| noticeDate | string | no | Mailing date printed on the assessment notice, as YYYY-MM-DD, for places where the deadline runs from the notice date. |
Use this when someone asks about "property tax exemptions for seniors", veteran or disabled-veteran property tax exemptions, disability exemptions, a homestead exemption, or a senior property tax freeze. Works for any US state and county. Takes a state, optionally a county, and the situation (senior, veteran, disabled, homestead). Returns each program with what it does, who qualifies, how and by w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | US state name or two-letter code, for example "Florida" or "FL". |
| county | string | no | County name if known, for example "Broward County". |
| situation | string | no | One of: senior, veteran, disabled, homestead. Free text is fine, for example "65 and retired". |
Use this when someone wants to estimate a property tax bill ("how much is my property tax"), see what a home improvement would add ("does a deck raise property taxes, and by how much"), or see what a successful appeal would save per year. Works for any US address, county or state. Give the assessed value from the tax bill or notice, or a street address and the assessed value is looked up. For the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scenario | string | no | Which calculation to run. Defaults to the one implied by the other fields. |
| address | string | no | Full US street address. Used to look up the assessed value and the local rate when they are not given. |
| state | string | no | US state name or two-letter code. Used for the typical local rate when no rate is given. |
| county | string | no | County name. Used with the state for the typical local rate. |
| assessedValue | number | no | Assessed value in dollars as shown on the tax bill or notice (not necessarily market value). Optional when an address is given. |
| annualTaxBill | number | no | Current annual property tax bill in dollars; used to derive the effective rate. |
| taxRatePercent | number | no | Tax rate in percent, for example 1.8. |
| millRate | number | no | Millage rate in mills per $1,000, for example 18. |
| improvementCost | number | no | Cost of the home improvement in dollars (treated as a ceiling on added assessed value). |
| addedAssessedValue | number | no | Added assessed value from the improvement, if known. |
| newAssessedValue | number | no | Target assessed value after a successful appeal. |
| reductionPercent | number | no | Percent reduction in assessed value after a successful appeal. |
Use this for any general property tax question that is not about one specific address: "how do I appeal my property tax assessment", "does a deck raise property taxes", "does finishing a basement or a kitchen remodel increase property taxes", how assessments and exemptions work, what evidence wins an appeal. Applies to any US state. Returns sourced answers from Grove Hopper county and state guides
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The property tax question in the user's own words. |
| state | string | no | US state name or two-letter code, if the question is local. |
| county | string | no | County name, if the question is local. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Grove Hopper Property Tax Check or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_property_tax_assessment | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_property_tax_appeal_deadline | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| find_property_tax_exemptions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| calculate_property_tax | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| answer_property_tax_question | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Grove Hopper Property Tax Check can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.