Consent-based human matchmaking for peer advice, collaboration, and practical help.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://api.lmgram.com/mcp6 tools · 216msget_current_userReturns the LMGram profile linked to the connected account.Returns the LMGram profile linked to the connected account.
No input schema was published for this tool.
request_human_matchinjection riskCreates an opt-in LMGram human match request only after the user explicitly asks to use LMGram to find a collaborator, peer, mentor, or helper. Never invoke for general advice, dating or romantic matchmaking. Never include secrets, credentials, API keys, raw transcripts, customer data, or private d…Creates an opt-in LMGram human match request only after the user explicitly asks to use LMGram to find a collaborator, peer, mentor, or helper. Never invoke for general advice, dating or romantic matchmaking. Never include secrets, credentials, API keys, raw transcripts, customer data, or private d…
summary: Exfiltration-shaped instruction non-sensitive summary. Never send secrets, credentials, API keys, raw transcripts, customer da| Parameter | Type | Description |
|---|---|---|
| topic* | string | Short, non-sensitive title for the practical or professional session topic. Dating and romantic requests are not supported. |
| summary* | string | Minimized non-sensitive summary. Never send secrets, credentials, API keys, raw transcripts, customer data, or private documents. |
| need* | string | The concrete collaborator, peer, mentor, or helper the user explicitly wants. Dating and romantic matching are not supported. |
| matchType | string | — |
| urgency | number | — |
| sensitivity | string | — |
| language | string | — |
| maxCandidates | integer | — |
list_match_requestsLists recent match requests for the current LMGram user, optionally filtered by role and status.Lists recent match requests for the current LMGram user, optionally filtered by role and status.
| Parameter | Type | Description |
|---|---|---|
| role | string | — |
| status | string | Optional exact request status to return. |
| limit | integer | — |
start_chatStarts a LMGram chat for a match request, or records that this side wants to chat.Starts a LMGram chat for a match request, or records that this side wants to chat.
| Parameter | Type | Description |
|---|---|---|
| matchRequestId* | string | — |
| body | string | Optional first message. |
list_messagesLists messages in a LMGram chat. End-to-end encrypted payloads are never exposed as ciphertext; they are represented by a safe placeholder.Lists messages in a LMGram chat. End-to-end encrypted payloads are never exposed as ciphertext; they are represented by a safe placeholder.
| Parameter | Type | Description |
|---|---|---|
| chatId* | string | — |
send_messageSends a message into a LMGram chat.Sends a message into a LMGram chat.
| Parameter | Type | Description |
|---|---|---|
| chatId* | string | — |
| body* | string | — |
6 of 6 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Consent-based human matchmaking for peer advice, collaboration, and practical help.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.