Skip to content

AddressLore MCP server

io.github.BurettoSofuto/addressloreBurettoSofutostreamable-httpv1.0.0Scanned

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

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the AddressLore MCP server can do

The AddressLore MCP server is published by the GitHub account BurettoSofuto. It has 3 tools. It can create or change data (2 tools: house_history and coverage), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • coverageThe Vancouver local areas, streets, blocks and directory years AddressLore covers: every directory year read with names (each area's extra years said), the years read for the whole…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The Vancouver local areas, streets, blocks and directory years AddressLore covers: every directory year read with names (each area's extra years said), the years read for the whole city, the later years that hold buildings and places only, and the census years, with each local area's count of streets and addresses and its page. Ask again with area for that area's streets, each with its blocks, its own years and its page.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • house_historyWhen 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 whet…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 (with the people, work and employers the 1920, 1930 and 1940 name sections list at the address), and where the 1911, 1921 and 1931 censuses list households at the address, their people, tenure, rent, rooms, origins and birthplaces (1911 gives only the people, origins and birthplaces; 1931 adds 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. A house with more than one answer holds (a hotel or rooming house) answers a summary with every year's count of listings, the latest years in full and each census as its summary; ask again with year for any other directory year or census year.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • find_houseLook up a Vancouver address, a street, a building's name or a resident's surname from 1945 or earlier in AddressLore's coverage.No findings

    Why it is in this group

    • The name "find_house" says "find": a word for reading.
    Description, as the server wrote it
    Look up a Vancouver address, a street, a building's name or a resident's surname from 1945 or earlier in AddressLore's coverage. Returns the matching house's path for house_history; the candidates when the address could be on more than one street ("which street") or matches more than one old address; a street's houses a page at a time with its page; or says plainly that the address isn't covered (never a nearby house in its place), with the nearest covered streets and the coverage page.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:57 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://addresslore.com/mcp: tools/list returned 3 tools to an anonymous client, including house_history (write), coverage (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff
    • Changed:coverageChanges thingsdescriptioninputSchema
    • Changed:find_houseOnly readsdescriptioninputSchema
    • Changed:house_historyChanges thingsdescriptioninputSchema
  2. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http addresslore https://addresslore.com/mcp
claude mcp add --transport http addresslore https://addresslore.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__addresslore__find_house"
    ],
    "ask": [
      "mcp__addresslore__house_history",
      "mcp__addresslore__coverage"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as addresslore. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.BurettoSofuto/addresslore/verify?hash=8766bc44dbb50adf94827bd0075bd729489f0d552ac38b88989e7af07858ab34" | jq -e '.changed == false'

Pinned hash 8766bc44dbb5, from Nov 16, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.BurettoSofuto/addresslore/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.BurettoSofuto/addresslore
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.BurettoSofuto/addresslore.svg)](https://radar.anlyon.com/servers/io.github.BurettoSofuto/addresslore)

Source: MCP Registry. Synced Oct 21, 2026, 18:15 UTC.

AddressLore MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AddressLore MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AddressLore MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the AddressLore MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the AddressLore MCP server have?

3 tools: 2 write, 1 read. house_history, coverage and find_house.

Does the AddressLore MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the AddressLore MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AddressLore MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.