Sagashi
REMOTE · APP.SAGASHI.AU
Checks Sydney homes for sale against a buyer's budget, school zone, commute and area, with reasons.
Available components
Last scanned (21 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 724 tokens (~144/item across 5 items; 5 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 Management3
- Stability check failed: schema churn in the 10 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 (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 →
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.
- 13 Nov 26 −1
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “answer_question” was removed ▼ security
- Tool “list_questions” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “home_details” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 12 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 72
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 21 Nov 2026 · Probed https://app.sagashi.au/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.sagashi.au | CN=WE1,O=Google Trust Services,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d644b44d915caf0e0e9d83ff5e863fcb |
| SANs: app.sagashi.au | ||||||
| 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 app.sagashi.au. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| au. | DS published | 26642 | 8 | Verified |
| sagashi.au. | 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=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https://fonts.gstatic.com;form-action 'self';frame-ancestors 'none';img-src 'self' data: https://*.googleapis.com https://*.gstatic.com *.google.com *.googleusercontent.com;object-src 'none';script-src 'nonce-Z4Q9QKz131LHoqNKE6hTBLnj' 'strict-dynamic' 'self' https: 'unsafe-eval' blob:;script-src-attr 'none';style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;upgrade-insecure-requests;connect-src 'self' https://*.googleapis.com *.google.com https://*.gstatic.com data: blob:;frame-src *.google.com;worker-src blob: |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.sagashi.au/mcp | Verified | 200 | |
| http (plaintext) | http://app.sagashi.au/mcp | HTTPS enforced | 301 | https://app.sagashi.au/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 →
find_homes Find homes that fit ~116
Checks the homes for sale in Sydney that Sagashi holds against a buyer's answers, and returns how many fit and the newest that do, each naming the answers it matched and linking to its source. Set only what the buyer said. Get suburbs from find_suburb, school codes from find_school and a place to travel to from find_place first. A driving or cycling trip is not checked here. Say only what Sagashi returned: when nothing fits, say so, without guesses about the market.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | object | yes | – |
No output schema declared.
No examples provided.
find_place Find a place to travel to ~68
Finds a place in Sydney a buyer travels to, such as a hospital, university or station, with the position find_homes takes in profile.commute. Answers from Sagashi's own list of places.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | What the buyer called it: at least a couple of letters. |
No output schema declared.
No examples provided.
find_school Find a public school ~56
Finds NSW public schools that have an intake zone, by name, with the four-digit codes find_homes takes in profile.schools.zoneSchools.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | What the buyer called it: at least a couple of letters. |
No output schema declared.
No examples provided.
find_suburb Find a suburb ~47
Finds Sydney suburbs by name, spelled as find_homes takes them in profile.about.suburbs.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | What the buyer called it: at least a couple of letters. |
No output schema declared.
No examples provided.
home_details One home in detail ~121
Call this when the buyer picks, compares or asks about a home find_homes returned, before answering about its schools, childcare, who lives nearby, safety, development or sales nearby: find_homes gives only what each home matched. Pass the same answers and the home's id. Returns its facts, school zones and nearest schools, childcare in its suburb, who lives nearby, recorded crime, development applications nearby and recent sales nearby.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id of a home find_homes returned for the same answers. |
| profile | object | yes | – |
No output schema declared.
No examples provided.
How do I install the Sagashi MCP server?
Sagashi is a hosted endpoint at https://app.sagashi.au/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 · app.sagashi.au
claude mcp add --transport http au-sagashi-sagashi 'https://app.sagashi.au/mcp'
What is the Sagashi MCP server?
Sagashi is an MCP server listed in the public MCP registry as au.sagashi/sagashi. Checks Sydney homes for sale against a buyer's budget, school zone, commute and area, with reasons. This page covers its hosted endpoint (https://app.sagashi.au/mcp).
Is the Sagashi MCP server safe to use?
Sagashi scores 71 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 Sagashi MCP server expose?
Sagashi exposes 5 tools: find_homes, home_details, find_suburb, find_school, find_place. Their descriptions and schemas cost roughly 408 tokens of context every time the server is loaded.
Does the Sagashi MCP server require authentication?
No. We connected to Sagashi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sagashi MCP server still maintained?
Sagashi 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 Sagashi MCP server?
VerifyMCP ran 13 checks on Sagashi, 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.