# Linkame (remote · linkame.events)

Access authorized Linkame contacts, profiles, events, tickets and matching results.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `linkame.events`: 79/100 (this document), [markdown](https://verifymcp.io/servers/ohdonpiano-linkame/linkame.md), [page](https://verifymcp.io/servers/ohdonpiano-linkame/linkame)

## Channel facts

- Endpoint: `https://linkame.events/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.8.0`

## 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-11-05.

- **Endpoint Security**: 100/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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1197 tokens (~47/item across 25 items; 25 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Linkame MCP server?

Linkame is a hosted endpoint at https://linkame.events/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.

### Claude

```bash
claude mcp add --transport http ohdonpiano-linkame 'https://linkame.events/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ohdonpiano-linkame": {
      "url": "https://linkame.events/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ohdonpiano-linkame": {
      "type": "http",
      "url": "https://linkame.events/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ohdonpiano-linkame]
url = "https://linkame.events/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ohdonpiano-linkame": {
      "type": "remote",
      "url": "https://linkame.events/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ohdonpiano-linkame --url 'https://linkame.events/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ohdonpiano-linkame:
    url: "https://linkame.events/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ohdonpiano-linkame": {
      "Transport": "http",
      "Url": "https://linkame.events/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ohdonpiano-linkame -t streamable-http -u 'https://linkame.events/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ohdonpiano-linkame": {
      "type": "http",
      "url": "https://linkame.events/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-11-05 (score 79, +1)

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

### 2026-11-03 (score 78, +1)

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

### 2026-10-31 (score 77, +1)

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

### 2026-10-29 (score 76, +1)

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

### 2026-10-27 (score 75, +1)

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

### 2026-10-25 (score 74, +1)

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

### 2026-10-24 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 73)

First indexed and scored.

## MCP tools (25)

### `account.get_current_user` (~23 tokens)

Restituisce il profilo base dell’utente autenticato.

### `profile.get_me` (~23 tokens)

Restituisce i profili Linkame dell’utente autenticato.

### `contacts.search` (~68 tokens)

Cerca nella rubrica dell’utente per nome, azienda, ruolo, email, tag o note. Supporta paginazione con limit e offset.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `pageToken` (string)
- `query` (string, required)

### `contacts.get` (~32 tokens)

Restituisce un contatto della rubrica usando il suo identificatore stabile.

Input parameters:

- `contactId` (string, required)

### `contacts.list_groups` (~30 tokens)

Restituisce i gruppi di contatti dell’utente, inclusi gli inviti pendenti.

### `contacts.get_timeline` (~63 tokens)

Restituisce la timeline di un contatto della rubrica. Supporta paginazione con limit e offset.

Input parameters:

- `contactId` (string, required)
- `limit` (integer)
- `offset` (integer)
- `pageToken` (string)

### `contacts.add_note` (~63 tokens)

Aggiunge una nota a un contatto. Richiede conferma esplicita e una idempotency key.

Input parameters:

- `confirm` (required)
- `contactId` (string, required)
- `idempotencyKey` (string, required)
- `text` (string, required)

### `events.list` (~52 tokens)

Elenca gli eventi pubblicati visibili all’utente. Supporta paginazione con limit e offset.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `pageToken` (string)

### `events.get` (~33 tokens)

Restituisce i dettagli di un evento pubblicato o gestito dall’utente.

Input parameters:

- `eventId` (string, required)

### `events.list_my_registrations` (~58 tokens)

Elenca gli eventi ai quali l’utente risulta registrato. Supporta paginazione con limit e offset.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `pageToken` (string)

### `events.list_my_tickets` (~65 tokens)

Elenca i biglietti posseduti o trasferiti all’utente senza esporre il QR. Supporta paginazione con limit e offset.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `pageToken` (string)

### `events.get_my_ticket` (~50 tokens)

Restituisce un biglietto dell’utente. Il QR viene incluso solo se richiesto esplicitamente.

Input parameters:

- `includeQrCode` (boolean)
- `ticketId` (string, required)

### `events.get_matching_status` (~37 tokens)

Restituisce lo stato dell’ultimo matching dell’utente, eventualmente filtrato per evento.

Input parameters:

- `eventId` (string)

### `events.get_matching_results` (~33 tokens)

Restituisce i risultati dell’ultimo matching completato dell’utente.

Input parameters:

- `eventId` (string)

### `organizer.events.list_managed` (~52 tokens)

Elenca gli eventi gestiti dall’organizzatore o dal super admin con stato e date.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `pageToken` (string)

### `organizer.events.get_dashboard` (~34 tokens)

Restituisce il riepilogo operativo aggiornato di un evento gestito.

Input parameters:

- `eventId` (string, required)

### `organizer.events.get_registrations` (~59 tokens)

Elenca le registrazioni paginando i partecipanti di un evento gestito.

Input parameters:

- `eventId` (string, required)
- `limit` (integer)
- `offset` (integer)
- `pageToken` (string)

### `organizer.events.get_ticketing_summary` (~39 tokens)

Restituisce riepilogo ticket, quantità vendute, assegnazioni e check-in.

Input parameters:

- `eventId` (string, required)

### `organizer.events.get_sessions` (~37 tokens)

Restituisce agenda, capienza e prenotazioni sessione di un evento gestito.

Input parameters:

- `eventId` (string, required)

### `organizer.events.get_matching_status` (~37 tokens)

Restituisce configurazione, stato e conteggi del matching di un evento gestito.

Input parameters:

- `eventId` (string, required)

### `organizer.events.get_support_tickets` (~67 tokens)

Elenca i ticket di supporto dell’evento con filtro stato e paginazione.

Input parameters:

- `eventId` (string, required)
- `limit` (integer)
- `offset` (integer)
- `pageToken` (string)
- `status` (string)

### `organizer.events.get_support_ticket` (~43 tokens)

Restituisce un ticket di supporto dell’evento e la conversazione.

Input parameters:

- `eventId` (string, required)
- `ticketId` (string, required)

### `organizer.support_tickets.list_all` (~64 tokens)

Elenca i ticket di supporto di qualsiasi evento; solo super admin.

Input parameters:

- `eventId` (string)
- `limit` (integer)
- `offset` (integer)
- `pageToken` (string)
- `status` (string)

### `organizer.events.reply_support_ticket` (~66 tokens)

Risponde a un ticket di supporto con conferma e idempotency key.

Input parameters:

- `confirm` (required)
- `eventId` (string, required)
- `idempotencyKey` (string, required)
- `text` (string, required)
- `ticketId` (string, required)

### `organizer.events.update_support_ticket_status` (~69 tokens)

Cambia lo stato di un ticket di supporto con conferma e idempotency key.

Input parameters:

- `confirm` (required)
- `eventId` (string, required)
- `idempotencyKey` (string, required)
- `status` (string, required)
- `ticketId` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 76
- 2026-10-29: 76
- 2026-10-28: 75
- 2026-10-27: 75
- 2026-10-26: 74
- 2026-10-25: 74
- 2026-10-24: 73
- 2026-10-23: 73

## Common questions

### What is the Linkame MCP server?

Linkame is an MCP server listed in the public MCP registry as io.github.ohdonpiano/linkame. Access authorized Linkame contacts, profiles, events, tickets and matching results. This page covers its hosted endpoint (https://linkame.events/mcp).

### Is the Linkame MCP server safe to use?

Linkame scores 79 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 Linkame MCP server expose?

Linkame exposes 25 tools: account.get_current_user, profile.get_me, contacts.search, contacts.get, contacts.list_groups, and 20 more. Their descriptions and schemas cost roughly 1,197 tokens of context every time the server is loaded.

### Does the Linkame MCP server require authentication?

Yes. Linkame asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Linkame MCP server still maintained?

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

## Links

- Remote endpoint: https://linkame.events/mcp
- Repository: https://github.com/ohdonpiano/linkame
- Website: https://github.com/ohdonpiano/linkame/blob/main/doc/MCP_PUBLICATION.md
- Changelog RSS feed: https://verifymcp.io/servers/ohdonpiano-linkame/linkame.xml
- Changelog JSON feed: https://verifymcp.io/servers/ohdonpiano-linkame/linkame.json
- HTML version of this page: https://verifymcp.io/servers/ohdonpiano-linkame/linkame