Skip to content

Yahad MCP server

ai.yahad/yahadyahad.aistreamable-httpv1.1.1Scanned

Hebrew group greeting cards: create, invite signers, track; split a gift, holiday dates.

6 tools: 4 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

4 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 Yahad MCP server can do

The Yahad MCP server is published by yahad.ai, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: suggest_prompts, occasion_date, create_board and gift_budget), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (create_board).

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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.1.1.

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

Changes things 4Claude Code: ask
  • create_boardCreates a group greeting card that several people sign before it opens on a set date, and returns the link to send to participants.Reads text others writeNo findings

    Why it is in this group

    • The name "create_board" says "create": 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
    Creates a group greeting card that several people sign before it opens on a set date, and returns the link to send to participants. Requires the organiser's email: the full management links are sent there, and a one-time 'take control' link is returned. Ask the person for anything missing; never invent an email. For Дарим (darim.ai) names are Russian; for Yahad (yahad.ai) Hebrew.

    Annotations the server declares

    • title: Create a group card
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
  • gift_budgetHow much each person gives toward a group gift: divide the cost by those who will actually pay, round down; the organiser adds the rest.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
    How much each person gives toward a group gift: divide the cost by those who will actually pay, round down; the organiser adds the rest. Or, from a per-person amount, the total budget. Pass exactly one of giftCost or perPerson. Amounts are in the service's currency.

    Annotations the server declares

    • title: Split a group gift
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • occasion_dateNext date and the one after for a professional day (Russian service) or a Jewish holiday (Hebrew service), computed from the calendar rule, never stale.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
    Next date and the one after for a professional day (Russian service) or a Jewish holiday (Hebrew service), computed from the calendar rule, never stale. For fasts and memorial days the answer says greetings are not customary.

    Annotations the server declares

    • title: When is a holiday
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • suggest_promptsSuggests ready questions the organiser can show participants, for an occasion.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
    Suggests ready questions the organiser can show participants, for an occasion. Optional recipientName fills the name in.

    Annotations the server declares

    • title: Suggest questions for participants
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 2Show 2 read-only tools
  • board_statusShows how collection is going for a card: how many have signed, when collection closes and when it opens.No findings

    Why it is in this group

    • The name "board_status" says "status": a word for reading.
    Description, as the server wrote it
    Shows how collection is going for a card: how many have signed, when collection closes and when it opens. Takes the participants' invite link.

    Annotations the server declares

    • title: Check collection progress
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_occasionsLists the occasions this group-card service supports, with the value to pass to create_board.No findings

    Why it is in this group

    • The name "list_occasions" says "list": a word for reading.
    Description, as the server wrote it
    Lists the occasions this group-card service supports, with the value to pass to create_board.

    Annotations the server declares

    • title: List occasions
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: 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.

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

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 out0
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 15, 2026, 13:22 UTC, unchanged since Oct 31, 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
4
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 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.yahad.ai/mcp: tools/list returned 6 tools to an anonymous client, including suggest_prompts (write), occasion_date (write), create_board (write), gift_budget (write)

    What this check looks for

Posture changes

  1. Oct 31, 2026
    • Tools that change things, listed without credentials: 2 to 4

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.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 4.View diff
    • Tools that change things, listed without credentials: 2 to 4
  2. Tools2 added.+2 addedView diff

Install

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

claude mcp add --transport http yahad https://api.yahad.ai/mcp
claude mcp add --transport http yahad https://api.yahad.ai/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__yahad__list_occasions",
      "mcp__yahad__board_status"
    ],
    "ask": [
      "mcp__yahad__suggest_prompts",
      "mcp__yahad__occasion_date",
      "mcp__yahad__create_board",
      "mcp__yahad__gift_budget"
    ],
    "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 yahad. Review it before you use it.

Capability tags behind 1 rule
  • mcp__yahad__create_board untrusted-input

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.yahad/yahad/verify?hash=3fb3bdf9f8588524712c5b2e385503d4419d831402e16e8bf099ab0e0704578d" | jq -e '.changed == false'

Pinned hash 3fb3bdf9f858, from Nov 10, 2026, 17:18 UTC.

Watch

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

https://radar.anlyon.com/servers/ai.yahad/yahad/changes.xml

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

Badge

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

Source: MCP Registry · repository. Synced Oct 29, 2026, 10:17 UTC.

Yahad MCP server: questions and answers

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

Is the Yahad MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 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 Yahad MCP server delete data?

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

Can the Yahad 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 Yahad MCP server have?

6 tools: 4 write, 2 read. suggest_prompts, occasion_date, create_board, gift_budget, list_occasions and board_status.

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

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

Does the Yahad MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Yahad MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 26, 2026. Every change is on this page and in its Atom feed.