ARGENTUM

REMOTE · ARGENTUM-MCP.RGISKARD.XYZ · SCANNED AUG 3

Karma economy for AI agents. Community attestations, on-chain reputation on Arbitrum.

Available components

+2 this week 50 50 Trust /100

Trust breakdown (6 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 →

Endpoint Security46

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability40

Verified sse transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability57

AI-judged instruction clarity (fair).Partial
Tool/resource definitions use about 787 tokens (~78/item across 10 items; 10 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · argentum-mcp.rgiskard.xyz

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http giskard09-argentum https://argentum-mcp.rgiskard.xyz/sse

# ~/.codex/config.toml

[mcp_servers.giskard09-argentum]
url = "https://argentum-mcp.rgiskard.xyz/sse"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "giskard09-argentum": {
      "type": "remote",
      "url": "https://argentum-mcp.rgiskard.xyz/sse",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add giskard09-argentum --url https://argentum-mcp.rgiskard.xyz/sse --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  giskard09-argentum:
    url: "https://argentum-mcp.rgiskard.xyz/sse"

// mcp.json

{
  "mcpServers": {
    "giskard09-argentum": {
      "type": "http",
      "url": "https://argentum-mcp.rgiskard.xyz/sse"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

3 Aug 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.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 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
30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +26
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 22

First indexed and scored.

Show 6 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://argentum-mcp.rgiskard.xyz/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=rgiskard.xyz	CN=YE1,O=Let's Encrypt,C=US	26 Jul 2026	24 Oct 2026	ECDSA 256	ECDSA-SHA384	6d05006d650dfbdb7edbda6cdbe6fc902e5
SANs: *.rgiskard.xyz, rgiskard.xyz
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of argentum-mcp.rgiskard.xyz. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
xyz.	present	3599, 18130	8, 8	Verified
rgiskard.xyz.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	405

Transports 2 probes

Transport	URL	Outcome	Status	Location
sse	https://argentum-mcp.rgiskard.xyz/sse	Verified	200
http (plaintext)	http://argentum-mcp.rgiskard.xyz/sse	Served over HTTP	200

MCP tools — 10 exposed · ~787 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.

Tool Tokens

attest_action ~89

Attest (verify) someone else's action. Your karma weight counts toward verification. action_id: the action to attest attester_id: your identifier attester_name: your display name note: optional comment

Input Output Examples

Name	Type	Req	Description
action_id	string	yes	—
attester_id	string	yes	—
attester_name	string	yes	—
note	string	—	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

execute_trail ~130

Record execution of a Mycelium Trail. The executor self-attests success or failure. trail_id: the trail being executed executor_id: your unique identifier executor_name: your display name status: 'success' or 'fail' output_hash: optional sha256 of the output payment_hash: optional Lightning payment hash

Input Output Examples

Name	Type	Req	Description
executor_id	string	yes	—
executor_name	string	yes	—
output_hash	string	—	—
payment_hash	string	—	—
status	string	—	—
trail_id	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_action_detail ~37

Get details of a specific action including attestations. action_id: the action to look up

Input Output Examples

Name	Type	Req	Description
action_id	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_karma ~41

Check an entity's karma, verified actions, and attestations given. entity_id: the entity to look up

Input Output Examples

Name	Type	Req	Description
entity_id	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_leaderboard ~39

Get the karma leaderboard — top entities by reputation. top: how many to show (default 10)

Input Output Examples

Name	Type	Req	Description
top	integer	—	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_trail ~38

Get details of a Mycelium Trail including its step sequence. trail_id: the trail id

Input Output Examples

Name	Type	Req	Description
trail_id	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

list_trails ~60

List Mycelium Trails available for execution. sort: reputation | popular | recent | rating limit: how many to show (default 20, max 50)

Input Output Examples

Name	Type	Req	Description
limit	integer	—	—
sort	string	—	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

rate_trail ~71

Rate a Trail execution 1..5. Cannot rate own trail. trail_id: the trail execution_id: the execution to rate rating: 1..5

Input Output Examples

Name	Type	Req	Description
execution_id	string	yes	—
rating	integer	yes	—
trail_id	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

register_trail ~140

Register a Mycelium Trail — a verifiable recipe of MCP service calls. author_id: your unique identifier author_name: your display name name: short trail name description: what the trail does steps_json: JSON list of steps, each {"service": "...", "tool": "...", "note": "..."} price_sats: cost in sats per execution

Input Output Examples

Name	Type	Req	Description
author_id	string	yes	—
author_name	string	yes	—
description	string	yes	—
name	string	yes	—
price_sats	integer	yes	—
steps_json	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

submit_action ~142

Submit a good action to ARGENTUM for community verification. entity_id: your unique identifier (e.g. GitHub username) entity_name: display name entity_type: 'human' or 'agent' action_type: HELP | BUILD | TEACH | FIX | WITNESS | CONNECT | RELEASE description: what you did proof: URL to evidence (GitHub PR, commit, etc.)

Input Output Examples

Name	Type	Req	Description
action_type	string	yes	—
description	string	yes	—
entity_id	string	yes	—
entity_name	string	yes	—
entity_type	string	yes	—
proof	string	—	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	22
27 Jul	48
28 Jul	49
29 Jul	49
30 Jul	48
31 Jul	48
1 Aug	49
2 Aug	49
3 Aug	50