Skip to content

縦綱 Tatezuna — o-sumo MCP server

us.osada/o-sumoosada.usstreamable-httpv1.0.1Scanned

Grand Sumo (大相撲) banzuke, torikumi results, and rikishi profiles from osada.us. Read-only, no auth.

5 tools: 5 only read.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the 縦綱 Tatezuna — o-sumo MCP server can do

The 縦綱 Tatezuna — o-sumo MCP server is published by osada.us, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data 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, and its tools changed once since Anlyon Radar first saw them.

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

5 tools

Only reads 5Show 5 read-only tools
  • get_banzukeGet official Grand Sumo banzuke (rankings for makuuchi and juryo divisions).No findings

    Why it is in this group

    • The name "get_banzuke" says "get": a word for reading.
    Description, as the server wrote it
    Get official Grand Sumo banzuke (rankings for makuuchi and juryo divisions). Optionally specify monthKey (YYYYMM, e.g. "202609") for historical basho, or omit for the latest basho.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_rikishi_profileGet detailed profile and career record for a specific rikishi by numeric ID.No findings

    Why it is in this group

    • The name "get_rikishi_profile" says "get": a word for reading.
    Description, as the server wrote it
    Get detailed profile and career record for a specific rikishi by numeric ID.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_torikumiGet torikumi match results or schedule for a specific day (pathDate in YYYYMMDD format).No findings

    Why it is in this group

    • The name "get_torikumi" says "get": a word for reading.
    Description, as the server wrote it
    Get torikumi match results or schedule for a specific day (pathDate in YYYYMMDD format).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_bashoList current and archived Grand Sumo basho available in o-sumo, along with their page URLs and API endpoints.No findings

    Why it is in this group

    • The name "list_basho" says "list": a word for reading.
    Description, as the server wrote it
    List current and archived Grand Sumo basho available in o-sumo, along with their page URLs and API endpoints.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • search_rikishiSearch Grand Sumo rikishi by 四股名 (shikona) or 読み (yomi).No findings

    Why it is in this group

    • The name "search_rikishi" says "search": a word for reading.
    Description, as the server wrote it
    Search Grand Sumo rikishi by 四股名 (shikona) or 読み (yomi). Returns up to 20 matching rikishi with their ID, name, reading, current rank, and profile URLs.

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

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 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 19, 2026, 17:23 UTC, unchanged since Nov 5, 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
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://osada.us/.well-known/oauth-protected-resource
Authorization servers
https://osada.us/
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no

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. Tools5 changed.~5 changedView diff

Install

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

claude mcp add --transport http o-sumo https://osada.us/mcp
claude mcp add --transport http o-sumo https://osada.us/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__o-sumo__search_rikishi",
      "mcp__o-sumo__get_rikishi_profile",
      "mcp__o-sumo__get_banzuke",
      "mcp__o-sumo__get_torikumi",
      "mcp__o-sumo__list_basho"
    ],
    "ask": [],
    "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 o-sumo. Review it before you use it.

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/us.osada/o-sumo/verify?hash=277618026241537276a3098f98b2908e454aa9918782ae1cc6dd1b235b2afa03" | jq -e '.changed == false'

Pinned hash 277618026241, from Nov 18, 2026, 19:17 UTC.

Watch

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

https://radar.anlyon.com/servers/us.osada/o-sumo/changes.xml

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

Badge

Anlyon Radar badge for us.osada/o-sumo
[![Anlyon Radar](https://radar.anlyon.com/badge/us.osada/o-sumo.svg)](https://radar.anlyon.com/servers/us.osada/o-sumo)

Source: MCP Registry · repository. Synced Nov 5, 2026, 01:17 UTC.

縦綱 Tatezuna — o-sumo MCP server: questions and answers

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

Is the 縦綱 Tatezuna — o-sumo MCP server safe?

No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the 縦綱 Tatezuna — o-sumo MCP server delete data?

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

Can the 縦綱 Tatezuna — o-sumo 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 縦綱 Tatezuna — o-sumo MCP server have?

5 tools: 5 read. search_rikishi, get_rikishi_profile, get_banzuke, get_torikumi and list_basho.

Does the 縦綱 Tatezuna — o-sumo MCP server need sign-in or OAuth?

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

Does the 縦綱 Tatezuna — o-sumo MCP server send data to outside services?

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

Has the 縦綱 Tatezuna — o-sumo MCP server changed its tools?

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