Skip to main content
Glama
Sign In
freedom-m2m-mcp-server

freedom-m2m-mcp-server

Official
by m2mfreedom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

freedom_stealth_unlocker

Fetch anti-bot protected web pages by rotating realistic browser profiles, returning clean Markdown, OpenGraph metadata, and JSON-LD structured data for LLM-ready input.

Instructions

Stealth Anti-Bot Web Unlocker (120 Sats / ~$0.113 USDC | 100/100 SLA Guaranteed). Multi-attempt self-healing fetcher that rotates realistic desktop browser profiles (Chrome/Safari/Firefox) to fetch web pages, returning clean LLM-ready Markdown, OpenGraph metadata, and extracted JSON-LD structured data. Zero-risk Pre-Flight validation & Atomic Token Protection via HTTP 402 (L402 Lightning / x402 Base & Solana).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "freedom_stealth_unlocker"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTarget public HTTP/HTTPS URL to unlock and convert to Markdown.
authHeaderNoOptional payment proof header if already settled: "L402 <macaroon>:<preimage>" or "x402 base:<0xTxHash>" or "x402 solana:<TxSignature>". Leave empty on first call to receive a 402 invoice challenge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose meaningful traits: multi-attempt self-healing with rotating Chrome/Safari/Firefox profiles, and the HTTP 402 payment flow (L402 Lightning / x402 Base & Solana) including pre-flight validation and token protection. It stops short of failure modes, timeouts, or rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single dense sentence that front-loads the tool name-style branding and buries the actual capability mid-string; marketing claims like '100/100 SLA Guaranteed' and 'Zero-risk' consume space without helping an agent invoke the tool. The pricing/payment detail is defensible, but the sentence is overstuffed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter, no-annotation, no-output-schema tool, the description usefully names the return payloads (Markdown, OpenGraph, JSON-LD) and explains the payment/settlement mechanism, which an agent needs before calling. Only error and retry-exhaustion behavior is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so url and authHeader are already fully documented in the schema, including the exact header formats. The description adds pricing context but no additional parameter meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (fetch/unlock web pages with anti-bot stealth) and names the exact return payloads (clean LLM-ready Markdown, OpenGraph metadata, JSON-LD). However, it never distinguishes itself from close siblings like freedom_clean_scraper or freedom_structured_extractor, so the anti-bot angle is left to be inferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No sentence states when to pick this over the sibling scrapers, nor any preconditions beyond the payment mechanics. The only actionable guidance ('Leave empty on first call to receive a 402 invoice challenge') lives in the schema, not the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools