Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BMLT Meetings

REMOTE · MCP.BMLT.APP · SCANNED SEP 24

Search Narcotics Anonymous meetings worldwide via the BMLT directory.

Available components

0 this week 77 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1193 tokens (~198/item across 6 items; 6 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the BMLT Meetings MCP server?

BMLT Meetings is a hosted endpoint at https://mcp.bmlt.app/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 · mcp.bmlt.app

# add to Claude Code
claude mcp add --transport http bmlt-enabled-bmlt-server-mcp 'https://mcp.bmlt.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "bmlt-enabled-bmlt-server-mcp": {
      "url": "https://mcp.bmlt.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "bmlt-enabled-bmlt-server-mcp": {
      "type": "http",
      "url": "https://mcp.bmlt.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.bmlt-enabled-bmlt-server-mcp]
url = "https://mcp.bmlt.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bmlt-enabled-bmlt-server-mcp": {
      "type": "remote",
      "url": "https://mcp.bmlt.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bmlt-enabled-bmlt-server-mcp --url 'https://mcp.bmlt.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  bmlt-enabled-bmlt-server-mcp:
    url: "https://mcp.bmlt.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "bmlt-enabled-bmlt-server-mcp": {
      "Transport": "http",
      "Url": "https://mcp.bmlt.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add bmlt-enabled-bmlt-server-mcp -t streamable-http -u 'https://mcp.bmlt.app/mcp'
// mcp.json
{
  "mcpServers": {
    "bmlt-enabled-bmlt-server-mcp": {
      "type": "http",
      "url": "https://mcp.bmlt.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 26 Aug 26 77
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 24 Sept 2026 · Probed https://mcp.bmlt.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.bmlt.app CN=YE2,O=Let's Encrypt,C=US 14 Sept 2026 13 Dec 2026 ECDSA 256 ECDSA-SHA384 51b2a643281e9de47a1585986bf6a714e00
SANs: mcp.bmlt.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.bmlt.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
bmlt.app. 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
content-security-policy upgrade-insecure-requests

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.bmlt.app/mcp Verified 200
http (plaintext) http://mcp.bmlt.app/mcp HTTPS enforced 301 https://mcp.bmlt.app/mcp
MCP tools · 6 exposed · ~989 tokens

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 →

Tool Tokens
get_meeting ~58

Fetch the full record for a single meeting by its BMLT id_bigint.

NameTypeReqDescription
idintegeryesBMLT meeting id_bigint.
root_server_urlstring–Override the configured BMLT root server URL.

No output schema declared.

No examples provided.

get_server_info ~45

Return capabilities, version, languages, and default coordinates for a BMLT root server.

NameTypeReqDescription
root_server_urlstring–Override the configured BMLT root server URL.

No output schema declared.

No examples provided.

list_formats ~151

List available meeting formats (Open, Closed, Speaker, Beginners, language tags, etc.) so the caller can map human-friendly format names to BMLT format IDs.

NameTypeReqDescription
format_idsarray–Restrict to specific format IDs.
include_unusedboolean–Include formats not currently assigned to any meeting. Default false.
key_stringsarray–Restrict to formats matching these short codes (e.g. ["O", "C", "SP"]).
languagestring–Language code for format names (e.g. "en", "es", "fr"). Defaults to server default.
root_server_urlstring–Override the configured BMLT root server URL.

No output schema declared.

No examples provided.

list_root_servers ~58

List public BMLT root servers known to the BMLT aggregator. Use the returned root_server_url values with other tools to query a specific server.

NameTypeReqDescription
name_containsstring–Case-insensitive substring filter applied to the server name.

No output schema declared.

No examples provided.

list_service_bodies ~115

List BMLT service bodies (zones, regions, areas, groups). Useful for translating "Northern California Region" to a service body ID for use with search_meetings.

NameTypeReqDescription
include_childrenboolean–Also include child service bodies of the requested IDs.
include_parentsboolean–Also include parent service bodies of the requested IDs.
root_server_urlstring–Override the configured BMLT root server URL.
service_body_idsarray–Restrict to specific service body IDs.

No output schema declared.

No examples provided.

search_meetings ~562

Search Narcotics Anonymous meetings on a BMLT root server. Filter by location (address or lat/lng + radius), weekday, time of day, format, venue type (in-person / virtual / hybrid), and service body. Returns a trimmed summary by default; pass data_format='full' for the raw BMLT response.

NameTypeReqDescription
addressstring–Free-form address to search near (geocoded server-side). Ignored if latitude+longitude are provided.
data_formatstring–"summary" returns a curated subset of fields (default). "full" returns the raw BMLT response.
format_idsarray–BMLT format IDs to require. Use list_formats to discover IDs (e.g. Open, Closed, Speaker, Beginners).
languagestring–Language code for format names (e.g. "en", "es", "de", "fr").
latitudenumber–Latitude in decimal degrees. Pair with longitude for an exact-coordinate search.
longitudenumber–Longitude in decimal degrees. Pair with latitude for an exact-coordinate search.
pageinteger–Page number (1-indexed). Used with page_size.
page_sizeinteger–Results per page. Omit to return all matches.
radius_kmnumber–Search radius in kilometers. Takes precedence over radius_miles when both are provided. Ignored when no coordinates are provided.
radius_milesnumber–Search radius in miles. Defaults to 10. Ignored if radius_km is provided or no coordinates are given.
recursive_servicesboolean–When service_body_ids is set, also include their children. Default true.
root_server_urlstring–Override the configured BMLT root server URL. Must be allowlisted unless BMLT_ALLOW_ANY_ROOT=true.
search_textstring–Free-text search across meeting name, location, and notes.
service_body_idsarray–Restrict to specific service bodies (regions/areas). Use list_service_bodies to discover IDs.
starts_afterstring–Earliest start time as 24h "HH:MM" (e.g. "18:00").
starts_beforestring–Latest start time as 24h "HH:MM" (e.g. "21:30").
venue_typesarray–Venue type filter. 1=In-person, 2=Virtual, 3=Hybrid.
weekdaysarray–Weekday filter. 1=Sunday, 2=Monday, ..., 7=Saturday. Example: [2,4,6] for Mon/Wed/Fri.

No output schema declared.

No examples provided.

Common questions

What is the BMLT Meetings MCP server?

BMLT Meetings is an MCP server listed in the public MCP registry as io.github.bmlt-enabled/bmlt-server-mcp. Search Narcotics Anonymous meetings worldwide via the BMLT directory. This page covers its hosted endpoint (https://mcp.bmlt.app/mcp).

Is the BMLT Meetings MCP server safe to use?

BMLT Meetings scores 77 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 BMLT Meetings MCP server expose?

BMLT Meetings exposes 6 tools: search_meetings, get_meeting, list_formats, list_service_bodies, get_server_info, list_root_servers. Their descriptions and schemas cost roughly 989 tokens of context every time the server is loaded.

Does the BMLT Meetings MCP server require authentication?

No. We connected to BMLT Meetings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BMLT Meetings MCP server still maintained?

BMLT Meetings is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.