Web Metadata, OpenGra… vs Opengraph IO MCP | AllMCPs
Web Metadata, OpenGraph & Contact Extractor vs Opengraph IO MCP
A side-by-side look at the Web Metadata, OpenGraph & Contact Extractor and Opengraph IO MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Web Metadata, OpenGraph & Contact Extractor for search & data extraction work over a hosted endpoint; choose Opengraph IO MCP for search & data extraction as a local process. You can also run both side by side in one block.
mcpServers
Which MCP server should you choose?
Choose Web Metadata, OpenGraph & Contact Extractor when
You need dedicated capabilities in the Search & Data Extraction domain.
No tool names declared yet. Check the project README from the listing page.
Opengraph IO MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Web Metadata, OpenGraph & Contact Extractor is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Opengraph IO MCP belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Web Metadata, OpenGraph & Contact Extractor for search & data extraction work and Opengraph IO MCP for search & data extraction.
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.
Web Metadata, OpenGraph & Contact Extractor has no declared pricing — check the project's own site. Opengraph IO MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add web-metadata-opengraph-contact-extractor and securecoders-opengraph-io-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Web Metadata, OpenGraph & Contact Extractor has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 10 GitHub stars. Opengraph IO MCP has 52/100 (Good) with 2 views, 0 installs and 2 GitHub stars.
Related comparisons
Popular comparisons with Web Metadata, OpenGraph & Contact Extractor
