AddressLore

io.github.BurettoSofutoPublished by GitHub account BurettoSofutov1.0.0Updated Oct 27, 2026

Vancouver house histories by address: who lived there each year to 1945, permits and the 1912 map.

VerifiedStreamable HTTPWeb executableLocation & LifestyleKnowledge & Memory

Overview

AI-generated overview

Remote MCP server for Vancouver house histories: look up an address or early resident's surname and get permits, the 1912 fire map and directory residents to…

What you can do
  • Resolve a Vancouver address, or a resident's surname from 1945 or earlier, to a covered house, or say plainly that the address is not covered along with the streets that are.
  • Retrieve a house's history: when it was built, the building permit (1901–1930), the City's year built, what the 1912 fire insurance map draws on the lot, whether today's building is likely that one, what stands today, and who lived there in each directory year.
  • List the streets, blocks and directory years covered, with each street's page.
When to use it
Useful for local history, genealogy or heritage research on Vancouver houses, or when someone wants to know who lived at an address before 1945 and how the building came about. Coverage is limited to Vancouver, so it is not a general address or property lookup.
Requirements
A remote streamable HTTP endpoint at addresslore.com; no package, environment variables or headers are declared. No authentication is declared, and the provider lists a web-executable option.
Before you install
The data is historical and Vancouver-specific, and the tool notes that a match is never substituted with a nearby house, so uncovered addresses return nothing. No credentials, payments or write actions are declared.

Installation

In SourceWeft

  1. Open AddressLore in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.BurettoSofuto%2Faddresslore/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "addresslore": {
      "type": "http",
      "url": "https://addresslore.com/mcp"
    }
  }
}

Tools

3

find_house

Find a house

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.

Parametersqueryrequired

house_history

A house's history

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. Residents' names through 1945 only; later years show a household and job without names. Anything inferred is marked inferred.

Parametersaddressrequired

coverage

What AddressLore covers

The Vancouver streets, blocks and directory years AddressLore covers, with each street's page.

Takes no parameters.

Version history

1
  1. v1.0.0LatestOct 21, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.