LMGram
REMOTE · API.LMGRAM.COM · SCANNED AUG 3
Consent-based human matchmaking for peer advice, collaboration, and practical help.
Available components
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 →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 286 tokens (~40/item across 7 items; 6 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 27% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.lmgram.com
claude mcp add --transport http saezbaldo-lmgram https://api.lmgram.com/mcp
[mcp_servers.saezbaldo-lmgram] url = "https://api.lmgram.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"saezbaldo-lmgram": {
"type": "remote",
"url": "https://api.lmgram.com/mcp",
"enabled": true
}
}
} openclaw mcp add saezbaldo-lmgram --url https://api.lmgram.com/mcp --transport streamable-http
mcp_servers:
saezbaldo-lmgram:
url: "https://api.lmgram.com/mcp" {
"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.
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.
- 2 Aug 26 +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.
- 31 Jul 26 +5
- 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
- 29 Jul 26 +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.
- 27 Jul 26 +1
- 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 61
First indexed and scored.
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 3 Aug 2026 · Probed https://api.lmgram.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lmgram.com | CN=WR3,O=Google Trust Services,C=US | 27 Jul 2026 | 25 Oct 2026 | RSA 2048 | SHA256-RSA | 269714ec8a6a6b030ac322fd7490cea1 |
| SANs: lmgram.com, www.lmgram.com, app.lmgram.com, api.lmgram.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of api.lmgram.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lmgram.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.lmgram.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://api.lmgram.com/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://api.lmgram.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.lmgram.com/mcp |
| Authorisation server | https://api.lmgram.com |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.lmgram.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.lmgram.com/mcp | Served over HTTP | 200 |
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.
get_current_user Get current LMGram profile ~20
Returns the LMGram profile linked to the connected account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_match_requests List LMGram match requests ~34
Lists recent match requests for the current LMGram user.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| role | string | — | — |
No output schema declared.
No examples provided.
list_messages List chat messages ~24
Lists messages in a LMGram chat.
| Name | Type | Req | Description |
|---|---|---|---|
| chatId | string | yes | — |
No output schema declared.
No examples provided.
request_human_match Request a human match ~111
Creates an opt-in LMGram human match request from a minimized session summary.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | — | — |
| matchType | string | — | — |
| maxCandidates | integer | — | — |
| need | string | yes | The concrete human connection the user wants. |
| sensitivity | string | — | — |
| summary | string | yes | Minimized summary. Do not send raw transcripts, secrets or private documents. |
| topic | string | yes | Short title for the current session topic. |
| urgency | number | — | — |
No output schema declared.
No examples provided.
send_message Send a chat message ~32
Sends a message into a LMGram chat.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | — |
| chatId | string | yes | — |
No output schema declared.
No examples provided.
start_chat Start or request a chat ~46
Starts a LMGram chat for a match request, or records that this side wants to chat.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | — | Optional first message. |
| matchRequestId | string | yes | — |
No output schema declared.
No examples provided.