ARGENTUM
REMOTE · ARGENTUM-MCP.RGISKARD.XYZ
Karma economy for AI agents. Community attestations, on-chain reputation on Arbitrum.
Available components
Last scanned (5 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 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
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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; "execute_trail" implies "execute" 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 10 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
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 Nov 26 +45
- HTTPS: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 2 Nov 26 −45
- Endpoint reachability: reachable → not serving MCP ▼ security
- HTTPS: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Sept 26 0
- Stability: 0.97 → pass security
- 29 Sept 26 0
- Stability: pass → 0.97 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
- 19 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: 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. security
- 18 Sept 26 0
- HSTS header: fail → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
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://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=YE2,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5bbe04716e3f66f9b43bf008cd03161ff32 |
| SANs: *.rgiskard.xyz, rgiskard.xyz | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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 →
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
| 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
| 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
| 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
| 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)
| 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
| 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)
| 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
| 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
| 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.)
| 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.
How do I install the ARGENTUM MCP server?
ARGENTUM is a hosted endpoint at https://argentum-mcp.rgiskard.xyz/sse, 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 · argentum-mcp.rgiskard.xyz
claude mcp add --transport http giskard09-argentum 'https://argentum-mcp.rgiskard.xyz/sse'
What is the ARGENTUM MCP server?
ARGENTUM is an MCP server listed in the public MCP registry as io.github.giskard09/argentum. Karma economy for AI agents. Community attestations, on-chain reputation on Arbitrum. This page covers its hosted endpoint (https://argentum-mcp.rgiskard.xyz/sse).
Is the ARGENTUM MCP server safe to use?
ARGENTUM scores 63 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 ARGENTUM MCP server expose?
ARGENTUM exposes 10 tools: submit_action, attest_action, get_karma, get_action_detail, register_trail, and 5 more. Their descriptions and schemas cost roughly 787 tokens of context every time the server is loaded.
Does the ARGENTUM MCP server require authentication?
No. We connected to ARGENTUM without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ARGENTUM MCP server still maintained?
ARGENTUM 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.