Linkame
REMOTE · LINKAME.EVENTS
Access authorized Linkame contacts, profiles, events, tickets and matching results.
Available components
Last scanned (21 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 4 Nov 2026.
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 Security100
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1197 tokens (~47/item across 25 items; 25 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 3 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 73
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 4 Nov 2026 · Probed https://linkame.events/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=linkame.events | CN=WR3,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | RSA 2048 | SHA256-RSA | b9f9d4f41066cd0e0a0af877445a3df1 |
| SANs: linkame.events | ||||||
| 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 |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of linkame.events. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| events. | present | 56837 | 8 | Verified |
| linkame.events. | present | 50972 | 13 | Verified |
| linkame.events. | Verified address RRset verified with the apex keys |
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://linkame.events/mcp/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://linkame.events/mcp/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31556926 |
Protected resource metadata
| Document | https://linkame.events/mcp/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://linkame.events/mcp |
| Authorisation server | https://linkame.events/mcp |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://linkame.events/mcp | Verified | 200 | |
| http (plaintext) | http://linkame.events/mcp | HTTPS enforced | 301 | https://linkame.events/mcp |
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 →
account.get_current_user ~23
Restituisce il profilo base dell’utente autenticato.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
contacts.add_note ~63
Aggiunge una nota a un contatto. Richiede conferma esplicita e una idempotency key.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | – | yes | – |
| contactId | string | yes | – |
| idempotencyKey | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
contacts.get ~32
Restituisce un contatto della rubrica usando il suo identificatore stabile.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | string | yes | – |
No output schema declared.
No examples provided.
contacts.get_timeline ~63
Restituisce la timeline di un contatto della rubrica. Supporta paginazione con limit e offset.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
| pageToken | string | – | – |
No output schema declared.
No examples provided.
contacts.list_groups ~30
Restituisce i gruppi di contatti dell’utente, inclusi gli inviti pendenti.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
contacts.search ~68
Cerca nella rubrica dell’utente per nome, azienda, ruolo, email, tag o note. Supporta paginazione con limit e offset.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| pageToken | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
events.get ~33
Restituisce i dettagli di un evento pubblicato o gestito dall’utente.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | – |
No output schema declared.
No examples provided.
events.get_matching_results ~33
Restituisce i risultati dell’ultimo matching completato dell’utente.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | – | – |
No output schema declared.
No examples provided.
events.get_matching_status ~37
Restituisce lo stato dell’ultimo matching dell’utente, eventualmente filtrato per evento.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | – | – |
No output schema declared.
No examples provided.
events.get_my_ticket ~50
Restituisce un biglietto dell’utente. Il QR viene incluso solo se richiesto esplicitamente.
| Name | Type | Req | Description |
|---|---|---|---|
| includeQrCode | boolean | – | – |
| ticketId | string | yes | – |
No output schema declared.
No examples provided.
events.list ~52
Elenca gli eventi pubblicati visibili all’utente. Supporta paginazione con limit e offset.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| pageToken | string | – | – |
No output schema declared.
No examples provided.
events.list_my_registrations ~58
Elenca gli eventi ai quali l’utente risulta registrato. Supporta paginazione con limit e offset.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| pageToken | string | – | – |
No output schema declared.
No examples provided.
events.list_my_tickets ~65
Elenca i biglietti posseduti o trasferiti all’utente senza esporre il QR. Supporta paginazione con limit e offset.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| pageToken | string | – | – |
No output schema declared.
No examples provided.
organizer.events.get_dashboard ~34
Restituisce il riepilogo operativo aggiornato di un evento gestito.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | – |
No output schema declared.
No examples provided.
organizer.events.get_matching_status ~37
Restituisce configurazione, stato e conteggi del matching di un evento gestito.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | – |
No output schema declared.
No examples provided.
organizer.events.get_registrations ~59
Elenca le registrazioni paginando i partecipanti di un evento gestito.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
| pageToken | string | – | – |
No output schema declared.
No examples provided.
organizer.events.get_sessions ~37
Restituisce agenda, capienza e prenotazioni sessione di un evento gestito.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | – |
No output schema declared.
No examples provided.
organizer.events.get_support_ticket ~43
Restituisce un ticket di supporto dell’evento e la conversazione.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | – |
| ticketId | string | yes | – |
No output schema declared.
No examples provided.
organizer.events.get_support_tickets ~67
Elenca i ticket di supporto dell’evento con filtro stato e paginazione.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
| pageToken | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
organizer.events.get_ticketing_summary ~39
Restituisce riepilogo ticket, quantità vendute, assegnazioni e check-in.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | yes | – |
No output schema declared.
No examples provided.
organizer.events.list_managed ~52
Elenca gli eventi gestiti dall’organizzatore o dal super admin con stato e date.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| pageToken | string | – | – |
No output schema declared.
No examples provided.
organizer.events.reply_support_ticket ~66
Risponde a un ticket di supporto con conferma e idempotency key.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | – | yes | – |
| eventId | string | yes | – |
| idempotencyKey | string | yes | – |
| text | string | yes | – |
| ticketId | string | yes | – |
No output schema declared.
No examples provided.
organizer.events.update_support_ticket_status ~69
Cambia lo stato di un ticket di supporto con conferma e idempotency key.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | – | yes | – |
| eventId | string | yes | – |
| idempotencyKey | string | yes | – |
| status | string | yes | – |
| ticketId | string | yes | – |
No output schema declared.
No examples provided.
organizer.support_tickets.list_all ~64
Elenca i ticket di supporto di qualsiasi evento; solo super admin.
| Name | Type | Req | Description |
|---|---|---|---|
| eventId | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| pageToken | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
profile.get_me ~23
Restituisce i profili Linkame dell’utente autenticato.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · linkame.events
claude mcp add --transport http ohdonpiano-linkame 'https://linkame.events/mcp'
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 78 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.