A
licenseA
qualityB
maintenanceWeb extraction MCP server for AI agents. Extract structured data from any URL with built-in Cloudflare bypass, JavaScript rendering, and intelligent parsing. Returns clean markdown or JSON.
5
794 npm
2
MIT
Opengraph io MCP
by securecoders
Related Servers
Alternatives to Opengraph io MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for ScreenshotFreeAPI – capture website screenshots, render HTML/PDF, and fetch app store listing screenshots from any MCP-compatible AI client.77 npmMIT
- AlicenseBqualityCmaintenanceMCP server for the Spider web crawling and scraping API, enabling AI agents to crawl, scrape, search, and extract web data.1311 npm2MIT
- FlicenseAqualityDmaintenanceMCP server for Cloudflare Browser Rendering Crawl API. Fetches and crawls web pages, returning clean Markdown optimized for LLM consumption.3-
- AlicenseAqualityDmaintenanceMCP server that exposes Scrapingdog APIs for web scraping, search engine queries, social media profiles/posts, screenshots, and datacenter proxy usage via nine tools.99 npm1MIT
- AlicenseAqualityDmaintenanceA powerful MCP server for fetching and transforming web content into various formats (HTML, JSON, Markdown, Plain Text) with ease.411,842 npm42MIT
TDQS
A4.2/5.0
Scored across 10 tools
Disambiguation4/5
The six getOg* tools have overlapping web-scraping purposes, but each description includes an explicit 'Pick the right tool' guide that clarifies when to use which. The four image tools (generateImage, iterateImage, inspectImageSession, exportImageAsset) are clearly distinct. Minor confusion possible between getOgScrapeData and getOgExtract, but overall boundaries are well documented.
Naming Consistency4/5
All tool names use camelCase and are readable. There are two sub-conventions: verb_noun for image tools (generateImage, exportImageAsset, inspectImageSession, iterateImage) and a getOg* prefix for web tools (getOgData, getOgMarkdown, etc.). The split is minor and consistent within each functional group.
Tool Count5/5
At 10 tools, the set is well-scoped: four cover the image lifecycle (generate, iterate, inspect, export) and six cover distinct web-content extraction modes. Every tool appears to earn its place without excessive granularity.
Completeness4/5
The surface covers the core image workflow (generation, iteration, session inspection, export) and a comprehensive set of URL extraction modes (metadata, markdown, raw HTML, targeted extraction, screenshot, natural-language query). Minor gaps exist—e.g., no list/delete session or asset cleanup operations—but the main lifecycle is complete.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive