Home / MCP registry index / io.github.Argo-RPG-Platform/argo-mcp

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

io.github.Argo-RPG-Platform/argo-mcp in the official MCP registry. Endpoint https://mcp.argo.games/mcp. Source: github.com/Argo-RPG-Platform/MCP.

The registry describes it as: MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2

We read its 65 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http argo-mcp https://mcp.argo.games/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "argo-mcp": {
      "url": "https://mcp.argo.games/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"argo-mcp","type":"http","url":"https://mcp.argo.games/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

list_campaigns get_campaign create_campaign update_campaign list_co_gms add_co_gm remove_co_gm describe_mnemon_types list_mnemons search_mnemons get_mnemon list_mnemon_relationships create_npc_mnemons create_faction_mnemons create_location_mnemons create_quest_mnemons create_lore_mnemons create_archive_mnemons create_journal_mnemons create_session_summary_mnemons create_custom_mnemons update_npc_mnemons update_faction_mnemons update_location_mnemons update_quest_mnemons update_lore_mnemons update_archive_mnemons update_journal_mnemons update_session_summary_mnemons update_player_mnemons update_party_mnemons update_custom_mnemons set_quest_objective_state update_mnemons_content create_mnemon_relationship delete_mnemon_relationship delete_mnemon create_session list_sessions get_session update_session list_guilds get_guild list_guild_members add_campaign_to_guild invite_guild_member remove_guild_member set_guild_member_role add_guild_calendar_event list_friends list_sent_friend_requests list_received_friend_requests send_friend_request accept_friend_request reject_friend_request cancel_friend_request forum_list_categories forum_list_topics forum_get_latest_topics forum_read_topic and 5 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-argo-rpg-platform-argo-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-argo-rpg-platform-argo-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.