Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

AgentID MCP

v1.0.0

Connect Claude Code to AgentID — persistent shared memory, live activity reporting, and multi-agent mission coordination via MCP

0· 75·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for colapsis/agentid-mcp.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "AgentID MCP" (colapsis/agentid-mcp) from ClawHub.
Skill page: https://clawhub.ai/colapsis/agentid-mcp
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install agentid-mcp

ClawHub CLI

Package manager switcher

npx clawhub@latest install agentid-mcp
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the instructions: the skill explains how to connect Claude Code to agentid.live, use an MCP secret, and read/write shared identity/memory and mission endpoints. It does not request unrelated binaries, credentials, or config paths.
Instruction Scope
All runtime instructions are scoped to the AgentID MCP protocol (report_activity, read/write memory, read_mission, etc.) and the agentid.live endpoints. The SKILL.md does not instruct reading local files, unrelated environment variables, or calling external endpoints outside agentid.live.
Install Mechanism
Instruction-only skill with no install spec and no code files — the lowest installation risk (nothing is downloaded or written to disk by the skill itself).
Credentials
The skill declares no required env vars, but the protocol requires placing an MCP secret (Bearer token) into Claude Code settings. This is proportional to the integration, but the user should treat that secret as sensitive and store it only in a secure agent config; do not reuse the secret elsewhere and avoid writing highly sensitive data into AgentID memory.
Persistence & Privilege
always is false and the skill does not request elevated platform privileges. Note: the SKILL.md tells the agent to act on mission handoffs immediately — that is functional behavior of the integration, so consider whether you want agents to autonomously execute handed-off work.
Assessment
This skill is coherent with its stated purpose, but before enabling it: (1) verify you trust https://agentid.live and review its privacy/security docs; (2) store the MCP secret only in Claude Code's secure settings and do not reuse it; (3) grant the integration the minimum privileges possible and rotate/revoke the secret if compromised; (4) avoid writing passwords or other highly sensitive secrets into AgentID memory; (5) be aware agents instructed to 'act on handoff immediately' may perform autonomous actions — test with low privileges first and monitor the AgentID dashboard for activity.

Like a lobster shell, security has layers — review code before you run it.

coordinationvk97enx9pdc1gx1v5xgxmrh3d3d84pfztidentityvk97enx9pdc1gx1v5xgxmrh3d3d84pfztlatestvk97enx9pdc1gx1v5xgxmrh3d3d84pfztmcpvk97enx9pdc1gx1v5xgxmrh3d3d84pfztmemoryvk97enx9pdc1gx1v5xgxmrh3d3d84pfztmulti-agentvk97enx9pdc1gx1v5xgxmrh3d3d84pfzt
75downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

AgentID MCP

AgentID gives your Claude agent a persistent identity with shared memory, activity reporting, and multi-agent mission coordination — all synchronized in real time across every instance of your agent.

Setup

1. Create your agent at agentid.live

Sign up at https://agentid.live, create an Identity, then create an Agent under it. You'll get:

  • An agent handle (e.g. my_agent)
  • An MCP secret from the agent's settings page

2. Add the MCP server to Claude Code

In your Claude Code settings, add the AgentID MCP server:

{
  "mcpServers": {
    "agentid-{your_handle}": {
      "type": "http",
      "url": "https://agentid.live/api/mcp/{your_handle}",
      "headers": {
        "Authorization": "Bearer {your_mcp_secret}"
      }
    }
  }
}

Replace {your_handle} and {your_mcp_secret} with the values from your agent's settings page.

3. Follow the session protocol

Once connected, the MCP server provides resources and tools. At the start of every session:

  1. Call report_activity(type="task.started", title="Session started", detail="<what the user asked>")
  2. Read your identity: agentid://identity/{handle}
  3. Read your memory: agentid://memory/{handle}
  4. Check for missions: read_mission()

Available MCP Tools

Memory

write_memory(key, value)
Store a persistent fact about the project or user. Use focused, specific keys — never one large blob.
Examples: project_stack, user_timezone, decision_deploy

read_memory(key?)
Read a specific memory key, or all memory if no key given.

search_memory(query)
Semantic search across all memory entries.


Activity Reporting

report_activity(type, title, detail, tokens_used?)
Report what you're doing — shows in the live Agency dashboard. Valid types:

  • task.started — before beginning a task
  • task.progress — at each meaningful step (detail required)
  • task.completed — when done (include tokens_used)
  • task.failed — on error

Detail is required on every call. Say specifically what happened — not "Task completed" but "Rewrote auth middleware, removed session token storage."


Multi-Agent Missions

Use these when multiple agents share the same identity and need to coordinate.

start_mission({ title, goal })
Declare a shared goal. Returns current status of all agents on this identity.

read_mission()
Read the active mission, all agent statuses, and any handoff addressed to you. Returns a YOUR ACTION section if a handoff targets your handle. Call this at session start.

update_status({ current_task, status })
Broadcast your current task to other agents. Status values: working | idle | done.

handoff({ summary, next_steps[], to? })
Pass work to another agent (or to: "any" for open pickup). Records what you completed and what comes next.


Session Protocol (copy into your CLAUDE.md)

SESSION START: Call report_activity (type="task.started"). Read identity and memory resources. Call read_mission() to check for active missions.

EVERY TASK: Call report_activity (task.started) before starting. Call report_activity (task.progress) at each meaningful step. Call report_activity (task.completed OR task.failed) when done.

MEMORY: Call read_memory at session start. Call write_memory whenever you learn a persistent fact.

MISSIONS: If a handoff is addressed to you, act on it immediately.

Resources

Comments

Loading comments...