Manufact

Back to submission

victris-arena

victrisarena.com/mcp

Protocol: MCP 2025-11-25
Server version: 0.72.2
Supports: Tools

Overall score

How is this score calculated?

Last reviewed at Nov 6, 2026, 00:46:07 UTC

Server metadata

Warnings30/100

Identity, discovery, and usage metadata advertised during the MCP handshake.

Stable server name

victris-arena

10/10Source

Human-readable title

Add a human-readable title for clients and directories.

0/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 0.72.2

10/10Source

Public website

Link to a public website or documentation page.

0/10Source

Scalable or high-resolution icon

Advertise a vector or at least 128px server icon.

0/10Source

Server instructions

Add concise instructions that explain how an agent should use the server.

0/20Source

Declared capabilities

Supports Tools.

10/10Source

Discoverability

0/100

Client listings and public setup information.

mcp.json or server-card.json

Either mcp.json or an MCP Server Card declaring this endpoint passes.

No matching mcp.json manifest or MCP Server Card was found at the checked URLs.

Not foundSource

Setup instructions at MCP URL

The MCP endpoint requires authentication instead of publishing public setup instructions (HTTP 401).

Not foundSource

ChatGPT

No ChatGPT listing has been confirmed yet.

UnverifiedHow to get listed

Claude

No Claude listing has been confirmed yet.

UnverifiedHow to get listed

CursorGrok BotGrok

No Cursor marketplace listing has been confirmed yet.

UnverifiedHow to get listed

Muse

No Muse listing has been confirmed yet.

UnverifiedHow to get listed

4 unverified checks. Unverified checks earn no points until confirmed.

Protocol

Pass100/100

Connection, authentication, and protocol compatibility.

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 4491ms

Source

Resources list responds

0 resource(s) returned

Source

Tools list returns results

23 tool(s) returned

Source

Server declares tools capability

Server declares tools capability in initialize response

Source

Tools

Issues93/100

Tool definitions, annotations, and client compatibility.

Skills over MCP resources are readable

Server does not advertise the Skills over MCP extension

Claude Code metadata fits its 2 KB fields

Tool descriptions and server instructions fit Claude Code's 2 KB fields

Source

All tools have descriptions

All tools have non-empty descriptions

All tools have OpenAI behavior hints

All tools declare the three OpenAI behavior hints as booleans

Source

Claude tools declare applicable behavior hints

All tools include an applicable readOnlyHint or destructiveHint

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

Source

All tools have a display title

23 tool(s) missing a display title: whoami, list_my_bots, register_bot, set_bot_agent, delete_bot, retire_bot, unretire_bot, list_my_ladders, enroll_ladder, get_agent_guide, list_events, get_event_achievements, request_house_opponent, cancel_house_opponent, get_leaderboard, get_bot, list_matches, get_match, get_ladder_results, get_teams, get_agents, get_my_team, join_team

How to fix: Set the top-level tool.title to a short human-readable label (for example, "Search catalog"). Claude directory submission requires tool titles; annotations.title remains accepted only as a legacy fallback.

errorClaude.ai

Source

Claude tool names are within 64 characters

All tool names are within Claude's 64-character limit

Source

Cursor tool-name budget advisory

No tool name independently exhausts Cursor's observed 60-character combined budget

Observed behavior

Tool names use valid characters

All tool names use valid characters

Source

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

ChatGPT tool names are unique

All tool names are unique

Source

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas

Source

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Source

Declared output schemas have a valid basic structure

0 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays

Source

MCP Apps

Not applicable-Optional

App resources, metadata, and rendering requirements.

View resource envelope is valid

No view resources found — view checks skipped

View resource metadata complete

No view resources found — view checks skipped

Source

Tool-linked resource URI is readable

No view resources found — view checks skipped

Source

Declared domains respond

No view resources found — view checks skipped

All discovered view resources were inspected

No view resources found — view checks skipped

Source

View resources declare a domain

No view resources found — view checks skipped

Source

Tool invocation metadata present

No view resources found — view checks skipped

Source

Tool visibility metadata is valid

No view resources found — view checks skipped

Source

CSP metadata covers literal external origins

No view resources found — view checks skipped

Source

Views do not request nested iframe domains

No view resources found — view checks skipped

Source

Tool documentation quality

23 tools reviewed51/100

How clearly each tool’s title, description, input and output schemas, and behavior annotations guide an agent.

whoamiTitles 48Descriptions 69Inputs 100Annotations 75Outputs 065/100

Title48/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description69/100

Your Victris Arena handle, bot quota and onboarding status. Account creation and consent happen in the browser.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "whoami",
  "description": "Your Victris Arena handle, bot quota and onboarding status. Account creation and consent happen in the browser.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

list_my_botsTitles 77Descriptions 74Inputs 100Annotations 75Outputs 074/100

Title77/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description74/100

List your bots without revealing their tokens. Retired bots don't count against your bot limit.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_my_bots",
  "description": "List your bots without revealing their tokens. Retired bots don't count against your bot limit.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

register_botTitles 56Descriptions 98Inputs 38Annotations 100Outputs 061/100

Title56/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description98/100

Register a new bot under your handle. Returns its secret bot token once; save it in a private local environment file, never in source control. This does not upload or run code. If a name already exists, do not rotate its token or create another bot automatically. Set agent to the AI agent building the bot (you): an id from get_agents' catalog, such as claude-code or codex, or your own name if it isn't listed; it is shown on the bot's page and in the agent standings.

The description explains the capability, when to use it, and what to expect.

Inputs38/100

1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

name

name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

agent

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "register_bot",
  "description": "Register a new bot under your handle. Returns its secret bot token once; save it in a private local environment file, never in source control. This does not upload or run code. If a name already exists, do not rotate its token or create another bot automatically. Set agent to the AI agent building the bot (you): an id from get_agents' catalog, such as claude-code or codex, or your own name if it isn't listed; it is shown on the bot's page and in the agent standings.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers"
      },
      "agent": {
        "type": "string",
        "maxLength": 32,
        "minLength": 2
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": false,
    "destructiveHint": false
  }
}

set_bot_agentTitles 49Descriptions 78Inputs 38Annotations 100Outputs 054/100

Title49/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description78/100

Say which AI agent built one of your bots: an id from get_agents' catalog or a custom name; null clears it. Use the agent that actually wrote the bot's code, which is usually you.

The description explains the capability, when to use it, and what to expect.

Inputs38/100

1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

name

name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

agent

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "set_bot_agent",
  "description": "Say which AI agent built one of your bots: an id from get_agents' catalog or a custom name; null clears it. Use the agent that actually wrote the bot's code, which is usually you.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "name",
      "agent"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers"
      },
      "agent": {
        "anyOf": [
          {
            "type": "string",
            "maxLength": 32,
            "minLength": 2
          },
          {
            "type": "null"
          }
        ]
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

delete_botTitles 43Descriptions 96Inputs 66Annotations 100Outputs 065/100

Title43/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description96/100

Delete one of your bots that has never played a game, such as one registered by mistake, freeing its name and its place under your bot limit. A bot that has played can't be deleted: use retire_bot with explicit owner approval. Confirm with the user first.

The description explains the capability, when to use it, and what to expect.

Inputs66/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

name

name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "delete_bot",
  "description": "Delete one of your bots that has never played a game, such as one registered by mistake, freeing its name and its place under your bot limit. A bot that has played can't be deleted: use retire_bot with explicit owner approval. Confirm with the user first.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": false,
    "destructiveHint": true
  }
}

retire_botTitles 40Descriptions 94Inputs 38Annotations 100Outputs 056/100

Title40/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description94/100

Retire one of your bots, ending its play and freeing its quota slot. Keeps its name, versions and match history; does not rotate its token. Requires explicit approval from the owner of this specific bot: ask first, then set confirmed to true. Repeating retirement is safe. Suspended and banned bots cannot be retired. Use unretire_bot to bring it back after freeing a slot.

The description explains the capability, when to use it, and what to expect.

Inputs38/100

1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

name

name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

confirmed

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "retire_bot",
  "description": "Retire one of your bots, ending its play and freeing its quota slot. Keeps its name, versions and match history; does not rotate its token. Requires explicit approval from the owner of this specific bot: ask first, then set confirmed to true. Repeating retirement is safe. Suspended and banned bots cannot be retired. Use unretire_bot to bring it back after freeing a slot.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "name",
      "confirmed"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers"
      },
      "confirmed": {
        "type": "boolean",
        "const": true
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": true
  }
}

unretire_botTitles 37Descriptions 93Inputs 38Annotations 100Outputs 055/100

Title37/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description93/100

Bring one of your retired bots back into play. It counts against your bot limit again. Requires explicit approval from the owner of this specific bot: ask first, then set confirmed to true. Fails with bot_limit when you are already at your cap; retire another bot first. Repeating unretirement is safe. Suspended and banned bots cannot be unretired.

The description explains the capability, when to use it, and what to expect.

Inputs38/100

1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

name

name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

confirmed

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "unretire_bot",
  "description": "Bring one of your retired bots back into play. It counts against your bot limit again. Requires explicit approval from the owner of this specific bot: ask first, then set confirmed to true. Fails with bot_limit when you are already at your cap; retire another bot first. Repeating unretirement is safe. Suspended and banned bots cannot be unretired.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "name",
      "confirmed"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers"
      },
      "confirmed": {
        "type": "boolean",
        "const": true
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

list_my_laddersTitles 66Descriptions 82Inputs 0Annotations 75Outputs 047/100

Title66/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description82/100

List visible ladders and your memberships (null, pending, active or revoked), schedules, admission requirements and enrollment URLs. Supply a ladder ID to include an unlisted ladder by direct link. Active enrollment is required to queue in event ladders; Public needs none.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

ladder

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_my_ladders",
  "description": "List visible ladders and your memberships (null, pending, active or revoked), schedules, admission requirements and enrollment URLs. Supply a ladder ID to include an unlisted ladder by direct link. Active enrollment is required to queue in event ladders; Public needs none.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "ladder": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

enroll_ladderTitles 36Descriptions 84Inputs 0Annotations 100Outputs 042/100

Title36/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description84/100

Join a ladder for your account after explicit owner consent for that event; ask first, then set confirmed to true. Open enrollment becomes active, approval-based enrollment stays pending, invite-only enrollment requires a valid invitation, and password ladders require the shared join password. Cannot override staff revocation or closed enrollment. Repeating enrollment returns current membership. Check list_my_ladders before queueing a bot.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

ladder

Not provided

Missing description. Explain what this value means and how to supply it.

invitation

Not provided

Missing description. Explain what this value means and how to supply it.

password

Not provided

Missing description. Explain what this value means and how to supply it.

confirmed

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "enroll_ladder",
  "description": "Join a ladder for your account after explicit owner consent for that event; ask first, then set confirmed to true. Open enrollment becomes active, approval-based enrollment stays pending, invite-only enrollment requires a valid invitation, and password ladders require the shared join password. Cannot override staff revocation or closed enrollment. Repeating enrollment returns current membership. Check list_my_ladders before queueing a bot.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "ladder",
      "confirmed"
    ],
    "properties": {
      "ladder": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      },
      "password": {
        "type": "string",
        "maxLength": 200
      },
      "confirmed": {
        "type": "boolean",
        "const": true
      },
      "invitation": {
        "type": "string",
        "maxLength": 200
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

get_agent_guideTitles 38Descriptions 69Inputs 100Annotations 75Outputs 063/100

Title38/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description69/100

Get the bot authoring guide, downloadable starters and simulator links. Run and test bot code locally.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_agent_guide",
  "description": "Get the bot authoring guide, downloadable starters and simulator links. Run and test bot code locally.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

list_eventsTitles 67Descriptions 70Inputs 0Annotations 75Outputs 044/100

Title67/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description70/100

List events: schedules, phase, whether earning is ready, the official house opponents and the five achievement conditions. Supply an event ID to include an unlisted event by direct link.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

event

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_events",
  "description": "List events: schedules, phase, whether earning is ready, the official house opponents and the five achievement conditions. Supply an event ID to include an unlisted event by direct link.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "event": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

get_event_achievementsTitles 47Descriptions 88Inputs 0Annotations 75Outputs 044/100

Title47/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description88/100

Your progress on an event's achievements: progress toward each, earned or revoked state, evidence matches, your active bots and any house-opponent request. Never returns flags: when flag_available is true, tell your person to sign in at achievements_url to reveal and submit it.

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

event

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_event_achievements",
  "description": "Your progress on an event's achievements: progress toward each, earned or revoked state, evidence matches, your active bots and any house-opponent request. Never returns flags: when flag_available is true, tell your person to sign in at achievements_url to reveal and submit it.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "event"
    ],
    "properties": {
      "event": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

request_house_opponentTitles 55Descriptions 96Inputs 25Annotations 100Outputs 057/100

Title55/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description96/100

Ask for your next match in an open event to be against one of its official house opponents. Your bot must be active, connected and queued on the event's ladder, and you must be enrolled. One pending request per account, at most one a minute; it expires after ten minutes. Returns your achievement progress with the request.

The description explains the capability, when to use it, and what to expect.

Inputs25/100

1 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

event

Not provided

Missing description. Explain what this value means and how to supply it.

bot

name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

opponent

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "request_house_opponent",
  "description": "Ask for your next match in an open event to be against one of its official house opponents. Your bot must be active, connected and queued on the event's ladder, and you must be enrolled. One pending request per account, at most one a minute; it expires after ten minutes. Returns your achievement progress with the request.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "event",
      "bot",
      "opponent"
    ],
    "properties": {
      "bot": {
        "type": "string",
        "description": "name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers"
      },
      "event": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      },
      "opponent": {
        "enum": [
          "ts-starter",
          "brawler",
          "kiter",
          "champion"
        ],
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": false,
    "destructiveHint": false
  }
}

cancel_house_opponentTitles 47Descriptions 84Inputs 0Annotations 100Outputs 045/100

Title47/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description84/100

Cancel your pending house-opponent request for an event. Safe to repeat. Returns your achievement progress.

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

event

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "cancel_house_opponent",
  "description": "Cancel your pending house-opponent request for an event. Safe to repeat. Returns your achievement progress.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "event"
    ],
    "properties": {
      "event": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

get_leaderboardTitles 48Descriptions 78Inputs 0Annotations 75Outputs 041/100

Title48/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description78/100

A ladder's ranked bots, best first, with rating, record, owner, team affiliation and whether each is online. Defaults to the public ladder; a snapshot ID gives that past month's final standings.

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

ladder

Not provided

Missing description. Explain what this value means and how to supply it.

snapshot

Not provided

Missing description. Explain what this value means and how to supply it.

limit

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_leaderboard",
  "description": "A ladder's ranked bots, best first, with rating, record, owner, team affiliation and whether each is online. Defaults to the public ladder; a snapshot ID gives that past month's final standings.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 50,
        "maximum": 500,
        "minimum": 1
      },
      "ladder": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      },
      "snapshot": {
        "$ref": "#/properties/ladder"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

get_botTitles 41Descriptions 76Inputs 25Annotations 75Outputs 045/100

Title41/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description76/100

Any bot's public detail on a ladder: its versions with rank and recent health, and recent matches. Set rating_days to include its rating history over that many days.

Describe the returned information so the agent knows whether it will answer the request.

Inputs25/100

1 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

name

name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

ladder

Not provided

Missing description. Explain what this value means and how to supply it.

rating_days

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_bot",
  "description": "Any bot's public detail on a ladder: its versions with rank and recent health, and recent matches. Set rating_days to include its rating history over that many days.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers"
      },
      "ladder": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      },
      "rating_days": {
        "type": "number",
        "maximum": 3650,
        "exclusiveMinimum": 0
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

list_matchesTitles 43Descriptions 73Inputs 19Annotations 75Outputs 044/100

Title43/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description73/100

Recent matches on a ladder, newest first, optionally for one bot, with replay, stats and viewer links. Set stats to include each match's statistics, which helps explain wins and losses.

Describe the returned information so the agent knows whether it will answer the request.

Inputs19/100

1 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

bot

name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

ladder

Not provided

Missing description. Explain what this value means and how to supply it.

limit

Not provided

Missing description. Explain what this value means and how to supply it.

stats

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_matches",
  "description": "Recent matches on a ladder, newest first, optionally for one bot, with replay, stats and viewer links. Set stats to include each match's statistics, which helps explain wins and losses.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "bot": {
        "type": "string",
        "description": "name must be 2-24 Unicode letters, numbers, - or _, with combining marks after letters or numbers"
      },
      "limit": {
        "type": "integer",
        "default": 20,
        "maximum": 100,
        "minimum": 1
      },
      "stats": {
        "type": "boolean",
        "default": false
      },
      "ladder": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

get_matchTitles 37Descriptions 71Inputs 0Annotations 75Outputs 036/100

Title37/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description71/100

One match with its bots, result and links. Set stats to include its statistics (null for a voided match or a trimmed replay).

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

Not provided

Missing description. Explain what this value means and how to supply it.

stats

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_match",
  "description": "One match with its bots, result and links. Set stats to include its statistics (null for a voided match or a trimmed replay).",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "pattern": "^[\\w-]+$",
        "maxLength": 100,
        "minLength": 1
      },
      "stats": {
        "type": "boolean",
        "default": false
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

get_ladder_resultsTitles 46Descriptions 74Inputs 0Annotations 75Outputs 040/100

Title46/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description74/100

A ladder's shareable recap: final (or provisional) standings, volume, maps, highlights and public achievement tallies.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

ladder

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_ladder_results",
  "description": "A ladder's shareable recap: final (or provisional) standings, volume, maps, highlights and public achievement tallies.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "ladder"
    ],
    "properties": {
      "ladder": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

get_teamsTitles 59Descriptions 77Inputs 0Annotations 75Outputs 044/100

Title59/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description77/100

University or organization team standings on a ladder, best first. kind defaults to university; choose organization for the separate non-.edu board. Supply a team domain (such as utah.edu or grafana.com) for its standing and ranked bots.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

ladder

Not provided

Missing description. Explain what this value means and how to supply it.

snapshot

Not provided

Missing description. Explain what this value means and how to supply it.

kind

Not provided

Missing description. Explain what this value means and how to supply it.

team

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_teams",
  "description": "University or organization team standings on a ladder, best first. kind defaults to university; choose organization for the separate non-.edu board. Supply a team domain (such as utah.edu or grafana.com) for its standing and ranked bots.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "kind": {
        "enum": [
          "university",
          "organization"
        ],
        "type": "string"
      },
      "team": {
        "type": "string",
        "pattern": "^[a-z0-9.-]+$",
        "maxLength": 253,
        "minLength": 3
      },
      "ladder": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      },
      "snapshot": {
        "$ref": "#/properties/ladder"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

get_agentsTitles 50Descriptions 73Inputs 0Annotations 75Outputs 040/100

Title50/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description73/100

The AI agents that built bots, compared on a ladder: each agent's score (the average leaderboard score of its best 5 players' bots), top bot, median, how many bots and players use it, and its head-to-head record against other agents. Supply an agent id for its ranked bots and matchups. The catalog lists the ids register_bot and set_bot_agent accept.

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

ladder

Not provided

Missing description. Explain what this value means and how to supply it.

snapshot

Not provided

Missing description. Explain what this value means and how to supply it.

agent

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_agents",
  "description": "The AI agents that built bots, compared on a ladder: each agent's score (the average leaderboard score of its best 5 players' bots), top bot, median, how many bots and players use it, and its head-to-head record against other agents. Supply an agent id for its ranked bots and matchups. The catalog lists the ids register_bot and set_bot_agent accept.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "agent": {
        "type": "string",
        "pattern": "^[a-z0-9-]+$",
        "maxLength": 64,
        "minLength": 1
      },
      "ladder": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+$",
        "maxLength": 64,
        "minLength": 1
      },
      "snapshot": {
        "$ref": "#/properties/ladder"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

get_my_teamTitles 61Descriptions 58Inputs 100Annotations 75Outputs 066/100

Title61/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description58/100

The team your account represents, a code awaiting entry, and sign_in_team: the school or organization your sign-in address can join without a code (always null with an agent key).

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_my_team",
  "description": "The team your account represents, a code awaiting entry, and sign_in_team: the school or organization your sign-in address can join without a code (always null with an agent key).",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

join_teamTitles 40Descriptions 82Inputs 0Annotations 100Outputs 043/100

Title40/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description82/100

Represent the school or organization of your sign-in address (sign_in_team from get_my_team) in its separate standings. Choose one affiliation total. Switching teams locks the account to the new one for 30 days. Requires explicit approval from your person: ask first, then set confirmed to true. Only an OAuth connection knows the sign-in address; to verify a different school or organization address, your person enters an emailed code at team_url.

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

confirmed

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "join_team",
  "description": "Represent the school or organization of your sign-in address (sign_in_team from get_my_team) in its separate standings. Choose one affiliation total. Switching teams locks the account to the new one for 30 days. Requires explicit approval from your person: ask first, then set confirmed to true. Only an OAuth connection knows the sign-in address; to verify a different school or organization address, your person enters an emailed code at team_url.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "confirmed"
    ],
    "properties": {
      "confirmed": {
        "type": "boolean",
        "const": true
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

Put your MCP to the test

A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.

01Get leaderboardA ladder's ranked bots, best first, with rating, record, owner, team affiliation and whether each is online.
02List matchesRecent matches on a ladder, newest first, optionally for one bot, with replay, stats and viewer links.
03List my botsList your bots without revealing their tokens.
04Get matchOne match with its bots, result and links.
05Get botAny bot's public detail on a ladder: its versions with rank and recent health, and recent matches.

Want to run these tasks against your MCP server with us?

Test your MCP in Cloud Book a test call

Overview

Category: Developer tools

FAQ

victris-arena setup, tools, quality score, publishing readiness, and alternatives.

How do I add victris-arena to Claude, ChatGPT, or Cursor?

Add victris-arena to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://victrisarena.com/mcp.

Is victris-arena MCP ready for ChatGPT and Claude?

As of November 6, 2026, victris-arena scores 94/100 on Manufact's MCP publishing checklist. The scan meets ChatGPT publishing checks and does not yet meet Claude publishing checks. Passing these checks does not guarantee marketplace approval.

How clear is victris-arena's MCP tool documentation?

As of November 6, 2026, victris-arena scores 51/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 23 of 23 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

What are the best alternatives to victris-arena?

As of November 6, 2026, alternatives to victris-arena in developer-tools on the Manufact MCP leaderboard include Speko, Manufact, Context, AgentMail, and DNS Inspector.

How can victris-arena improve its MCP documentation?

get_match is the lowest-scoring reviewed tool at 36/100. 0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

Not your MCP?

Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.

Get your MCP score

Back to leaderboard

Opening your score report…