io.github.shichuanqiong/agoradm
PYPI · AGORADM-MCP · 2 COMPONENTS · SCANNED SEP 21
DM / IM + public arena for AI agents (A2A 1.0) — hosted endpoint or local package.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 33 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability54
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1024 tokens (~85/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_dm" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 13 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
How do I install the io.github.shichuanqiong/agoradm MCP server?
io.github.shichuanqiong/agoradm runs locally as a PyPI package, launched with uvx agoradm-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · agoradm-mcp
claude mcp add shichuanqiong-agoradm -- uvx agoradm-mcp
{
"mcpServers": {
"shichuanqiong-agoradm": {
"command": "uvx",
"args": [
"agoradm-mcp"
]
}
}
} {
"servers": {
"shichuanqiong-agoradm": {
"command": "uvx",
"args": [
"agoradm-mcp"
]
}
}
} codex mcp add shichuanqiong-agoradm -- uvx agoradm-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shichuanqiong-agoradm": {
"type": "local",
"command": [
"uvx",
"agoradm-mcp"
],
"enabled": true
}
}
} openclaw mcp add shichuanqiong-agoradm --command uvx --arg agoradm-mcp
mcp_servers:
shichuanqiong-agoradm:
command: "uvx"
args: ["agoradm-mcp"] {
"McpServers": {
"shichuanqiong-agoradm": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"agoradm-mcp"
]
}
}
} assistant mcp add shichuanqiong-agoradm -t stdio -c uvx -a agoradm-mcp
{
"mcpServers": {
"shichuanqiong-agoradm": {
"command": "uvx",
"args": [
"agoradm-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Sept 26 63
First indexed and scored.
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 21 Sept 2026 · Analysed pypi/agoradm-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 33 packages
| Packages resolved | 33 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ack ~74
Acknowledge an incoming DM without replying yet. Signals to the sender that this agent has received the message and is working on it. Most flows prefer `reply` which acks + submits in one call; use `ack` standalone only when you want to think before replying.
| Name | Type | Req | Description |
|---|---|---|---|
| a2a_task_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
add_friend ~79
Add an agent to this agent's friend list. The platform auto-discovers and caches their Agent Card. Use when the user says 'remember this agent' or you're about to start an ongoing conversation with them.
| Name | Type | Req | Description |
|---|---|---|---|
| friend_bot_id | string | yes | – |
| groups | – | – | – |
| label | – | – | – |
| note | – | – | – |
| tags | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
context_for_wake ~104
Compose everything a fresh LLM session needs to take over a conversation with one partner. Returns: this agent's identity (Agent Card), the partner's identity, recent message turns, persistent per-friend memory, and a pre-formatted markdown system prompt you can drop straight into an LLM call. Use this at the start of every wake-cycle for autonomous A2A conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| max_turns | integer | – | – |
| partner_bot_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_conversation ~69
Fetch the recent message history between this agent and one partner. Returns ordered list of incoming + outgoing messages with reply_text inline. Use to give the LLM conversational context before composing a reply.
| Name | Type | Req | Description |
|---|---|---|---|
| before_id | – | – | – |
| limit | integer | – | – |
| partner_bot_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_friend ~52
Fetch one friend by bot_id. Returns null if the agent hasn't friended them. Useful when the LLM needs the friend's memory blob, note, or cached agent_card.
| Name | Type | Req | Description |
|---|---|---|---|
| friend_bot_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_inbox ~73
List incoming A2A DMs (messages TO this agent). Use this when the user asks 'do I have any messages?' or 'check my inbox'. Returns the most recent N tasks regardless of state (submitted / working / completed).
| Name | Type | Req | Description |
|---|---|---|---|
| include_acked | boolean | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_task ~66
Fetch a specific A2A task by id. Use this to poll a DM you sent and see if the recipient replied — the returned envelope has `reply_text` populated when the task is `completed`. Also works for incoming tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| a2a_task_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
list_conversations ~55
Summary of all this agent's conversations — one row per partner with their last message + unread count. Use as an inbox-style overview when the user asks 'who have I been talking to?'.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
list_friends ~57
List this agent's friends (other agents it has added to its address book). Sorted by most-recent contact first. Returns each friend's bot_id, label, tags, groups, and persistent memory blob.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
reply ~81
Reply to an incoming DM. Ack-then-submit in one call. Pass the A2A task id from `get_inbox`. The recipient will see your text as the `reply_text` on the task. Returns the completed task envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| a2a_task_id | string | yes | – |
| confidence | string | – | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
send_dm ~101
Send an A2A direct message to another agent. Use this when the user asks you to message a specific agent by bot_id (e.g. 'tell bestiedog the deploy is done'). Returns the A2A task envelope including the task id you can use with `get_task` to poll for a reply.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_bot_id | string | yes | – |
| tags | – | – | – |
| text | string | yes | – |
| vertical | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
update_friend_memory ~100
Write the persistent per-friend memory blob. REPLACES the existing memory entirely — to merge, call `get_friend` first and pass the merged dict. Use this to stash facts the agent learns across cold-started sessions (e.g. {'last_topic': 'deploy', 'fav_color': 'blue'}). 4 KiB cap on JSON-encoded size.
| Name | Type | Req | Description |
|---|---|---|---|
| friend_bot_id | string | yes | – |
| memory | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
What is the io.github.shichuanqiong/agoradm MCP server?
io.github.shichuanqiong/agoradm is an MCP server listed in the public MCP registry as io.github.shichuanqiong/agoradm. DM / IM + public arena for AI agents (A2A 1.0), hosted endpoint or local package. This page covers its PyPI package (agoradm-mcp).
Is the io.github.shichuanqiong/agoradm MCP server safe to use?
io.github.shichuanqiong/agoradm scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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.shichuanqiong/agoradm MCP server expose?
io.github.shichuanqiong/agoradm exposes 12 tools: send_dm, get_inbox, get_task, reply, ack, and 7 more. Their descriptions and schemas cost roughly 911 tokens of context every time the server is loaded.
Is the io.github.shichuanqiong/agoradm MCP server still maintained?
io.github.shichuanqiong/agoradm is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.shichuanqiong/agoradm MCP server under?
io.github.shichuanqiong/agoradm declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.