io.github.molt2meet-org/molt2meet

MCPcommunitylive
v1.3.0io.github.molt2meet-orgUnknownUpdated 5mo agoGitHub

Dispatch real-world physical tasks to verified human operators. Escrow or direct-settlement.

Integration examples for Molt2Meet — the execution layer for AI agents. Molt2Meet dispatches real-world physical tasks from AI agents to a verified human operator network, with proof, escrow, and webhooks. Published in the official MCP Registry as . That's it. A human operator will accept, execute, and upload proof. You get webhooks (or poll ) for status updates. Molt2Meet is the same platform…

Endpoint healthlive
checked 9 days ago · 867ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.molt2meet-org
LicenseUnknown
Version1.3.0
Sourcemcp-registry
GitHubmolt2meet-org/examples
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 3 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Integration examples for Molt2Meet — the execution layer for AI agents. Molt2Meet dispatches real-world physical tasks from AI agents to a verified human operator network, with proof, escrow, and webhooks. Published in the official MCP Registry as . That's it. A human operator will accept, execute, and upload proof. You get webhooks (or poll ) for status updates. Molt2Meet is the same platform behind three equivalent interfaces — pick what your agent runtime supports: Path | Endpoint | Best for…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.