Skip to content

localhum MCP server

app.localhum/localhumlocalhum.appstreamable-httpv1.0.0Scanned

What's on tonight at San Diego's small venues: live music, trivia, comedy, open mics, happy hours.

3 tools: 1 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • 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 localhum MCP server can do

The localhum MCP server is published by localhum.app, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: localhum_venue), but cannot delete data. 2 tools only read.

3 tools bring in text other people can write (localhum_whats_on, localhum_venue and localhum_areas).

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 once 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 1Claude Code: ask
  • localhum_venueLook up one venue by name ("Winstons", "The Casbah", "Pure Project North Park") or its localhum address: where it is, its own website and Instagram, its regular weekly nights and d…Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Look up one venue by name ("Winstons", "The Casbah", "Pure Project North Park") or its localhum address: where it is, its own website and Instagram, its regular weekly nights and deals, and what it has booked in the coming days. When several venues fit the name, returns them to choose from. Its pages are for personal, non-commercial use with their localhum links (localhum.app/terms#use).

    Annotations the server declares

    • title: One venue
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • localhum_areasList the regions and neighbourhoods localhum covers, with what each is also called and how many things are on there in the next seven days.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the regions and neighbourhoods localhum covers, with what each is also called and how many things are on there in the next seven days. Use it to check coverage, or to find an area value for localhum_whats_on. Personal, non-commercial use (localhum.app/terms#use).

    Annotations the server declares

    • title: Areas covered
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • localhum_whats_onFind what's on at San Diego's bars, breweries, clubs, cafes, galleries and small venues from a question in plain words.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Find what's on at San Diego's bars, breweries, clubs, cafes, galleries and small venues from a question in plain words. Use it for questions about events or things to do in San Diego: live music, a band or DJ, trivia, karaoke, comedy, open mics, drag, dance nights, run clubs, markets, classes, happy hours and deals, on a day or in a neighbourhood. Pass the question the way the person said it, place and time included: "live jazz in North Park tonight", "free things to do this weekend", "happy hour near Ocean Beach on Friday", "anything at the Casbah this week". Place, time, the kinds of thing wanted, what to leave out ("not happy hours"), free and for kids are all read from the words, so keep them in and don't rewrite them into keyword lists. A short list works ("comedy or open mic"); for several different wishes, ask once for each. With no place it searches all of Greater San Diego; with no time, the next seven days. It covers San Diego County only (localhum_areas lists every neighbourhood and city); for anywhere else it says so and lists nothing. Returns listings with the day, time, venue, neighbourhood, price when the venue gave one, and a link to each. Several pages of results come with next_offset. Each listing comes with its localhum link; localhum's terms allow personal, non-commercial use with that link (localhum.app/terms#use).

    Annotations the server declares

    • title: What's on
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

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 outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
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 18, 2026, 16:22 UTC, unchanged since Nov 4, 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
1
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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://localhum.app/mcp: tools/list returned 3 tools to an anonymous client, including localhum_venue (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

Install

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

claude mcp add --transport http localhum https://localhum.app/mcp
claude mcp add --transport http localhum https://localhum.app/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__localhum__localhum_whats_on",
      "mcp__localhum__localhum_areas"
    ],
    "ask": [
      "mcp__localhum__localhum_venue"
    ],
    "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 localhum. Review it before you use it.

Capability tags behind 3 rules
  • mcp__localhum__localhum_whats_on untrusted-input
  • mcp__localhum__localhum_venue untrusted-input
  • mcp__localhum__localhum_areas untrusted-input

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/app.localhum/localhum/verify?hash=d5da010af09e8592b8877d038543f5fbfc0aca533f8cc92cbec3b16a79ea7634" | jq -e '.changed == false'

Pinned hash d5da010af09e, from Nov 16, 2026, 14:18 UTC.

Watch

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

https://radar.anlyon.com/servers/app.localhum/localhum/changes.xml

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

Badge

Anlyon Radar badge for app.localhum/localhum
[![Anlyon Radar](https://radar.anlyon.com/badge/app.localhum/localhum.svg)](https://radar.anlyon.com/servers/app.localhum/localhum)

Source: MCP Registry. Synced Nov 3, 2026, 06:17 UTC.

localhum MCP server: questions and answers

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

Is the localhum MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 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 localhum MCP server delete data?

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

Can the localhum 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 localhum MCP server have?

3 tools: 1 write, 2 read. localhum_venue, localhum_whats_on and localhum_areas.

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

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

Does the localhum MCP server send data to outside services?

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

Has the localhum MCP server changed its tools?

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