@true402.dev/mcp-server

link_preview

Fetch a URL and return its Open Graph card (title, description, image, site name, favicon, canonical). POST { url }; an unpaid request returns 402. Flat-priced per request.

Instructions

Fetch a URL and return its Open Graph card (title, description, image, site name, favicon, canonical). POST { url }; an unpaid request returns 402. Flat-priced per request. (PAID x402 service — USDC on Base; the MCP server needs a funded wallet to settle.) Price: $0.003 USD (fixed).

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": "link_preview"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The page URL (http/https)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.1Jun 20, 2026

TDQS

A3.7/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 well: it discloses the POST contract, the 402 response for unpaid requests, flat per-request pricing, the settlement chain (USDC on Base), and the hard prerequisite of a funded wallet. Remaining gaps are redirect/timeout behavior and whether failed or non-OG pages are charged.

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

Conciseness4/5

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

Purpose comes first in one dense sentence, followed by the transactional constraints. The final parenthetical is information-rich but slightly cluttered; nothing is truly wasted for a paid service.

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?

No output schema exists, and the description compensates by enumerating the return fields (title, description, image, site name, favicon, canonical) and covering the payment prerequisite. For a single-parameter read tool, an agent has enough to call it correctly, though failure modes other than 402 are 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 coverage is 100% with a single documented parameter, so the baseline is 3. The description adds only that the URL is sent as a POST body field, which marginally supplements the schema's "The page URL (http/https)" note.

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?

Opens with a specific verb and resource ("Fetch a URL and return its Open Graph card") and enumerates the exact returned fields, so the agent knows it is a pure card-metadata fetch rather than content extraction. It never names web_extract or screenshot, so the differentiation from those siblings must be inferred from the output list.

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

Usage Guidelines3/5

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

Implicit guidance only: the returned fields make clear this is for link previews/cards, and the payment block implies a pay-per-call service. There is no explicit statement of when to prefer this over web_extract or screenshot, nor any exclusion for non-HTML or paywalled URLs.

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