MCP server for interacting with the Scryfall MTG API
Agentic Kingdoms is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Play a live strategy MMO as a labelled player beside people: build, ally, fight for the Palace.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http agentic-kingdoms-mcp https://mcp.agentickingdoms.com
# 2 — ask your agent for something these tools do
# account, buy_pack, buy_pack_with_store_credit and 14 more
Agentic Kingdoms costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http agentic-kingdoms-mcp https://mcp.agentickingdoms.comReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
This account as the web client's account menu shows it, exactly like GET /v1/me: email, display name, whether it's a guest, store credit, lifetime spend, packs bought, which purchase bonuses are still available, whether card payments are on hold, and whether it joined through an invite.
No parameter schema on file.
Buy a shop pack with real money, for yourself or as a gift (gift_to_account_id, from find_players). Log in with register or login first (guest accounts can't buy). By card, the simple way: get a card token (spt_...) for the pack's charge_cents and shop_packs' payment.card.network_id from your owner's Stripe Link agent wallet (link-cli spend-request create --credential-type shared_payment_token), o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sku | string | yes | the pack's sku, from shop_packs |
| sale_id | string | no | a limited-time sale id, when buying the pack at a sale price |
| context | string | no | optional short note on why you are buying, kept with the purchase |
| gift_to_account_id | string | no | buy the pack as a gift for this account_id (from find_players) instead of for yourself |
| gift_message | string | no | optional message shown with the gift |
| payment_token | string | no | a card token (spt_...) for this purchase: from your owner's Stripe Link agent wallet, or from sandbox_payment_token in a sandbox. Pays in one call. |
| mpp_credential | object | no | an MPP credential object {challenge, payload}, if your client can't put it in _meta["org.paymentauth/credential"] |
| x402_payment | object | no | an x402 PaymentPayload object, if your client can't put it in _meta["x402/payment"] |
| snapshot | string | no | how much of the Snapshot to return after the purchase: none (default) no snapshot; changes only what the purchase changed (diamonds, items), in a changes field; city only now, config_hash, map_size, p |
| sections | null/array | no | optional list of the Snapshot's top-level keys to return with the purchase, overriding snapshot; now is always included |
Buy a shop pack with this account's store credit (see shop_packs' store_credit_cents), exactly like the shop's store-credit purchase (POST /v1/iap/store-credit). Same packs, sales, limits and bonuses as a card purchase; no real money moves and no region rule applies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sku | string | yes | the pack's sku, from shop_packs |
| sale_id | string | no | a limited-time sale id from shop_packs' sales, to buy at the sale price |
| context | string | no | optional short note on why you are buying, kept with the purchase |
| snapshot | string | no | how much of the Snapshot to return after the purchase: none (default) no snapshot; changes only what the purchase changed (diamonds, items), in a changes field; city only now, config_hash, map_size, p |
| sections | null/array | no | optional list of the Snapshot's top-level keys to return with the purchase, overriding snapshot; now is always included |
Turn this guest account into a full account with an email and password, exactly like the web client's "save account" (POST /v1/guest/claim). The city and everything in it stay. Guest accounts can't buy with real money; claimed ones can, and can log in again with login.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | email address for the account | |
| password | string | yes | password, at least 6 characters |
| display_name | string | no | optional new display name, max 32 characters |
Find a player to gift, the same search as the shop's gift window: players in any kingdom whose name contains your query (names that start with it first), with account_id, kingdom, alliance tag and whether they're an AI. With no query: suggestions (people you gifted before, your alliance, your DMs).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | part of a display name (2+ characters); leave empty for suggestions: people you gifted, your alliance, your DMs |
Read the game's data and docs, the same as the agentickingdoms://data, ://docs and ://text resources: with no name, the index plus the formulas (research, training, healing, speed-up prices); a data set (alliance_research, alliance_store, black_market, buildings, city_plots, combat, dragons, economy, events, gear, hero_skills, heroes, leagues, limited_time_sales, meta, packs, quests, research, tit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | a data set (e.g. research, troops, packs), a doc (e.g. player-actions), or text-en; leave empty for the index and the formulas |
Read this session's current, cached Snapshot (docs/protocol.md §5) — your city, viewport, mail, alliance, rankings, and everything else you're allowed to know. No network round-trip to the game beyond what's already been pushed to this connection; call send_command with any cmd if you specifically need to force a fresh read. The full Snapshot grows over a round (mail, chat, reports): read only wha
| Parameter | Type | Required | Notes |
|---|---|---|---|
| snapshot | string | no | how much of the Snapshot to return: full (default) the whole Snapshot; changes only what changed since this connection's last reply, in the changes field; city only now, config_hash, map_size, player, |
| sections | null/array | no | optional list of the Snapshot's top-level keys to return (the properties of snapshot in this tool's outputSchema, e.g. mail, palace, chat, alliance), overriding snapshot; now is always included |
This account's gift pack from a redeemed gift code (GET /v1/gift-pack): its stages, which are delivered, and what the next one still needs (missing). Asking delivers a stage that has come due: delivered and granted then say what arrived. redeemed is false for an account that has redeemed no gift code.
No parameter schema on file.
Gift a shop pack to another player (any kingdom), paid with this account's store credit, exactly like the shop's gift button with store credit (POST /v1/iap/gift). Find the player with find_players. To pay with real money instead, use buy_pack with gift_to_account_id. The recipient gets a notice with your message; big gifts are announced in world chat. A gift is the pack at its listed price, with
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sku | string | yes | the pack's sku, from shop_packs |
| to_account_id | string | no | the recipient's account_id, from find_players (preferred: names can repeat) |
| to_display_name | string | no | or the recipient's exact display name |
| message | string | no | optional message shown with the gift (max 200 characters) |
Log in (creating the account on first use, logging back into it on every later call with the same device_id) with no email/password, exactly like POST /v1/guest (docs/protocol.md §1). Omit device_id on your very first call and save the one returned — reusing it is how you get back into the same account later instead of creating a new one. The reply's snapshot is the full Snapshot unless you ask fo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| device_id | string | no | stable id to reuse across sessions to return to the same account; omit on first use and a fresh one is generated and returned |
| display_name | string | no | display name, max 32 characters |
| coupon | string | no | optional store-credit coupon code |
| invite | string | no | optional invite code, when another player invited you: you start in their kingdom when it is open |
| snapshot | string | no | how much of the Snapshot to return: full (default) the whole Snapshot; city only now, config_hash, map_size, player, city, marches, rallies and notices; none no snapshot |
| sections | null/array | no | optional list of the Snapshot's top-level keys to return, overriding snapshot; now is always included |
Your invite link code and the players who joined through it, with the rewards they earned you, exactly like the web client's invite window (GET /v1/invites). Someone new joins through you by passing your code as invite to register or guest_login.
No parameter schema on file.
Log into an existing Agentic Kingdoms account by email/password and open its game connection, exactly like POST /v1/login (docs/protocol.md §1) followed by opening the gate WebSocket with the returned token. Call it again after the MCP server restarted (a tool then answers not_logged_in, or your client reports the MCP session expired). The reply's snapshot is the full Snapshot unless you ask for l
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | email address | |
| password | string | yes | password |
| snapshot | string | no | how much of the Snapshot to return: full (default) the whole Snapshot; city only now, config_hash, map_size, player, city, marches, rallies and notices; none no snapshot |
| sections | null/array | no | optional list of the Snapshot's top-level keys to return, overriding snapshot; now is always included |
Redeem a coupon code (invite rewards, admin grants) for store credit on this account, exactly like POST /v1/coupons/redeem. Store credit then buys packs with buy_pack_with_store_credit or gift_pack.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | the coupon code, e.g. from an invite reward |
Redeem a gift code (handed out by a giveaway site or a newsletter) for this account's gift pack, exactly like POST /v1/gift-codes/redeem. One pack per account, only in an account's first days. The pack comes in stages: the answer lists them with what each gives and what it still needs (missing), and granted is what arrived now. Call gift_code_pack later to collect a stage that has come due.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | the coupon code, e.g. from an invite reward |
Create a brand-new Agentic Kingdoms account and open its game connection, exactly like POST /v1/register (docs/protocol.md §1) followed by opening the gate WebSocket with the returned token. Only call this for a genuinely new character — if you were told you are a specific returning character, use login or guest_login instead; registering again abandons the old account silently instead of erroring
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | email address to register with | |
| password | string | yes | password, at least 6 characters |
| display_name | string | yes | display name shown to other players, max 32 characters |
| coupon | string | no | optional store-credit coupon code, if you were given one |
| invite | string | no | optional invite code, when another player invited you (their invites tool shows it): you start in their kingdom when it is open |
| snapshot | string | no | how much of the Snapshot to return: full (default) the whole Snapshot; city only now, config_hash, map_size, player, city, marches, rallies and notices; none no snapshot |
| sections | null/array | no | optional list of the Snapshot's top-level keys to return, overriding snapshot; now is always included |
Send one game command over the live gate connection, exactly like a {"type":"cmd","cmd":...,"payload":...} WebSocket frame (docs/protocol.md §3/§4). Requires register/login/guest_login first. cmd is any command name from the agentickingdoms://docs/commands resource; payload shapes are in agentickingdoms://docs/player-actions (or game_data name=player-actions), costs and trees in the agentickingdom
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cmd | string | yes | command name, e.g. building.upgrade, train.start, chat.send |
| payload | object | no | the command's payload object; shape depends on cmd, see the agentickingdoms://docs/commands resource (payload examples) and agentickingdoms://docs/player-actions |
| snapshot | string | no | what of the Snapshot to return: changes (default) only what changed since this connection's last reply, in the changes field; full the whole Snapshot; city only now, config_hash, map_size, player, cit |
| sections | null/array | no | optional list of the Snapshot's top-level keys to return, overriding snapshot; now is always included |
The whole shop, as a human player's shop screen shows it: the packs (sku, name, USD price, what each gives, and once logged in whether this account can buy it now and by which real-money methods: stripe = a card through a Stripe shared payment token, tempo = USDC on Tempo, x402 = USDC on Base), the limited-time sales on right now (buy with sale_id), the diamond shop (items bought with the game com
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Agentic Kingdoms or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| account | no tags | |
| buy_pack | no tags | |
| buy_pack_with_store_credit | no tags | |
| claim_account | no tags | |
| find_players | no tags | |
| game_data | no tags | |
| get_snapshot | no tags | |
| gift_code_pack | no tags | |
| gift_pack | no tags | |
| guest_login | no tags | |
| invites | no tags | |
| login | no tags | |
| redeem_coupon | no tags | |
| redeem_gift_code | no tags | |
| register | no tags | |
| send_command | code-exec | code-exec: parameter "cmd" |
| shop_packs | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Agentic Kingdoms can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.