well-006-url-metadata
dev.workers.mmelnyk2000.well-006-url-metadataPublished by well-006-url-metadata.mmelnyk2000.workers.devOfficial publisherv1.0.0Updated Oct 24, 2026
Page title, description and Open Graph tags. x402 $0.005 USDC, Base. As is, no warranty.
Overview
A remote MCP endpoint that returns a page's title, description and Open Graph metadata for a given URL.
- What you can do
- This server exposes a single metadata lookup capability: given a URL, it returns the page title, description and Open Graph tags. It runs as a hosted remote endpoint over streamable HTTP, so there is nothing to install locally. No tools are listed in the manifest, and no README is provided, so the exact tool names and parameters are not documented here.
- When to use it
- Useful when an assistant needs quick link previews, page titles or social-card metadata for URLs it is already working with, without fetching and parsing the HTML itself. It is a narrow, single-purpose service, so it only makes sense if metadata extraction is a recurring need.
- Requirements
- A remote streamable HTTP endpoint; no local runtime, package or environment variables are declared. No authentication is declared, but the description indicates each call is paid for with x402 at $0.005 USDC on Base, so a wallet or payment-capable client is needed.
Installation
In SourceWeft
- Open well-006-url-metadata in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.workers.mmelnyk2000.well-006-url-metadata%2Furl-metadata/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"well-006-url-metadata": {
"type": "http",
"url": "https://well-006-url-metadata.mmelnyk2000.workers.dev/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 16, 2026
Score
17% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.