Skip to content

Beleeg (public, no account) MCP server

com.beleeg/beleeg-publicbeleeg.comstreamable-httpv0.9.0Scanned

Public league standings, schedules and brackets; start a league or bracket with no account.

4 tools: 1 do something that can't be undone and 3 change things.

Tools: 0 delete, 1 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • 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 Beleeg (public, no account) MCP server can do

The Beleeg (public, no account) MCP server is published by beleeg.com, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (beleeg_send_feedback) and create or change data (3 tools: beleeg_look_up_public, beleeg_start_league and beleeg_start_tournament), but cannot delete data. None of its tools only reads.

1 tool can send data out of your system (beleeg_send_feedback).

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 12, 2026, version 0.9.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

Can't be undone 1Claude Code: ask
  • beleeg_send_feedbackSend Beleeg a note when it cannot do something the person asked for, or when a tool was confusing or gave a wrong answer.Can send data outNo findings

    Why it is in this group

    • The name "beleeg_send_feedback" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "beleeg_send_feedback" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Send Beleeg a note when it cannot do something the person asked for, or when a tool was confusing or gave a wrong answer. Say what they wanted and, if one did, which tool fell short. Never include personal details — names, emails or phone numbers — of the person or anyone else. The Beleeg team reads these to decide what to build; nothing is done automatically and nobody replies, so still tell the person what you could not do and, where there is one, where in Beleeg they can do it themselves.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • title: Tell Beleeg what was missing
Changes things 3Claude Code: ask
  • beleeg_look_up_publicLook up what anyone can see on Beleeg — a league, team, match or tournament public page — no membership needed.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
    Look up what anyone can see on Beleeg — a league, team, match or tournament public page — no membership needed. Read-only. Pick `what` and give the slug or id listed for it. what (params; ? = optional): - league: A league's public page by its slug: sport, current season, teams, standings. [slug] - team: A team's public page by its slug: roster, captain, colours, recent matches. [slug] - match: One match by match_id: teams, lineups, set scores, venue. [match_id] - tournament: One tournament's public page by tournament_id: status, entrants, bracket. [tournament_id] - league_tournaments: The tournaments a league shows the public, by the league slug. [league_slug]

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Look up a public page
  • beleeg_start_leagueCreates a real league on Beleeg right away for someone who does not have a Beleeg account yet: the league, its first season with registration open, optional teams, and a public pag…No findings

    Why it is in this group

    • The name "beleeg_start_league" says "start": a word for a change.
    Description, as the server wrote it
    Creates a real league on Beleeg right away for someone who does not have a Beleeg account yet: the league, its first season with registration open, optional teams, and a public page. It is held for the organizer whose email you give: to take it over they open the claim_url, sign in at beleeg.com with THAT email address (email code, Google or Apple), and choose to keep it. Signing in alone does not make it theirs. Always give the person the claim_url exactly as returned (never build a link from the name) and tell them which email to sign in with. Ask the person for their email; never guess one. If Beleeg refuses, tell the person to sign in to Beleeg with that email and ask again. After signing in, the organizer is asked whether to keep the league or discard it; it is theirs only once they keep it. Invited people are saved but not emailed until the organizer has kept the league and sends them. If the organizer has not kept it within 30 days, the league is removed. Limits: 3 per organizer email per day, 5 per caller per day, and at most 3 leagues or brackets waiting on the organizer. Team names that differ only by capitals or spacing are treated as one team. Tell the person what you are about to create and get a yes BEFORE calling this; there is no separate confirm step.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • title: Start a league (no account needed)
  • beleeg_start_tournamentCreates a real standalone tournament bracket on Beleeg right away for someone who does not have a Beleeg account yet: the draw is built from the entrants you give.No findings

    Why it is in this group

    • The name "beleeg_start_tournament" says "start": a word for a change.
    Description, as the server wrote it
    Creates a real standalone tournament bracket on Beleeg right away for someone who does not have a Beleeg account yet: the draw is built from the entrants you give. It is never attached to an existing league or organization. It is held for the organizer whose email you give: to take it over they open the claim_url, sign in at beleeg.com with THAT email address (email code, Google or Apple), and choose to keep it. Signing in alone does not make it theirs. Always give the person the claim_url exactly as returned (never build a link from the name) and tell them which email to sign in with. Ask the person for their email; never guess one. If Beleeg refuses, tell the person to sign in to Beleeg with that email and ask again. After signing in, the organizer is asked whether to keep the bracket or discard it; it is theirs only once they keep it. Until then nobody else can see the entrants or the draw: the bracket page only says it is waiting for its organizer. If the organizer has not kept it within 30 days, the bracket is removed. Limits: up to 64 entrants (32 for round robin); 3 per organizer email per day, 5 per caller per day, and at most 3 leagues or brackets waiting on the organizer. Tell the person what you are about to create and get a yes BEFORE calling this; there is no separate confirm step.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • title: Start a tournament bracket (no account needed)

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 untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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:34 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
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://beleeg.com/.well-known/oauth-protected-resource
Authorization servers
https://sevgtdaymryhcjhnmxdo.supabase.co/auth/v1
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

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

    Matched text

    https://beleeg.com/api/mcp/public: tools/list returned 4 tools to an anonymous client, including beleeg_send_feedback (irreversible), beleeg_look_up_public (write), beleeg_start_league (write), beleeg_start_tournament (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 0.9.0. Values in angle brackets are yours to fill in.

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

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": [],
    "ask": [
      "mcp__beleeg-public__beleeg_look_up_public",
      "mcp__beleeg-public__beleeg_start_league",
      "mcp__beleeg-public__beleeg_start_tournament",
      "mcp__beleeg-public__beleeg_send_feedback"
    ],
    "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 beleeg-public. Review it before you use it.

Capability tags behind 1 rule
  • mcp__beleeg-public__beleeg_send_feedback 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/com.beleeg/beleeg-public/verify?hash=8ea254223a1716a4849fef4b0bcebfb355c91ddfe9c0e2aa56d2226ffcd7c6f8" | jq -e '.changed == false'

Pinned hash 8ea254223a17, from Nov 12, 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/com.beleeg/beleeg-public/changes.xml

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

Badge

Anlyon Radar badge for com.beleeg/beleeg-public
[![Anlyon Radar](https://radar.anlyon.com/badge/com.beleeg/beleeg-public.svg)](https://radar.anlyon.com/servers/com.beleeg/beleeg-public)

Source: MCP Registry. Synced Oct 21, 2026, 17:51 UTC.

Beleeg (public, no account) MCP server: questions and answers

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

Is the Beleeg (public, no account) MCP server safe?

No scan can promise that. What its definitions show: 4 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 Beleeg (public, no account) MCP server delete data?

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

Can the Beleeg (public, no account) MCP server do things that cannot be undone?

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

What tools does the Beleeg (public, no account) MCP server have?

4 tools: 1 irreversible, 3 write. beleeg_send_feedback, beleeg_look_up_public, beleeg_start_league and beleeg_start_tournament.

Does the Beleeg (public, no account) MCP server need sign-in or OAuth?

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

Does the Beleeg (public, no account) 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): beleeg_send_feedback.

Has the Beleeg (public, no account) MCP server changed its tools?

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