A
licenseNot graded
qualityD
maintenanceZero-signup link-preview API that returns clean metadata (title, description, image, etc.) from any public URL. No API key required.
2
MIT
LinkMeta
by dev.linkmeta
Server Details
Free URL metadata extraction API. Extract titles, descriptions, Open Graph tags, and favicons from any URL. No API keys required.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Added
validate_metadata
2 tool updates
- Changed
batch_extract_metadata1 field changed- changed
Input schema / properties / fields / descriptionPrevious value: -"Comma-separated fields to return (e.g. \"title,body,summary,redirectChain\"). Include \"body\" for clean extracted page text."New value: +"Comma-separated fields to return (e.g. \"title,body,summary,statusCode,contentType\"). Include \"body\" for clean extracted page text."
- Changed
extract_metadata1 field changed- changed
Input schema / properties / fields / descriptionPrevious value: -"Comma-separated fields to return (e.g. \"title,body,summary,redirectChain\"). Include \"body\" for clean extracted page text. Available: url,title,description,image,favicon,siteName,type,locale,language,author,publishedDate,modifiedDate,keywords,themeColor,canonical,wordCount,summary,body,redirectChain,twitter,openGraph,jsonLd,responseTime"New value: +"Comma-separated fields to return (e.g. \"title,body,summary,statusCode,contentType\"). Include \"body\" for clean extracted page text. Available: url,statusCode,contentType,title,description,image,favicon,siteName,type,locale,language,author,publishedDate,modifiedDate,keywords,themeColor,canonical,wordCount,summary,body,redirectChain,twitter,openGraph,jsonLd,responseTime"
2 tool updates
- Changed
batch_extract_metadata2 fields changed- changed
Input schema / properties / fields / descriptionPrevious value: -"Comma-separated fields to return (e.g. \"title,body,summary\"). Include \"body\" for clean extracted page text."New value: +"Comma-separated fields to return (e.g. \"title,body,summary,redirectChain\"). Include \"body\" for clean extracted page text." - added
Input schema / properties / timeoutAdded value: +{ + "description": "Request timeout in milliseconds (default 10000, max 30000). Increase for slow-responding targets.", + "type": "number" +}
- Changed
extract_metadata2 fields changed- changed
Input schema / properties / fields / descriptionPrevious value: -"Comma-separated fields to return (e.g. \"title,body,summary\"). Include \"body\" for clean extracted page text. Available: url,title,description,image,favicon,siteName,type,locale,language,author,publishedDate,modifiedDate,keywords,themeColor,canonical,wordCount,summary,body,twitter,openGraph,jsonLd,responseTime"New value: +"Comma-separated fields to return (e.g. \"title,body,summary,redirectChain\"). Include \"body\" for clean extracted page text. Available: url,title,description,image,favicon,siteName,type,locale,language,author,publishedDate,modifiedDate,keywords,themeColor,canonical,wordCount,summary,body,redirectChain,twitter,openGraph,jsonLd,responseTime" - added
Input schema / properties / timeoutAdded value: +{ + "description": "Request timeout in milliseconds (default 10000, max 30000). Increase for slow-responding targets.", + "type": "number" +}
2 tool updates
- Changed
batch_extract_metadata2 fields changed- added
Input schema / properties / fieldsAdded value: +{ + "description": "Comma-separated fields to return (e.g. \"title,body,summary\"). Include \"body\" for clean extracted page text.", + "type": "string" +} - added
Input schema / properties / summary_lengthAdded value: +{ + "description": "Max summary length in characters (default 300, max 2000)", + "type": "number" +}
- Changed
extract_metadata2 fields changed- added
Input schema / properties / fieldsAdded value: +{ + "description": "Comma-separated fields to return (e.g. \"title,body,summary\"). Include \"body\" for clean extracted page text. Available: url,title,description,image,favicon,siteName,type,locale,language,author,publishedDate,modifiedDate,keywords,themeColor,canonical,wordCount,summary,body,twitter,openGraph,jsonLd,responseTime", + "type": "string" +} - added
Input schema / properties / summary_lengthAdded value: +{ + "description": "Max summary length in characters (default 300, max 2000)", + "type": "number" +}
2 tool updates
- First observed
batch_extract_metadata - First observed
extract_metadata
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Zero-signup anonymous link-unfurl API. One GET returns clean JSON metadata for any public URL.
Pay-per-call Open Graph/link preview metadata for AI agents. $0.01 USDC per call, no signup.
Free Open Graph image generator API. Create beautiful OG images with customizable themes, icons, and colors. No API keys required.
Free screenshot and webpage capture API. Capture full-page screenshots, specific elements, or PDF snapshots of any URL. No API keys required.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceProvides URL metadata extraction (title, description, image, site name) from OpenGraph and meta tags for link previews.-
OpenSERP Cloudofficial
AlicenseBqualityCmaintenanceSearch API for AI, SEO & automation. Browser-rendered Google, Bing, Yandex, Baidu, DuckDuckGo and Ecosia results with URL extraction (+image search and engine metadata tools)9602MIT- AlicenseNot gradedqualityCmaintenanceEnables interaction with the Microlink API for link previews and data extraction, requiring no authentication. It is part of the Pipeworx MCP gateway, providing access to over 673 live data sources.4MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation4/5
The three tools have distinct primary purposes: batch_extract_metadata handles multiple URLs, extract_metadata handles single URL extraction, and validate_metadata focuses on validation/scoring. However, extract_metadata and batch_extract_metadata overlap significantly in functionality (both extract metadata), which could cause minor confusion about when to use each.
Naming Consistency5/5
All tool names follow a consistent snake_case pattern with clear verb_noun structure (batch_extract_metadata, extract_metadata, validate_metadata). The naming is predictable and readable throughout the set.
Tool Count4/5
Three tools is a reasonable count for a metadata-focused server, covering extraction (single and batch) and validation. It feels slightly thin but adequate for the domain, as core operations are present without being overwhelming.
Completeness4/5
The tool set covers key metadata operations: extraction (single and batch) and validation. A minor gap exists in lacking explicit update or management tools for metadata, but this is reasonable for a read-only metadata service, and agents can work with the provided tools effectively.