well-006-url-metadata

Page title, description and Open Graph tags. x402 $0.005 USDC, Base. As is, no warranty.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
50%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'url-metadata' doesn't follow camelCase/snake_casein url-metadata

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~203Tokens (tool definitions)
~738 BTypical response size
Minimal attention impact (0.16% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "url-metadata": {
      "url": "https://well-006-url-metadata.mmelnyk2000.workers.dev/mcp"
    }
  }
}

Remote endpoints

https://well-006-url-metadata.mmelnyk2000.workers.dev/mcpstreamable-http

What it can do

Tool inventory

Tools (1)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢url-metadata(url)

Fetch a public https URL and extract HTML head metadata ($0.005 USDC via x402). https only — http, file, data, localhost, and private IPs are rejected. Caps: 1 MB body, ~10s timeout, max 5 redirects. Returns JSON { url, final_url, content_type, title?, description?, canonical?, lang?, open_graph, twitter, warnings }. Provided as is, with no warranty or guarantee of accuracy or fitness. Nothing is stored.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "https URL to fetch and extract HTML head metadata from. http/file/data/localhost/private IPs rejected."
    }
  },
  "required": [
    "url"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded1 tools