mcp-registry/io.github.moltycel/moltrust-mcp-server · v1.28.1
Also listed as awesome/moltycel/moltrust-mcp-server
As of 2026-10-18 20:31 UTC, the Moltycel Moltrust MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 8 minutes.
Give an agent a verifiable identity, and check another agent's before dealing with it.
Claude Code
claude mcp add --transport http moltycel-moltrust-mcp-server https://api.moltrust.ch/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"moltycel-moltrust-mcp-server": {
"type": "http",
"url": "https://api.moltrust.ch/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
56 of 56 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
56 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
137 parameter(s) across 48 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,811 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 48 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.moltycel%2Fmoltrust-mcp-server/fixes
{
"name": "ads_check",
"description": "Allow / hold / forbid for one intended Amazon Ads MCP tool call, before it runs.\n\n Needs your MolTrust API key as the X-API-Key header of the MCP connection (free key:\n POST https://api.moltrust.ch/auth/signup). Counts against your plan like any check.\n Never send Amazon credentials: they are refused.\n\n Args:\n profile: the `profile` object from ads_mandate_template\n tool: the Amazon Ads MCP tool name, e.g. campaign_management-update_campaign_budg",
"inputSchema": {
"type": "object",
"title": "ads_checkArguments",
"required": [
"profile",
"tool",
"arguments"
],
"properties": {
"tool": {
"type": "string",
"title": "Tool"
},
"context": {
"anyOf": [
{
"type": "object",
"additionalProperties": true
},
{
"type": "null"
}
],
"title": "Context",
"default": null
},
"profile": {
"type": "object",
"title": "Profile",
"additionalProperties": true
},
"arguments": {
"type": "object",
"title": "Arguments",
"additionalProperties": true
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "moltrust_deposit_info",
"description": "Get USDC deposit instructions to buy MolTrust credits.\n\n Returns the MolTrust wallet address on Base (Ethereum L2),\n USDC token contract, conversion rate (1 USDC = 100 credits),\n and step-by-step instructions.\n ",
"inputSchema": {
"type": "object",
"title": "moltrust_deposit_infoArguments",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "moltrust_stats",
"description": "Get MolTrust network statistics.\n\n Returns total registered agents, credentials issued,\n ratings given, and other network health metrics.\n ",
"inputSchema": {
"type": "object",
"title": "moltrust_statsArguments",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.moltycel/moltrust-mcp-server"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.moltycel/moltrust-mcp-server"}) over MCP.
ads_mandate_template ~547 tokensmt_fantasy_commit ~370 tokensmt_issue_music_credential ~327 tokensmt_travel_issue_vc ~312 tokensmt_endorse_agent ~299 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.moltycel%2Fmoltrust-mcp-server?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.moltycel%2Fmoltrust-mcp-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.moltycel%2Fmoltrust-mcp-server.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.moltycel%2Fmoltrust-mcp-server.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.moltycel%2Fmoltrust-mcp-server?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c1dd1a19e1bb1fdf…, first seen 2026-10-17, included at leaf 4788 of 23,302. Version history · verify what your client received.
Compare: most reliable security servers · most reliable other servers · most reliable data servers · most reliable knowledge servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 20:31 UTC, the Moltycel Moltrust MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 8 minutes.
Moltycel Moltrust MCP server advertises 56 tools, including ads_check, ads_mandate_template, ads_onboard, moltguard_credential_issue, moltguard_credential_verify.
Point your MCP client at this streamable-http endpoint: https://api.moltrust.ch/mcp
Glimind scanned all 56 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.