Opengraph IO MCP vs Web Metadata, OpenGraph & Contact Extractor
A side-by-side look at the Opengraph IO MCP and Web Metadata, OpenGraph & Contact Extractor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Opengraph IO MCP for search & data extraction work as a local process; choose Web Metadata, OpenGraph & Contact Extractor for search & data extraction over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Opengraph IO MCP when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
Choose Web Metadata, OpenGraph & Contact Extractor when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 52/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 10 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Opengraph IO MCP | View Web Metadata, OpenGraph & Contact Extractor |
Tools & capabilities
Opengraph IO MCP tools
No tool names declared yet. Check the project README from the listing page.
Web Metadata, OpenGraph & Contact Extractor 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.
Opengraph IO MCP
{
"mcpServers": {
"securecoders-opengraph-io-mcp": {
"command": "npx",
"args": [
"-y",
"opengraph-io-mcp-install"
]
}
}
}
Web Metadata, OpenGraph & Contact Extractor
{
"mcpServers": {
"web-metadata-opengraph-contact-extractor": {
"url": "https://mcp.rapidapi.com"
}
}
}
Frequently asked questions
Opengraph IO MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. Web Metadata, OpenGraph & Contact Extractor belongs to Search & Data Extraction and uses a remote HTTP/SSE transport. Pick Opengraph IO MCP for search & data extraction work and Web Metadata, OpenGraph & Contact Extractor 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.
Opengraph IO MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. Web Metadata, OpenGraph & Contact Extractor has no declared pricing — check the project's own site. 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 securecoders-opengraph-io-mcp and web-metadata-opengraph-contact-extractor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Opengraph IO MCP has a quality signal of 52/100 (Good) with 2 views, 0 installs and 2 GitHub stars. Web Metadata, OpenGraph & Contact Extractor has 40/100 (Fair) with 0 views, 0 installs and 10 GitHub stars.