AddressLore
REMOTE · ADDRESSLORE.COM
Vancouver house histories by address: who lived there each year to 1945, permits and the 1912 map.
Available components
Last scanned (21 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 4 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. 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 Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 422 tokens (~140/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 Management47
- Stability observed for 14 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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 Nov 26 +7
- HTTPS: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Tool “house_history” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 1 Nov 26 +1
- Tool “house_history” rewrote its description, which is the text the model reads security
- 29 Oct 26 +1
- Tool “house_history” rewrote its description, which is the text the model reads security
- 27 Oct 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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 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.
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 Nov 2026 · Probed https://addresslore.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=addresslore.com | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a60cccb9f0ef547a13e1f8dabb5daf57 |
| SANs: addresslore.com, *.addresslore.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 addresslore.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| addresslore.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=86400 |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://addresslore.com/mcp | Verified | 200 | |
| http (plaintext) | http://addresslore.com/mcp | HTTPS enforced | 301 | https://addresslore.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 →
coverage What AddressLore covers ~25
The Vancouver streets, blocks and directory years AddressLore covers, with each street's page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_house Find a house ~86
Look up a Vancouver address, or a resident's surname from 1945 or earlier, in AddressLore's coverage. Returns the matching house's path for house_history, or says plainly that the address isn't covered (never a nearby house in its place), with the covered streets.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | An address ("526 Keefer Street") or a surname ("Clandenning"). |
No output schema declared.
No examples provided.
house_history A house's history ~219
When a covered Vancouver house was built and what stood there: the building permit (1901–1930) and the City's year built, what the 1912 fire insurance map draws on the lot and whether today's building is very likely that one, what stands today, and who lived there in each directory year with each listing's source page, and where the 1921 and 1931 censuses list households at the address, their people, tenure, rent, rooms, origins and birthplaces (and in 1931 the home's value and a radio) as counts, and in 1921 the people by name as Library and Archives Canada's index gives them, each with its LAC record link. Residents' names through 1945 only; later years show a household and job without names. Anything inferred is marked inferred.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | A Vancouver street address as written today or in the directories ("620 Keefer St", "2649 Yew"), an AddressLore house path ("620-keefer") or its URL. |
No output schema declared.
No examples provided.
How do I install the AddressLore MCP server?
AddressLore is a hosted endpoint at https://addresslore.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 · addresslore.com
claude mcp add --transport http burettosofuto-addresslore 'https://addresslore.com/mcp'
What is the AddressLore MCP server?
AddressLore is an MCP server listed in the public MCP registry as io.github.BurettoSofuto/addresslore. Vancouver house histories by address: who lived there each year to 1945, permits and the 1912 map. This page covers its hosted endpoint (https://addresslore.com/mcp).
Is the AddressLore MCP server safe to use?
AddressLore scores 79 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 AddressLore MCP server expose?
AddressLore exposes 3 tools: find_house, house_history, coverage. Their descriptions and schemas cost roughly 330 tokens of context every time the server is loaded.
Does the AddressLore MCP server require authentication?
No. We connected to AddressLore without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AddressLore MCP server still maintained?
AddressLore is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.