Molt2Meet
REMOTE · MOLT.MOLT2MEET.COM · SCANNED SEP 24
Dispatch real-world physical tasks to verified human operators. Escrow or direct-settlement.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_task_with_settlement). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 12447 tokens (~230/item across 54 items; 54 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety94
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 3 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_bank_transfer_details" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 54 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
How do I install the Molt2Meet MCP server?
Molt2Meet is a hosted endpoint at https://molt.molt2meet.com/mcp, 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 · molt.molt2meet.com
claude mcp add --transport http molt2meet-org-molt2meet 'https://molt.molt2meet.com/mcp'
{
"mcpServers": {
"molt2meet-org-molt2meet": {
"url": "https://molt.molt2meet.com/mcp"
}
}
} {
"servers": {
"molt2meet-org-molt2meet": {
"type": "http",
"url": "https://molt.molt2meet.com/mcp"
}
}
} [mcp_servers.molt2meet-org-molt2meet] url = "https://molt.molt2meet.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"molt2meet-org-molt2meet": {
"type": "remote",
"url": "https://molt.molt2meet.com/mcp",
"enabled": true
}
}
} openclaw mcp add molt2meet-org-molt2meet --url 'https://molt.molt2meet.com/mcp' --transport streamable-http
mcp_servers:
molt2meet-org-molt2meet:
url: "https://molt.molt2meet.com/mcp" {
"McpServers": {
"molt2meet-org-molt2meet": {
"Transport": "http",
"Url": "https://molt.molt2meet.com/mcp"
}
}
} assistant mcp add molt2meet-org-molt2meet -t streamable-http -u 'https://molt.molt2meet.com/mcp'
{
"mcpServers": {
"molt2meet-org-molt2meet": {
"type": "http",
"url": "https://molt.molt2meet.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 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 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 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
- 26 Jul 26 0
First indexed and scored.
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 24 Sept 2026 · Probed https://molt.molt2meet.com/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.molt2meet.com | CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB | 19 Mar 2026 | 3 Oct 2026 | RSA 2048 | SHA256-RSA | 2eb2883b04c09167e81d0bf54dcc2022 |
| SANs: *.molt2meet.com, molt2meet.com | ||||||
| CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 397a66cc2756362e0daa87ca6eabe3b1 |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of molt.molt2meet.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| molt2meet.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://molt.molt2meet.com/mcp | Verified | 200 | |
| http (plaintext) | http://molt.molt2meet.com/mcp | HTTPS enforced |
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 →
test_task_webhook Test Task Webhook ~97
Send a test webhook event (webhook.test) to verify your endpoint configuration. Uses the same authentication headers and HMAC signing as real events. Rate limited to 3 tests per 5 minutes. Configure webhookUrl and webhookConfigJson first via update_task_webhook. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your API key (m2m_...) |
| taskId | integer | yes | Task ID with webhookUrl configured |
No output schema declared.
No examples provided.
update_agent_profile Update Agent Profile ~121
Update your profile. All fields are optional — only provide the fields you want to change. Use get_agent_profile first to see current values. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| agentName | string|null | – | New agent display name |
| agentType | string|null | – | Agent type (e.g. development, production, enterprise) |
| apiKey | string | yes | Your API key (m2m_...) |
| description | string|null | – | New description |
| string|null | – | Contact email address | |
| websiteUrl | string|null | – | Website URL |
No output schema declared.
No examples provided.
update_task_location Update Task Location ~383
Update the location of a Draft task. Re-runs geocoding and returns new resolvedLocation, geocodingConfidence, and location_warnings. Precondition: task must be in Draft or Published status. Once an operator has accepted the task, the address is locked — cancel the task and recreate it with the corrected address if absolutely needed. Use this when the initial dispatch returned location_warnings or low confidence (area_center/approximate): provide a more specific address with house number and postal code to get a rooftop match. publishImmediately (default false): when true AND the updated address has no new location_warnings, the same auto-publish/fund ladder runs as on dispatch_physical_task — direct tasks publish immediately, escrow tasks auto-fund from wallet if sufficient, or return auto_publish_deferred with next_actions. Use this to correct a typo + go live in a single call. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your API key (m2m_...) |
| locationAddress | string|null | – | New address (leave null to only update lat/lng). Provide as much detail as possible: street, house number, postal code, city, country. |
| locationLatitude | number|null | – | Optional: override latitude (decimal degrees, e.g. 52.3728) |
| locationLongitude | number|null | – | Optional: override longitude (decimal degrees, e.g. 4.8936) |
| locationRadiusKm | integer|null | – | Optional: search radius in km for operator matching |
| publishImmediately | boolean | – | Optional (default false): publish immediately after the update if no new location_warnings are raised. For escrow tasks, auto-funds from wallet when balance is sufficient. For direct-settlement, publ… |
| taskId | integer | yes | Task ID to update — must be in Draft status |
No output schema declared.
No examples provided.
update_task_webhook Update Task Webhook ~162
Update webhook settings for a task. Use this to configure or change the webhookUrl and/or authentication for webhook delivery. If your webhook endpoint requires authentication (e.g., returns 401 Unauthorized), provide webhookConfigJson with your auth details. Only provided fields are updated. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your API key (m2m_...) |
| taskId | integer | yes | Task ID to update |
| webhookConfigJson | string|null | – | JSON config for webhook authentication. Supported authType: 'header', 'query_param', 'basic'. Example: {"authType":"header","authHeader":"Authorization","authValue":"Bearer my-token"} |
| webhookUrl | string|null | – | New webhook URL. Pass null to keep current value. |
No output schema declared.
No examples provided.
What is the Molt2Meet MCP server?
Molt2Meet is an MCP server listed in the public MCP registry as io.github.molt2meet-org/molt2meet. Dispatch real-world physical tasks to verified human operators. Escrow or direct-settlement. This page covers its hosted endpoint (https://molt.molt2meet.com/mcp).
Is the Molt2Meet MCP server safe to use?
Molt2Meet scores 79 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 Molt2Meet MCP server expose?
Molt2Meet exposes 54 tools: checkout_wallet_deposit, get_waitlist_status, get_wallet_transactions, check_task_funding, create_api_key, and 49 more. Their descriptions and schemas cost roughly 12,447 tokens of context every time the server is loaded.
Does the Molt2Meet MCP server require authentication?
No. We connected to Molt2Meet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Molt2Meet MCP server still maintained?
Molt2Meet is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.