Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.antoinedelorme/kweenkl-mcp

REMOTE · API.KWEENKL.COM

Push notifications for AI agents - send instant iPhone notifications from any MCP client.

Available components

0 this week 83 Trust /100

Last scanned (19 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Trust breakdown (7 categories)

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 775 tokens (~96/item across 8 items; 6 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 28 Sept 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
  • 25 Sept 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
  • 26 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 17 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • MCP protocol: fail → pass ▲ functional
    • Schema quality: excellent → good functional
    • MCP protocol version: 2024-11-05 → 2026-07-28 functional
    • Server version: 1.0.0 → 1.1.0 functional
Diagnostics

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 21 Nov 2026 · Probed https://api.kweenkl.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kweenkl.com CN=WE1,O=Google Trust Services,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 38cb6876cb1178450e6bc94027b4ab8b
SANs: kweenkl.com, api.kweenkl.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.kweenkl.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
kweenkl.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.kweenkl.com/mcp Verified 200
http (plaintext) http://api.kweenkl.com/mcp Served over HTTP 200
MCP tools · 6 exposed · ~697 tokens

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 →

Tool Tokens
fetch ~56

Fetch details about a specific kweenkl channel or notification by ID.

NameTypeReqDescription
idstringyesThe ID of the channel or notification to fetch
typestringyesType of resource to fetch: 'channel' or 'notification'

No output schema declared.

No examples provided.

kweenkl ~363

Send a push notification using kweenkl. The verb 'kweenkl' means to send a notification. Use this to notify users about important events, updates, or information that requires immediate attention.

NameTypeReqDescription
glanceobject–Optional structured visualization rendered as a card inside the kweenkl iOS app. Must include a 'type' field. v1 supports type='line_chart' with required fields {labels: string[], values: number[]} (…
messagestringyesThe notification message content. Should be clear, concise, and actionable. Maximum recommended length: 500 characters for optimal mobile display.
payloadobject–Optional custom JSON payload for additional metadata. Can include any structured data that your app might process (e.g., action buttons, deep links, custom data).
prioritystring–Priority level for the notification. 'high' = urgent/critical alerts, 'normal' = standard updates (default), 'low' = non-urgent information.
titlestring–Optional title for the notification. Should be brief (max 50 chars recommended). If omitted, only the message will be shown.
webhook_tokenstringyesThe webhook token for your kweenkl channel. Format: UUID-like string. Can be found in the kweenkl iOS app by opening a channel and viewing 'Channel Info'.

No output schema declared.

No examples provided.

kweenkl_login ~141

Start the kweenkl login/onboarding flow. If the user provides their device_token (from the iOS app), this will immediately create their webhook. Otherwise, guides them to download the app or join the waitlist.

NameTypeReqDescription
device_tokenstring–The user's device token from the kweenkl iOS app. If provided, immediately creates a webhook for them.
emailstring–User's email address for waitlist subscription (only used if has_app is false)
has_appboolean–Whether the user already has the kweenkl iOS app installed. If true and no device_token, starts device auth flow.

No output schema declared.

No examples provided.

kweenkl_login_check ~59

Check the status of a device authorization flow. Call this after kweenkl_login to see if the user has approved the connection in their iOS app.

NameTypeReqDescription
session_idstringyesThe session ID returned from kweenkl_login

No output schema declared.

No examples provided.

kweenkl_status ~35

Check kweenkl server connectivity and status. Use this to verify the connection is working before sending notifications. No authentication required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~43

Search kweenkl notification channels and messages. Use this to find channels by name or search through notification history.

NameTypeReqDescription
querystringyesSearch query to find channels or notifications

No output schema declared.

No examples provided.

Install

How do I install the io.github.antoinedelorme/kweenkl-mcp server?

io.github.antoinedelorme/kweenkl-mcp is a hosted endpoint at https://api.kweenkl.com/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 · api.kweenkl.com

# add to Claude Code
claude mcp add --transport http antoinedelorme-kweenkl-mcp 'https://api.kweenkl.com/mcp'
Common questions

What is the io.github.antoinedelorme/kweenkl-mcp server?

io.github.antoinedelorme/kweenkl-mcp is listed in the public MCP registry as io.github.antoinedelorme/kweenkl-mcp. Push notifications for AI agents - send instant iPhone notifications from any MCP client. This page covers its hosted endpoint (https://api.kweenkl.com/mcp).

Is the io.github.antoinedelorme/kweenkl-mcp server safe to use?

io.github.antoinedelorme/kweenkl-mcp scores 83 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 io.github.antoinedelorme/kweenkl-mcp server expose?

io.github.antoinedelorme/kweenkl-mcp exposes 6 tools: kweenkl_status, kweenkl_login, kweenkl_login_check, search, fetch, kweenkl. Their descriptions and schemas cost roughly 697 tokens of context every time the server is loaded.

Does the io.github.antoinedelorme/kweenkl-mcp server require authentication?

No. We connected to io.github.antoinedelorme/kweenkl-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.antoinedelorme/kweenkl-mcp server still maintained?

io.github.antoinedelorme/kweenkl-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.antoinedelorme/kweenkl-mcp server?

VerifyMCP ran 13 checks on io.github.antoinedelorme/kweenkl-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.