Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Argo-RPG-Platform/argo-mcp

REMOTE · MCP.ARGO.GAMES · 2 COMPONENTS

MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2

0 this week 90 Trust /100

Last scanned (7 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 5427 tokens (~83/item across 65 items; 65 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management98
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 59% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 66 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Oct 26 0
    • Tool “create_session_summary_mnemons” rewrote its description, which is the text the model reads security
    • Tool “update_session_summary_mnemons” rewrote its description, which is the text the model reads security
  • 19 Oct 26 −1
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.1.0 ▼ security
    • Tool “create_player_mnemons” was removed ▼ security
    • Tool “create_mnemon_relationship” rewrote its description, which is the text the model reads security
    • Tool “update_player_mnemons” rewrote its description, which is the text the model reads security
    • Tool “update_npc_mnemons” rewrote its description, which is the text the model reads security
    • Tool “describe_mnemon_types” rewrote its description, which is the text the model reads security
    • Tool “create_npc_mnemons” rewrote its description, which is the text the model reads security
    • Schema quality: excellent → good functional
    • New tool “update_party_mnemons” functional
    • New tool “update_faction_mnemons” functional
    • New tool “create_faction_mnemons” functional
  • 30 Sept 26 0
    • Tool “create_quest_mnemons” rewrote its description, which is the text the model reads security
    • Tool “update_quest_mnemons” rewrote its description, which is the text the model reads security
    • Tool “get_mnemon” rewrote its description, which is the text the model reads security
    • Tool “create_mnemon_relationship” rewrote its description, which is the text the model reads security
    • New tool “set_quest_objective_state” functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Sept 26 0
    • Stability: fail → pass ▲ security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.argo.games/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.argo.games CN=WR3,O=Google Trust Services,C=US 10 Oct 2026 8 Jan 2027 RSA 2048 SHA256-RSA db0941ef737d5ec709921ed9686ad2a9
SANs: mcp.argo.games
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.argo.games. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
games. present 52900 8 Verified
argo.games. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.argo.games/.well-known/oauth-protected-resource", scope="campaign.read"

Bearer resource_metadata="https://mcp.argo.games/.well-known/oauth-protected-resource", scope="campaign.read"

Protected resource metadata

Document https://mcp.argo.games/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.argo.games
Authorisation server https://mcp.argo.games

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.argo.games/mcp Verified 200
http (plaintext) http://mcp.argo.games/mcp HTTPS enforced 302 https://mcp.argo.games/mcp
MCP tools · 65 exposed · ~5,265 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
set_quest_objective_state ~161

Tick, fail or reopen one objective of a quest by its id (get_mnemon's quest.objectives[].id), at any depth, without rewriting the quest. A GM sets any state. A player may only tick an objective they can see done, or undo that, and only while the quest's playersCanTick is on. Returns the quest as get_mnemon shows it, its progress recounted.

NameTypeReqDescription
campaignIdstringyesCampaign ID.
entryIdstringyesThe quest: entryId (hex) or exact title.
objectiveIdstringyesThe objective, as get_mnemon's quest.objectives[].id names it.
statestringyesopen, done or failed.
NameTypeReqDescription
blocksarrayyes–
entryIdstringyes–
questobject–Quests only: status, kind, objectives, reward chips and progress as this user may see them.
titlestringyes–
typestringyes–
typePropertiesobject––

No examples provided.

update_archive_mnemons ~36

Update typed/meta fields of Archive mnemons.

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

update_campaign ~118

Update a campaign's display name and/or description. Both fields optional — only supplied fields are changed; pass an empty string to clear the description. GMs and co-GMs can call this; rule-system swaps remain WebApp-only.

NameTypeReqDescription
campaignDescriptionstring–New description (setting, tone, premise). Omit to leave unchanged. Pass an empty string to clear the existing description.
campaignIdstringyesID of the campaign to update.
campaignNamestring–New display name. Omit to leave unchanged.
NameTypeReqDescription
campaignDescriptionstring|null––
campaignNamestringyes–
coGameMasterIds–––
gameMasterIdstringyes–
gameSystemSlugstring|null––
idstringyes–
ruleSystemstring|null––

No examples provided.

update_custom_mnemons ~38

Update typed/meta fields of Custom-typed mnemons.

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

update_faction_mnemons ~71

Update typed/meta fields of Faction mnemons (visibility, tags, members). An entry that is not a Faction fails its item. Does NOT modify content blocks — use update_mnemons_content for that.

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

update_journal_mnemons ~37

Update typed/meta fields of Journal mnemons.

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

update_location_mnemons ~36

Update typed/meta fields of Location mnemons.

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

update_lore_mnemons ~37

Update typed/meta fields of Lore mnemons.

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

update_mnemons_content ~237

Edit the body content of one or more mnemon entries. Each item carries an entryId and an ordered list of ops (append, insertAfter, replace, remove) applied atomically per entry. Op content is authored as Markdown (headings, lists, quotes, code fences, bold/italic, links) — do NOT send HTML. Mentions: @[label](mnemon:<entryId>). Images: ![caption](asset:<assetId>@<campaignId>) — upload the asset first; inline base64 / data: URLs are not accepted. Node addressing: get body-node ids from get_mnemon, then target them in replace/remove/insertAfter. A single op's Markdown may produce several nodes; new nodes get fresh server-generated ids (replace keeps the original id on the first new node). On a bad op (missing blockId, unknown op, etc.) the whole entry's batch is rejected with the failedOpIndex; no partial mutation per entry. See describe_mnemon_types.blockOps for the full vocabulary.

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

update_npc_mnemons ~104

Update typed/meta fields of NPC mnemons (visibility, tags, role, faction membership, etc.). An entry that is not an NPC fails its item; use update_faction_mnemons for a faction. Does NOT modify content blocks — use update_mnemons_content for that. Set visibility=PUBLIC on multiple NPCs in a single call by listing them in items[].

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

update_party_mnemons ~73

Update typed/meta fields of PlayerParty mnemons — one per party in the campaign. PlayerParty mnemons cannot be created: the server makes one for each party. Who may edit an entry is decided by its own permissions.

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

update_player_mnemons ~75

Update typed/meta fields of Player mnemons — one per character in a party. Player mnemons cannot be created: the server makes one for each character that joins a party. Who may edit an entry is decided by its own permissions.

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

update_quest_mnemons ~135

Update Quest mnemons. A field left out is left as it is: status, kind, playersCanTick, hook, the giverId / locationId / parentQuestId links (an empty string removes one), and objectives, rewards, background or gmNotes, each of which replaces its part of the quest and keeps the rest. Name existing objectives and chips by the ids get_mnemon's `quest` returns so they keep what the GM wrote under them. To tick one objective, use set_quest_objective_state.

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

update_session ~90

Reschedule a campaign session or edit its title/description. All fields optional. Owner-only on the backend.

NameTypeReqDescription
campaignIdstringyesCampaign ID.
descriptionstring––
endAtstring–ISO-8601 instant.
sessionIdstringyesSession ID.
startAtstring–ISO-8601 instant.
titlestring––
NameTypeReqDescription
attendanceReplies–––
campaignIdstringyes–
createdAtstring|null––
createdByUserIdstring|null––
descriptionstring|null––
endAtstring|null––
guildIdstring|null––
idstringyes–
invitedPartyIds–––
invitedUserIds–––
startAtstringyes–
titlestringyes–
updatedAtstring|null––

No examples provided.

update_session_summary_mnemons ~56

Update the recap, date, number and meta fields of SessionSummary mnemons. To change the story, use update_mnemons_content.

NameTypeReqDescription
campaignIdstringyes–
itemsarrayyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

Install

How do I install the io.github.Argo-RPG-Platform/argo-mcp server?

io.github.Argo-RPG-Platform/argo-mcp is a hosted endpoint at https://mcp.argo.games/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.argo.games

# add to Claude Code
claude mcp add --transport http argo-rpg-platform-argo-mcp 'https://mcp.argo.games/mcp'
Common questions

What is the io.github.Argo-RPG-Platform/argo-mcp server?

io.github.Argo-RPG-Platform/argo-mcp is listed in the public MCP registry as io.github.Argo-RPG-Platform/argo-mcp. MCP server for Argo RPG Platform, connects AI assistants to campaign data via OAuth2. This page covers its hosted endpoint (https://mcp.argo.games/mcp).

Is the io.github.Argo-RPG-Platform/argo-mcp server safe to use?

io.github.Argo-RPG-Platform/argo-mcp scores 90 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Argo-RPG-Platform/argo-mcp server expose?

io.github.Argo-RPG-Platform/argo-mcp exposes 65 tools: list_campaigns, get_campaign, create_campaign, update_campaign, list_co_gms, and 60 more. Their descriptions and schemas cost roughly 5,265 tokens of context every time the server is loaded.

Does the io.github.Argo-RPG-Platform/argo-mcp server require authentication?

Yes. io.github.Argo-RPG-Platform/argo-mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the io.github.Argo-RPG-Platform/argo-mcp server still maintained?

io.github.Argo-RPG-Platform/argo-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.