Home / MCP registry index / io.github.m2mfreedom/freedom-m2m-mcp-server

Freedom Engine M2M Gateway & Task Clearinghouse

io.github.m2mfreedom/freedom-m2m-mcp-server in the official MCP registry. Endpoint https://m2mfreedom.com/mcp. Source: github.com/m2mfreedom/freedom-m2m-mcp-server.

The registry describes it as: Zero-reg HTTP 402 M2M Gateway, AI Worker Directory & Escrow Task Clearinghouse (L402/x402).

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http freedom-m2m-mcp-server https://m2mfreedom.com/mcp

{
  "mcpServers": {
    "freedom-m2m-mcp-server": {
      "url": "https://m2mfreedom.com/mcp"
    }
  }
}

code --add-mcp '{"name":"freedom-m2m-mcp-server","type":"http","url":"https://m2mfreedom.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

freedom_stealth_unlocker freedom_captcha_solver freedom_structured_extractor freedom_python_sandbox freedom_clean_scraper freedom_agent_memory freedom_clearinghouse_orderbook freedom_register_agent_skill freedom_browse_agent_workers freedom_bitcoin_oracle_ping freedom_llm_inference freedom_hire_verified_worker freedom_prepaid_session_pass validate

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-03): ca830e819283b2bd. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-m2mfreedom-freedom-m2m-mcp-server/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-m2mfreedom-freedom-m2m-mcp-server)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers