# 縦綱 Tatezuna — o-sumo (remote · osada.us)

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

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `osada.us`: 73/100 (this document), [markdown](https://verifymcp.io/servers/us-osada-o-sumo/osada.md), [page](https://verifymcp.io/servers/us-osada-o-sumo/osada)

## Channel facts

- Endpoint: `https://osada.us/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 335 tokens (~67/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the 縦綱 Tatezuna — o-sumo MCP server?

縦綱 Tatezuna — o-sumo is a hosted endpoint at https://osada.us/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http us-osada-o-sumo 'https://osada.us/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "us-osada-o-sumo": {
      "url": "https://osada.us/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "us-osada-o-sumo": {
      "type": "http",
      "url": "https://osada.us/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.us-osada-o-sumo]
url = "https://osada.us/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "us-osada-o-sumo": {
      "type": "remote",
      "url": "https://osada.us/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add us-osada-o-sumo --url 'https://osada.us/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  us-osada-o-sumo:
    url: "https://osada.us/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "us-osada-o-sumo": {
      "Transport": "http",
      "Url": "https://osada.us/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add us-osada-o-sumo -t streamable-http -u 'https://osada.us/mcp'
```

### Other

```json
{
  "mcpServers": {
    "us-osada-o-sumo": {
      "type": "http",
      "url": "https://osada.us/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 73)

First indexed and scored.

## MCP tools (5)

### `search_rikishi` (~86 tokens)

Search rikishi（力士検索）

Search Grand Sumo rikishi by 四股名 (shikona) or 読み (yomi). Returns up to 20 matching rikishi with their ID, name, reading, current rank, and profile URLs.

Input parameters:

- `query` (string, required): Search query for rikishi name or reading (e.g. "大の里", "おおのさと")

### `get_rikishi_profile` (~44 tokens)

Get rikishi profile（力士プロフィール）

Get detailed profile and career record for a specific rikishi by numeric ID.

Input parameters:

- `id` (integer, required): Official rikishi ID (e.g. 4227)

### `get_banzuke` (~88 tokens)

Get banzuke（番付）

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.

Input parameters:

- `monthKey` (string): Basho month key in YYYYMM format (e.g. "202609"). Defaults to current basho.

### `get_torikumi` (~84 tokens)

Get torikumi（取組）

Get torikumi match results or schedule for a specific day (pathDate in YYYYMMDD format).

Input parameters:

- `mode` (string): Whether to fetch "result" (completed bouts) or "schedule" (scheduled bouts). Defaults to "result".
- `pathDate` (string, required): Date key in YYYYMMDD format (e.g. "20260927")

### `list_basho` (~33 tokens)

List basho（場所一覧）

List current and archived Grand Sumo basho available in o-sumo, along with their page URLs and API endpoints.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/us-osada-o-sumo/osada#diagnostics

## Score history

- 2026-11-05: 73

## Common questions

### What is the 縦綱 Tatezuna — o-sumo MCP server?

縦綱 Tatezuna — o-sumo is an MCP server listed in the public MCP registry as us.osada/o-sumo. Grand Sumo (大相撲) banzuke, torikumi results, and rikishi profiles from osada.us. Read-only, no auth. This page covers its hosted endpoint (https://osada.us/mcp).

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

縦綱 Tatezuna — o-sumo scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the 縦綱 Tatezuna — o-sumo MCP server expose?

縦綱 Tatezuna — o-sumo exposes 5 tools: search_rikishi, get_rikishi_profile, get_banzuke, get_torikumi, list_basho. Their descriptions and schemas cost roughly 335 tokens of context every time the server is loaded.

### Does the 縦綱 Tatezuna — o-sumo MCP server require authentication?

No. We connected to 縦綱 Tatezuna — o-sumo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the 縦綱 Tatezuna — o-sumo MCP server still maintained?

縦綱 Tatezuna — o-sumo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://osada.us/mcp
- Repository: https://github.com/dai/o-sumo
- Website: https://osada.us/
- Changelog RSS feed: https://verifymcp.io/servers/us-osada-o-sumo/osada.xml
- Changelog JSON feed: https://verifymcp.io/servers/us-osada-o-sumo/osada.json
- HTML version of this page: https://verifymcp.io/servers/us-osada-o-sumo/osada