What is the main functional difference between Web Metadata, OpenGraph & Contact Extractor and Fetcher MCP?

Web Metadata, OpenGraph & Contact Extractor is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Fetcher MCP belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Web Metadata, OpenGraph & Contact Extractor for search & data extraction work and Fetcher MCP for search & data extraction.

How do I install Web Metadata, OpenGraph & Contact Extractor or Fetcher MCP in Claude Desktop, Cursor, or Windsurf?

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Are Web Metadata, OpenGraph & Contact Extractor and Fetcher MCP free to use, or do they require API keys?

Web Metadata, OpenGraph & Contact Extractor has no declared pricing — check the project's own site. Fetcher MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Can I run both Web Metadata, OpenGraph & Contact Extractor and Fetcher MCP at the same time in my AI client?

Yes. MCP clients support multiple servers: add web-metadata-opengraph-contact-extractor and jae-jae-fetcher-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Web Metadata, OpenGraph & Contact Extractor has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 10 GitHub stars. Fetcher MCP has 60/100 (Good) with 6 views, 0 installs and 1,088 GitHub stars.

Web Metadata, OpenGraph & Contact Extractor vs Fetcher MCP

A side-by-side look at the Web Metadata, OpenGraph & Contact Extractor and Fetcher MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Web Metadata, OpenGraph & Contact ExtractorSearch & Data Extraction · Remote HTTP/SSETurns any URL into SEO metadata, contacts, tech stack, and AI-ready Markdown, in one call.40FairAuth: not declared

Fetcher MCPSearch & Data Extraction · Local subprocess (stdio)MCP server for fetching web page content using Playwright headless browser, supporting Javascript rendering and intelligent content extraction, and outputting Markdown or HTML format.60GoodAuth: no auth required

Verdict: choose Web Metadata, OpenGraph & Contact Extractor for search & data extraction work over a hosted endpoint; choose Fetcher MCP for search & data extraction as a local process. You can also run both side by side in one mcpServers block.

Spec	Web Metadata, OpenGraph & Contact Extractor	Fetcher MCP
Category	Search & Data Extraction	Search & Data Extraction
Quality signal	40/100 · Fair	60/100 · Good
Install command	Confirmed	Confirmed
Transport	Remote HTTP/SSE	Local subprocess (stdio)
Auth	Not declared	No auth required
Pricing	Not declared	Free
Required env vars	None listed	None listed
Verified owner	Community listing	Community listing
GitHub stars	10	1,088
Directory activity	0 views 0 installs 0 upvotes	6 views 0 installs 0 upvotes
Tools	Not listed	Not listed
Full listing	View Web Metadata, OpenGraph & Contact Extractor	View Fetcher MCP

Web Metadata, OpenGraph & Contact Extractor vs Fetcher MCP

Which MCP server should you choose?

Choose Web Metadata, OpenGraph & Contact Extractor when

Choose Fetcher MCP when

Feature & specification comparison

Tools & capabilities

Web Metadata, OpenGraph & Contact Extractor tools

Fetcher MCP tools

Ready-to-paste client configs