HortOS (United States)
REMOTE · US.HORTOSAPP.COM · SCANNED OCT 4
Search US wholesale plant growers' live availability lists and price a whole plant list. Read-only.
Available components
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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 439 tokens (~219/item across 2 items; 2 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 Management30
- Stability observed for 9 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 2 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the HortOS (United States) MCP server?
HortOS (United States) is a hosted endpoint at https://us.hortosapp.com/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 · us.hortosapp.com
claude mcp add --transport http com-hortosapp-us 'https://us.hortosapp.com/mcp'
{
"mcpServers": {
"com-hortosapp-us": {
"url": "https://us.hortosapp.com/mcp"
}
}
} {
"servers": {
"com-hortosapp-us": {
"type": "http",
"url": "https://us.hortosapp.com/mcp"
}
}
} [mcp_servers.com-hortosapp-us] url = "https://us.hortosapp.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-hortosapp-us": {
"type": "remote",
"url": "https://us.hortosapp.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-hortosapp-us --url 'https://us.hortosapp.com/mcp' --transport streamable-http
mcp_servers:
com-hortosapp-us:
url: "https://us.hortosapp.com/mcp" {
"McpServers": {
"com-hortosapp-us": {
"Transport": "http",
"Url": "https://us.hortosapp.com/mcp"
}
}
} assistant mcp add com-hortosapp-us -t streamable-http -u 'https://us.hortosapp.com/mcp'
{
"mcpServers": {
"com-hortosapp-us": {
"type": "http",
"url": "https://us.hortosapp.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
- Tool “price_plant_list” rewrote its description, which is the text the model reads security
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 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.
- 26 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Sept 26 65
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 4 Oct 2026 · Probed https://us.hortosapp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hortosapp.com | CN=WE1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 321637c758ce5d960e289d3e46e8ef53 |
| SANs: hortosapp.com, *.hortosapp.com | ||||||
| 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 us.hortosapp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hortosapp.com. | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), 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://us.hortosapp.com/mcp | Verified | 200 | |
| http (plaintext) | http://us.hortosapp.com/mcp | HTTPS enforced | 308 | https://us.hortosapp.com/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 →
price_plant_list Price a plant list ~159
Price a whole plant list or planting schedule from wholesale growers' live stock lists: each line matched to a grower, size and trade price, with the growers near the job preferred. Returns the priced lines and a link to the priced list on HortOS, which the person opens, checks and sends themselves. This tool does not place an order.
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | – | Optional: a name for the job or site. |
| list | string | yes | The plant list as text, one plant per line with quantity, name and pot size, e.g. '40 x Lomandra Tanika 140mm'. |
| near | string | – | Optional: the job's suburb, town or postcode, so growers near the job are used. |
No output schema declared.
No examples provided.
search_plants Search wholesale plants ~150
Search America's live wholesale plant market: which wholesale growers list a plant, in which pot sizes, and from what trade price (USD, ex tax). Use it for "who grows X" or "what does X cost wholesale". Botanical or common names both work.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Plant name, botanical or common, e.g. 'Lomandra Tanika' or 'lilly pilly'. |
| size | string | – | Optional pot size, e.g. 3G, 15G, 24" Box, Liners or Field Grown. |
| state | string | – | Optional state or province code to limit growers, e.g. QLD, NSW, FL. |
No output schema declared.
No examples provided.
What is the HortOS (United States) MCP server?
HortOS (United States) is an MCP server listed in the public MCP registry as com.hortosapp/us. Search US wholesale plant growers' live availability lists and price a whole plant list. Read-only. This page covers its hosted endpoint (https://us.hortosapp.com/mcp).
Is the HortOS (United States) MCP server safe to use?
HortOS (United States) scores 76 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 HortOS (United States) MCP server expose?
HortOS (United States) exposes 2 tools: search_plants, price_plant_list. Their descriptions and schemas cost roughly 309 tokens of context every time the server is loaded.
Does the HortOS (United States) MCP server require authentication?
No. We connected to HortOS (United States) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HortOS (United States) MCP server still maintained?
HortOS (United States) is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.