Skip to main content
Glama
rocnubie

Banned from Equestria MCP Server

by rocnubie
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

Banned from Equestria MCP Server

Banned from Equestria (Daily) - Play Online

MCP Badge Read Only License: MIT MCP Zero Config Node

A Model Context Protocol server that exposes the canonical Banned from Equestria knowledge surface — game rules, modes, constraints, and entry points, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.

Official website: https://bannedfromequiti.online

🎮 About Banned from Equestria

Banned from Equestria is an independent fan archive for the adult Banned from Equestria Daily Flash game. It preserves versions 1.0 through 1.5 and lets visitors play them in a browser through a self-hosted Ruffle player, without a Flash plugin.

The site includes English and Spanish pages, an 18+ age gate, version notes, character and cheat guides, and download hubs for Android, Windows, and SWF files. This MCP exposes that public scope and the official archive links as read-only context; it does not reproduce the game or verify third-party downloads.

The archive is not affiliated with Hasbro, My Little Pony rights holders, or the original game creator. Visitors should review the live archive and its credits before using any download.

Related MCP server: Muse AI Image MCP Server

Tools

get_game_rules

Return the verified game rules, modes, constraints, and public entry points the site exposes. (Banned from Equestria)

Input: no parameters. Returns: text/markdown.

get_official_links

Return the canonical list of official links for Banned from Equestria (website, support, docs when available).

Input: no parameters. Returns: text/markdown.

Resources

  • site://bannedfromequiti/rules — Verified game rules, modes, constraints, and public entry points.

  • site://bannedfromequiti/faq — Short FAQ generated from public site metadata.

  • site://bannedfromequiti/links — Canonical URLs to share with users.

Prompts

tell_me_about_bannedfromequiti

Summarize what the site is, who it's for, and how it works. — Banned from Equestria

plan_a_run_bannedfromequiti

Plan a single play-through using verified rules and entry points. — Banned from Equestria

Installation

Install via Smithery

npx -y @smithery/cli install bannedfromequiti-mcp --client claude

(Replace claude with cursor, windsurf, or continue for those clients.)

Install from source

git clone https://github.com/rocnubie/bannedfromequiti-mcp.git
cd bannedfromequiti-mcp
pnpm install

Then add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):

{
  "mcpServers": {
    "bannedfromequiti-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/bannedfromequiti-mcp/src/index.mjs"
      ]
    }
  }
}

Debug with MCP Inspector

npx @modelcontextprotocol/inspector node src/index.mjs

Official Links

Development

pnpm install
pnpm start                 # run the server over stdio

License

MIT

Available Tools

2 tools
get_game_rulesA

Return the verified game rules, modes, constraints, and public entry points the site exposes. (Banned from Equestria)

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It mentions 'verified' and the cryptic '(Banned from Equestria)', but does not disclose caching, rate limits, or authentication requirements. For a simple read-only tool this is minimally acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence plus a parenthetical, efficiently conveying the purpose. It is well-structured and front-loaded, though the parenthetical adds minimal value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters, no output schema, and a straightforward task, the description covers the basics: what is returned (rules, modes, constraints, entry points). It could be more precise about 'public entry points' but is sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so the baseline is 4. The description does not need to add parameter information, and it correctly omits any.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns 'verified game rules, modes, constraints, and public entry points', using a specific verb and resource. It distinguishes itself from the sibling tool 'get_official_links' by implying it deals with rules/constraints rather than links.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. The sibling tool 'get_official_links' is mentioned but no comparison or exclusion criteria given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.0
    • First observedget_game_rules
    • First observedget_official_links
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0
Disambiguation5/5

The two tools serve clearly distinct purposes: one returns game rules and modes, the other returns official links. There is no overlap or ambiguity in their functions.

Naming Consistency5/5

Both tools follow a consistent 'get_' prefix followed by a specific noun phrase (game_rules, official_links), making the naming pattern predictable and clear.

Tool Count3/5

With only two tools, the server feels minimally scoped. While it may serve a narrow purpose of providing reference information, the count is at the lower end of what is typically reasonable for an MCP server.

Completeness2/5

The tool set covers only basic information retrieval (rules and links). Given the server name implies a broader game-related purpose, there are obvious gaps such as missing tools for gameplay, user interaction, or dynamic data.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rocnubie/bannedfromequiti-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server