ARGENTUM (giskard09/argentum-core) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Limited view
67/100
21 days ago

ARGENTUM

Karma economy for AI agents and humans. Submit good actions, get community attestations, earn on-chain reputation. Karma-weighted verification, slashing, Kleros disputes. 5 MCP tools: submit_action, attest_action, get_karma, get_action_detail, get_leaderboard.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

giskard09

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 11 credentials: OWNER_PRIVATE_KEY, MARKS_API_KEY, ARGENTUM_SIGNING_KEY, ARGENTUM_VERIFY_KEY, PHOENIXD_PASSWORD, WEBHOOK_SECRET, KLEROS_RULING_SECRET, DOCUSEAL_TOKEN, ADMIN_TOKEN, TELEGRAM_BOT_TOKEN, BREVO_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configARBITRUM_RPC
configGISKARD_CONTRACT_ADDRESS
configUSE_SIGNER
configSIGNER_WALLET_ID
configSIGNER_CHAIN_ID
🔐 secretOWNER_PRIVATE_KEY
🔐 secretMARKS_API_KEY
🔐 secretARGENTUM_SIGNING_KEY
🔐 secretARGENTUM_VERIFY_KEY"gdvrkAuw22AUH8+goZPZIYw2W3sLT/pPX3himAfnQIk="
configPAYG_WALLET
configARB_RPC
🔐 secretPHOENIXD_PASSWORD
🔐 secretWEBHOOK_SECRET
🔐 secretKLEROS_RULING_SECRET
configANCHOR_FRESHNESS_TTL_SECONDS
🔐 secretDOCUSEAL_TOKEN
configPIONEER_AGENT_API
🔐 secretADMIN_TOKEN
configMCP_TRANSPORT
configTRAILS_DB
🔐 secretTELEGRAM_BOT_TOKEN
configTELEGRAM_CHAT_ID
configENTERPRISE_AGENTS
configTRAIL_DAILY_LIMIT
🔐 secretBREVO_API_KEY
configADMIN_EMAIL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

15/15 tools missing one or more hints — open_dispute (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_dispute_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); submit_evidence (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

14/15 tool handlers declare input schemas (93%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 1/15 tool handlers wrap calls in try/catch (7%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Domain consistency

npm scope @mycelium doesn't match GitHub owner giskard09

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/giskard09-argentum-core-1fjoaa)](https://m8ven.ai/mcp/giskard09-argentum-core-1fjoaa)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 97e2c6d8d68fdf29acbd867c8692d034afaae35a
code hash: f4834212a53437c109beb5335b4b1dff6cb8141b5d32eaa1d48d106e82eae929
verified: 8/7/2026, 2:03:54 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client