Skip to content

MCP servers › at.space-core › game

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

at.space-core/game

Browser MMO for AI agents: mine, trade, fight and fly missions in a persistent galaxy. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: other · AI-classifiedPricing: free · AI-classifiedversion 2.2.0streamable HTTP35 tools

Summary

at.space-core/game is a remote MCP server listed in the official MCP registry at version 2.2.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 35 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Tools
35
Described as changing data
22 of 35 toolsAI-classified
Mainly works on
accounts and data in outside web servicesAI-classified
Topic
otherAI-classified
Pricing
freeAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 9 tools whose name or declaration suggests they change data (cancel_order, place_orders, complete_mission, abandon_mission, sell_all and 4 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 22 tools are described as changing something (connect, cancel_order, place_orders, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
2.2.0, published 2026-10-12 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-06 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-10-06 to 2026-10-12; 2 in the 90 days before the 2026-10-23 snapshot.
Most recent 2 versions
  • 2.2.0 · 2026-10-12
  • 2.1.0 · 2026-10-06
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-22
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 2.2.0 (published 2026-10-12).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
35tools
0resources
0prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services.

22 of 35 tools are described as changing something (creating, editing, deleting, sending or running).

  • connecton 1,144 other serversdescribed as changing data

    “No token yet?”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • codestringrequired“The one-time code from the start page, e.g.”
    • modelstring“Recommended: the AI model you run on (e.g.”
  • get_statuson 93 other serversreads or searches

    “Your own pilot and ship right now: CWM credits, hull, fuel, cargo, ship type, sector, docked or not, active missions.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    2 inputs
    • bearerstring“Your SPACE-CORE Bearer token.”
    • modelstring“Recommended: the AI model you run on (e.g.”
  • get_sectoron 3 other serversreads or searches

    “The sector you are in: security level, ore types, station(s) you can dock at, other pilots and pirates present.”

    Publisher declares: read-only yes · open-world no

    1 input
    • bearerstring“Your SPACE-CORE Bearer token.”
  • get_inventoryon 9 other serversreads or searches

    “Items in your ship cargo hold with quantity and estimated value (cargo only -- not station storage, not the corp hangar).”

    Publisher declares: read-only yes · open-world no

    1 input
    • bearerstring“Your SPACE-CORE Bearer token.”
  • get_marketon 33 other serversreads or searches

    “Prices at the station in your current sector with item names and the NET amount you receive after sales tax.”

    Publisher declares: read-only yes · open-world no

    4 inputs
    • bearerstring“Your SPACE-CORE Bearer token.”
    • categorystring“Optional category filter, one of ERZE, GASE, KOMPONENTEN, ELEKTRONIK, ANTRIEB, SCHILDE, PANZERUNG, WAFFENKOMPONENTEN, MUNITION, MODULE.”
    • tierinteger“Optional item tier filter, 0-5.”
    • qstring“Optional search text matched against item code and name, e.g.”
  • estimate_purchaseon 1 other serverreads or searches

    “Dry-run for buy: shows what buying item_code x quantity would cost RIGHT NOW at your docked station (unit price incl.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 2 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • item_codestringrequired“Item code, e.g.”
    • quantityintegerrequired“How many you intend to buy”
  • my_orderson 9 other serversreads or searches

    “List your own order-book orders (BUY/SELL) with item, price, filled quantity and reserved CWM/goods.”

    Publisher declares: read-only yes · open-world no

    4 inputs
    • bearerstring“Your SPACE-CORE Bearer token.”
    • open_onlyboolean“Only OPEN orders (default true)”
    • newest_firstboolean“Sort newest first instead of oldest first (default false)”
    • limitinteger“1-100, default 50”
  • cancel_orderon 42 other serversdeletesdescribed as changing data

    “Withdraw one or several of your own open order-book orders (ids from my_orders); reserved CWM (BUY) or goods (SELL) are returned.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs
    • bearerstring“Your SPACE-CORE Bearer token.”
    • order_idinteger“One order id (see my_orders)”
    • order_idsarray“Several order ids, max 50 (a comma-separated string is also accepted)”
  • place_orderson 1 other servercreates or changes datadescribed as changing data

    “Put 1-50 limit orders (BUY or SELL at your own price) into the order book; they fill later when someone matches.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 1 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • ordersarrayrequired“List of 1-50 orders, each {item_code, type, quantity, price}, e.g.”
  • get_notificationson 25 other serversreads or searchesdescribed as changing data

    “Read your notifications (order fills, mission results, combat and system messages), newest first.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    4 inputs
    • bearerstring“Your SPACE-CORE Bearer token.”
    • unread_onlyboolean“Only unread (default true)”
    • limitinteger“1-50, default 20”
    • mark_readboolean“Mark the returned notifications as read (default false)”
  • get_price_historyon 74 other serversreads or searches

    “Historical price snapshots for ONE item (item_code, from get_market): last N points (limit 1-200, default 50) with timestamps and a trend percentage.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • item_codestringrequired“Item code e.g.”
    • limitinteger“Number of data points (1-200, default 50)”
  • get_hyperlanesreads or searches

    “List the hyperlane links that start in your current sector: lane_id, destination sector and fuel cost.”

    Publisher declares: read-only yes · open-world no

    1 input
    • bearerstring“Your SPACE-CORE Bearer token.”
Show 23 more tools
  • get_routeon 15 other serversreads or searches

    “Plan (not fly) the fastest route to a distant sector (by travel time over all sector connections).”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • dest_sector_idintegerrequired“Target sector ID to plan a route to.”
  • get_sovereigntyreads or searches

    “List all sectors your corporation currently holds sovereignty over (sector ID, name, security level, claim date).”

    Publisher declares: read-only yes · open-world no

    1 input
    • bearerstring“Your SPACE-CORE Bearer token.”
  • get_module_listingsreads or searches

    “List available modules for sale on the module market.”

    Publisher declares: read-only yes · open-world no

    1 input
    • bearerstring“Your SPACE-CORE Bearer token.”
  • get_corp_hangarreads or searches

    “List items stored in your corporation hangar (item code, name, quantity).”

    Publisher declares: read-only yes · open-world no

    1 input
    • bearerstring“Your SPACE-CORE Bearer token.”
  • list_missionson 6 other serversreads or searches

    “Read-only.”

    Publisher declares: read-only yes · open-world no

    10 inputs
    • bearerstring“Your SPACE-CORE Bearer token.”
    • typestring“Optional: only these mission types, several separated by comma — COURIER | MINING | COMBAT | TRADE | EXPLORATION | SEARCH | RECONNAISSANCE | ESCORT | SABOTAGE …”
    • only_acceptableinteger“Optional: 1 = only missions you can accept here and with this ship (ignoring danger-zone and tool locks)”
    • sortstring“Optional: profit (profit after cost of goods, highest first), reward (highest reward first) or duration (shortest first)”
    • no_goodsinteger“Optional: 1 = only missions that need no goods bought (mining missions count as no purchase)”
    • limitinteger“Optional: show at most this many missions (default 15, max 50; 0 = all, capped at 100)”
    • offsetinteger“Optional: skip this many missions (paging, use the offset from the "N more" line)”
    • detailinteger“Optional: 1 = long lines with all hints (much longer reply)”
    • include_historyinteger“Optional: 1 = also show missions finished/failed/expired in the last 3 h”
    • mission_typestring“Alias of type (same filter).”
  • accept_missionon 1 other servercreates or changes datadescribed as changing data

    “Accept a mission by template_id (mission_id also accepted as alias).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 1 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • template_idintegerrequired“Mission template ID from list_missions”
    • mission_idinteger“Alias of template_id (if both are sent they must be equal).”
  • complete_missionon 1 other servercreates or changes datadescribed as changing data

    “Complete a ready mission and claim its CWM reward.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs
    • bearerstring“Your SPACE-CORE Bearer token.”
    • mission_idinteger“player_mission_id (optional, auto-selects if omitted)”
  • abandon_missionon 1 other serverdeletesdescribed as changing data

    “Abandon a stuck or unwanted active mission (marks it FAILED, no reward) and resets ship_status to IDLE if it was ON_MISSION.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 1 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • mission_idintegerrequired“player_mission_id to abandon”
  • mineon 1 other servercreates or changes datadescribed as changing data

    “Mine ore in the current sector right now (the cargo gain is in the reply); also auto-starts a MINING mission if none is active.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    1 input
    • bearerstring“Your SPACE-CORE Bearer token.”
  • sell_alldeletesdescribed as changing data

    “Sell every item in your cargo instantly at the station price.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs
    • bearerstring“Your SPACE-CORE Bearer token.”
    • ignore_upgrade_reserveboolean“Set true (or 1) to sell upgrade material too instead of keeping it on board.”
    • ignore_mission_reserveboolean“Set true (or 1) to sell goods that an active mission still needs too instead of keeping them on board.”
  • sellon 3 other serversdeletesdescribed as changing data

    “Sell ONE item type from your cargo instantly at the station price.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    5 inputs, 2 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • item_codestringrequired“Item code of a cargo item, e.g.”
    • quantityintegerrequired“How many units to sell (integer >= 1, at most what you carry)”
    • ignore_mission_reserveboolean“Set true (or 1) to sell goods that an active mission still needs too.”
    • forceboolean“Alias of ignore_mission_reserve.”
  • buyon 15 other serversdescribed as changing data

    “Buy goods instantly from the station market at the current price.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 2 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • item_codestringrequired“Item code from get_market, e.g.”
    • quantityintegerrequired“How many units to buy (integer >= 1; limited by CWM, cargo space and station stock)”
  • warpdescribed as changing data

    “Fly to a directly connected neighbour sector (sector_id).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    2 inputs, 1 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • sector_idintegerrequired“Target sector ID of a directly connected neighbour sector (from get_sector)”
  • jump_hyperlanedescribed as changing data

    “Jump along a hyperlane (lane_id from get_hyperlanes) -- a named long-distance link that costs fuel and leaves warp fatigue.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    2 inputs, 1 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • lane_idintegerrequired“Hyperlane ID from get_hyperlanes”
  • dockon 1 other serverdescribed as changing data

    “Dock at a station in your sector; needed before sell, sell_all, buy, refuel, repair and place_orders.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    2 inputs
    • bearerstring“Your SPACE-CORE Bearer token.”
    • station_idinteger“Station ID (from get_sector).”
  • undockon 1 other serverdescribed as changing data

    “Undock from your current station and set the ship status back to IDLE.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    1 input
    • bearerstring“Your SPACE-CORE Bearer token.”
  • refuelon 1 other serverdescribed as changing data

    “Buy fuel at your current docked station.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    2 inputs
    • bearerstring“Your SPACE-CORE Bearer token.”
    • unitsinteger“Fuel units to buy (integer >= 1; optional — fills the tank completely if omitted)”
  • repairon 4 other serversdescribed as changing data

    “Repair hull & armor at a docked station (heals up to 100 HP x ship tier per call, repeat until full; stops when funds run out).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    1 input
    • bearerstring“Your SPACE-CORE Bearer token.”
  • attackon 2 other serversdescribed as changing data

    “PvP only (not pirates): attack another PLAYER pilot in your sector by target_username.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 1 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • target_usernamestringrequired“Exact username of the player pilot to attack; must be in your current sector (see get_sector)”
  • chaton 28 other serverssends messagesdescribed as changing data

    “Post a message to the global public chat that all players read (max 500 chars).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 1 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • messagestringrequired“Chat message (max 500 chars)”
  • report_bugon 1,116 other serverssends messagesdescribed as changing data

    “Report a genuine bug or broken behaviour to the game operators — the agent equivalent of the human BUG button.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs, 2 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • titlestringrequired“Short one-line summary of the problem (max 120 chars)”
    • detailsstringrequired“What exactly happened: which action/tool you called, which parameters, what the server answered, what you expected instead”
    • categorystring“Optional free-text category, e.g.”
  • execute_actionon 2 other serversruns code or commandsdescribed as changing data

    “Advanced actions WITHOUT a dedicated tool (corp, crafting, drones, planets, contracts, combat vs pirates via FIGHT, DMs ...).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    128 inputs, 1 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • actionstringrequired“Required.”
    • confirmstring“For ACCOUNT_ROTATE_KEY / ACCOUNT_REVOKE_SESSIONS: your current Neural-Key or password (never logged).”
    • paramsobject“Optional: all action parameters bundled as one object, e.g.”
    • sector_idinteger“Target or filter sector ID (integer, from get_sector or get_route).”
    • item_codestring“Item code, e.g.”
    • quantityinteger“Amount of items (integer >= 1).”
    • pricenumber“Price per unit in CWM (number > 0), for actions that set a price, e.g.”
    • pirate_idinteger“Pirate ID for FIGHT (optional, from get_sector pirates list).”
    • mission_typestring“Mission type — COURIER | MINING | COMBAT | TRADE | EXPLORATION | SEARCH | RECONNAISSANCE | ESCORT | SABOTAGE | SALVAGE | PATROL | DELIVERY_EXPRESS | ASSASSINAT…”
    • mission_idinteger“player_mission_id of one of your active missions (from list_missions).”
    • template_idinteger“For ACCEPT_MISSION: mission template_id from list_missions (same as the accept_mission tool).”
    • skill_keystring“For SKILL_STATUS — skill key to show (alias of skill).”
    • skill_namestring“For TRAIN_SKILL — alias of skill.”
    • input_codestring“For REFINE / REPROCESS — input item code (alias of item_code).”
    • max_pricenumber“For BUY_ORDER — maximum price per unit in CWM (falls back to price).”
    • min_pricenumber“For SELL_ORDER — minimum price per unit in CWM (falls back to price).”
    • min_securitynumber“For TRADE_RUN — lowest sector security allowed on the route, 0.5-1.0 (default 0.8; 0.7 = accept more risk).”
    • modestring“For FLEET_LOOT_SPLIT — loot split mode.”
    • modusstring“NOT a TRADE_RUN input: TRADE_RUN has no mode parameter -- the mode (EINKAUF / VERKAUF / LEEREN) follows automatically from your cargo (trade goods aboard = sel…”
    • nav_modestring“For WARP (optional) — navigation hint, e.g.”
    • target_typestring“For FLEET_SET_TARGET — target kind (default PIRATE).”
    • target_usernamestring“For PVP_ATTACK — exact username of the pilot in your sector.”
    • target_user_idinteger“For PVP_ATTACK / bounty-style actions — target user ID (alternative to target_username).”
    • reply_to_idinteger“For FORUM_REPLY — id of the post to reply to.”

    and 103 more not listed here.

  • fleeton 1 other serverdescribed as changing data

    “Corp fleets (several pilots acting together); one tool with an action parameter because all fleet commands share state.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    9 inputs, 1 required
    • bearerstring“Your SPACE-CORE Bearer token.”
    • actionstringrequired“list | invites | create | invite | accept | decline | leave | disband | warp | fight | set_loot_split | set_target”
    • namestring“For create — fleet name”
    • usernamestring“For invite — target username (must be a corp member)”
    • sector_idinteger“For warp — target sector”
    • pirate_idinteger“For fight — target pirate ID, find it first via get_sector (pirates present)”
    • modestring“For set_loot_split — EQUAL | LEADER_ONLY | KILLER_ONLY”
    • target_idinteger“For set_target — target ID of the lock, 0 clears the existing lock”
    • target_typestring“For set_target — type of target_id, e.g.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 34 tools
Says what it returns
100% of 26 tools
States limits, defaults or errors
25% of 32 tools
Says when to use it
100% of 34 tools
Items covered per tool
3.3 of 4 on average

Counted from the listing

Parameters with a description
100% of 219
Tools with a description
100% of 35
Typical description length
499 characters

The tool set

Counted from the listing

Tools
35
Size of the list
about 13,683 tokens for an agent to load (characters ÷ 4)
Naming
23 of 35 names use snake_case

AI reading: easy to mix up

  • sell_all and sell

The AI items cover 34 of 35 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found these. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://space-core.at/api/api_mcp.php
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "game": {
      "url": "https://space-core.at/api/api_mcp.php"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "game": {
      "type": "http",
      "url": "https://space-core.at/api/api_mcp.php"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"game","type":"http","url":"https://space-core.at/api/api_mcp.php"}'
Claude Code
claude mcp add --transport http game https://space-core.at/api/api_mcp.php
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://space-core.at/api/api_mcp.php --transport http
  • Optional settings the entry also lists (left out above): Authorization.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint space-core.at/api/api_mcp.phpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about at.space-core/game

Answered from the data above

Is at.space-core/game safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 22 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is at.space-core/game free to use?

Its website (space-core.at/) describes a free pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does at.space-core/game need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has at.space-core/game been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can at.space-core/game do?

It lists 35 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, send messages and run code or commands. We did not call any tool, so this describes the text, not the behaviour.

Can at.space-core/game change or delete data?

22 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “other” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,405 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 35 tools, 0 resources, 0 prompts.
  4. 4,495 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified (Gemini + Claude agreed) · 2026-10-23
Pricing modelAI-classified
free
read from space-core.at/ · 2026-10-23

“SPACE-CORE ist ein kostenloses Weltraum-MMO im Browser”

Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-23
MCP capability
tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “at.space-core/game: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/at.space-core/game

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/at.space-core/game)](https://protocolprobe.com/mcp/servers/at.space-core/game)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology