Skip to content

kweenkl-mcp server

io.github.antoinedelorme/kweenkl-mcpantoinedelormestreamable-httpv1.1.0Scanned

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

6 tools: 1 do something that can't be undone, 2 change things and 3 only read.

Tools: 0 delete, 1 irreversible, 2 write, 3 read.
  • Reads private data · 1
  • Reads text others write · 6
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the kweenkl-mcp server can do

The kweenkl-mcp server is published by the GitHub account antoinedelorme. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (kweenkl) and create or change data (2 tools: kweenkl_login and kweenkl_login_check), but cannot delete data. 3 tools only read.

1 tool reads private data (search); 6 tools bring in text other people can write (kweenkl_status, kweenkl_login, kweenkl_login_check and 3 more); 1 tool can send data out of your system (kweenkl). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Can't be undone 1Claude Code: ask
  • kweenklSend a push notification using kweenkl.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Send Notification
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 2Claude Code: ask
  • kweenkl_loginStart the kweenkl login/onboarding flow.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Login / Setup
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • kweenkl_login_checkCheck the status of a device authorization flow.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check Login Status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • fetchFetch details about a specific kweenkl channel or notification by ID.Reads text others writeNo findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Fetch details about a specific kweenkl channel or notification by ID.

    Annotations the server declares

    • title: Fetch Resource
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • kweenkl_statusCheck kweenkl server connectivity and status.Reads text others writeNo findings

    Why it is in this group

    • The name "kweenkl_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check kweenkl server connectivity and status. Use this to verify the connection is working before sending notifications. No authentication required.

    Annotations the server declares

    • title: Check Status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__kweenkl__kweenkl"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:02 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.kweenkl.com/mcp: tools/list returned 6 tools to an anonymous client, including kweenkl (irreversible), kweenkl_login (write), kweenkl_login_check (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http kweenkl https://api.kweenkl.com/mcp
claude mcp add --transport http kweenkl https://api.kweenkl.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__kweenkl__kweenkl_status",
      "mcp__kweenkl__search",
      "mcp__kweenkl__fetch"
    ],
    "ask": [
      "mcp__kweenkl__kweenkl_login",
      "mcp__kweenkl__kweenkl_login_check",
      "mcp__kweenkl__kweenkl"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as kweenkl. Review it before you use it.

Capability tags behind 6 rules
  • mcp__kweenkl__kweenkl_status untrusted-input
  • mcp__kweenkl__kweenkl_login untrusted-input
  • mcp__kweenkl__kweenkl_login_check untrusted-input
  • mcp__kweenkl__search private-data, untrusted-input
  • mcp__kweenkl__fetch untrusted-input
  • mcp__kweenkl__kweenkl untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.antoinedelorme/kweenkl-mcp/verify?hash=5c2cb631262460bf6d4ab4067607b4423482cd6c35213b9538648d2768ae9cfa" | jq -e '.changed == false'

Pinned hash 5c2cb6312624, from Nov 16, 2026, 10:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.antoinedelorme/kweenkl-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.antoinedelorme/kweenkl-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.antoinedelorme/kweenkl-mcp.svg)](https://radar.anlyon.com/servers/io.github.antoinedelorme/kweenkl-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:23 UTC.

kweenkl-mcp server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the kweenkl-mcp server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the kweenkl-mcp server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the kweenkl-mcp server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: kweenkl.

What tools does the kweenkl-mcp server have?

6 tools: 1 irreversible, 2 write, 3 read. kweenkl, kweenkl_login, kweenkl_login_check, kweenkl_status, search and fetch.

Does the kweenkl-mcp server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the kweenkl-mcp server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): kweenkl.

Has the kweenkl-mcp server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.