Skip to content

Wake MCP server

ai.wakeagents/wakewakeagents.aistreamable-httpv1.0.0Scanned

Read wakeagents.ai as an agent: about, search, read a page, get-started links to install or scan.

4 tools: 2 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • 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 Wake MCP server can do

The Wake MCP server is published by wakeagents.ai, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: about and get_started), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (read_page); 1 tool can send data out of your system (read_page).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.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.

4 tools

Changes things 2Claude Code: ask
  • aboutWhat this site is and where its main pages are: documentation, API, pricing, sign-up.No 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.
    Description, as the server wrote it
    What this site is and where its main pages are: documentation, API, pricing, sign-up. Call this first.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_startedThe links to download, install, sign up, see pricing or book a demo.1 finding

    Why it is in this group

    • The name "get_started" says "get": a word for reading.
    • The description's first verb is "link": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_started" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "get_started" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    The links to download, install, sign up, see pricing or book a demo. Call this when the person wants to use or buy what this site offers, and give them the link.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • read_pageRead a page of this site as text.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "read_page" says "read": a word for reading.

    What it can reach

    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Read a page of this site as text. Pass a URL or a path on this site.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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.

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, 18:18 UTC, unchanged since Nov 20, 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
2
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
  • WarnThe whole server

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

    Matched text

    https://wakeagents.ai/agents/wakeagents.ai/mcp?via=mcp_registry: tools/list returned 4 tools to an anonymous client, including about (write), get_started (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "get_started" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "get_started" says "get": a word for reading.

    What this check looks for

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.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http wake https://wakeagents.ai/agents/wakeagents.ai/mcp?via=mcp_registry
claude mcp add --transport http wake https://wakeagents.ai/agents/wakeagents.ai/mcp?via=mcp_registry

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__wake__search"
    ],
    "ask": [
      "mcp__wake__about",
      "mcp__wake__read_page",
      "mcp__wake__get_started"
    ],
    "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 wake. Review it before you use it.

Capability tags behind 1 rule
  • mcp__wake__read_page 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/ai.wakeagents/wake/verify?hash=ac8a9a16da304971a7ca5565845f751be73b4ce41a5eeef7d088d2a94a5f600d" | jq -e '.changed == false'

Pinned hash ac8a9a16da30, from Nov 20, 2026, 00:18 UTC.

Watch

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

https://radar.anlyon.com/servers/ai.wakeagents/wake/changes.xml

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

Badge

Anlyon Radar badge for ai.wakeagents/wake
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.wakeagents/wake.svg)](https://radar.anlyon.com/servers/ai.wakeagents/wake)

Source: MCP Registry. Synced Nov 20, 2026, 00:17 UTC.

Wake MCP server: questions and answers

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

Is the Wake MCP server safe?

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

Can the Wake MCP server delete data?

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

Can the Wake MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Wake MCP server have?

4 tools: 2 write, 2 read. about, get_started, search and read_page.

Does the Wake MCP server need sign-in or OAuth?

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

Does the Wake 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): read_page.

Has the Wake MCP server changed its tools?

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