# LMGram (remote · api.lmgram.com)

Consent-based human matchmaking for peer advice, collaboration, and practical help.

- Trust score: 69/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.lmgram.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/saezbaldo-lmgram/api.md), [page](https://verifymcp.io/servers/saezbaldo-lmgram/api)

## Channel facts

- Endpoint: `https://api.lmgram.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 286 tokens (~40/item across 7 items; 6 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 27% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http saezbaldo-lmgram https://api.lmgram.com/mcp
```

### Codex

```toml
[mcp_servers.saezbaldo-lmgram]
url = "https://api.lmgram.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "saezbaldo-lmgram": {
      "type": "remote",
      "url": "https://api.lmgram.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add saezbaldo-lmgram --url https://api.lmgram.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  saezbaldo-lmgram:
    url: "https://api.lmgram.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "saezbaldo-lmgram": {
      "type": "http",
      "url": "https://api.lmgram.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (6)

### `get_current_user` (~20 tokens)

Get current LMGram profile

Returns the LMGram profile linked to the connected account.

### `request_human_match` (~111 tokens)

Request a human match

Creates an opt-in LMGram human match request from a minimized session summary.

Input parameters:

- `language` (string)
- `matchType` (string)
- `maxCandidates` (integer)
- `need` (string, required): The concrete human connection the user wants.
- `sensitivity` (string)
- `summary` (string, required): Minimized summary. Do not send raw transcripts, secrets or private documents.
- `topic` (string, required): Short title for the current session topic.
- `urgency` (number)

### `list_match_requests` (~34 tokens)

List LMGram match requests

Lists recent match requests for the current LMGram user.

Input parameters:

- `limit` (integer)
- `role` (string)

### `start_chat` (~46 tokens)

Start or request a chat

Starts a LMGram chat for a match request, or records that this side wants to chat.

Input parameters:

- `body` (string): Optional first message.
- `matchRequestId` (string, required)

### `list_messages` (~24 tokens)

List chat messages

Lists messages in a LMGram chat.

Input parameters:

- `chatId` (string, required)

### `send_message` (~32 tokens)

Send a chat message

Sends a message into a LMGram chat.

Input parameters:

- `body` (string, required)
- `chatId` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/saezbaldo-lmgram/api#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 69
- 2026-08-01: 68
- 2026-07-31: 68
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://api.lmgram.com/mcp
- Website: https://lmgram.com/
- Changelog RSS feed: https://verifymcp.io/servers/saezbaldo-lmgram/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/saezbaldo-lmgram/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/saezbaldo-lmgram/api