Web Metadata, OpenGraph & Contact Extractor vs Scrivener MCP
A side-by-side look at the Web Metadata, OpenGraph & Contact Extractor and Scrivener 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 Scrivener MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Web Metadata, OpenGraph & Contact Extractor when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
Choose Scrivener MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Knowledge & Memory |
| Quality signal | 40/100 · Fair | 61/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 | 67 |
| Directory activity | 0 views 0 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Web Metadata, OpenGraph & Contact Extractor | View Scrivener MCP |
Tools & capabilities
Web Metadata, OpenGraph & Contact Extractor tools
No tool names declared yet. Check the project README from the listing page.
Scrivener 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
{
"mcpServers": {
"web-metadata-opengraph-contact-extractor": {
"url": "https://mcp.rapidapi.com"
}
}
}
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}
Frequently asked questions
Web Metadata, OpenGraph & Contact Extractor is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Web Metadata, OpenGraph & Contact Extractor for search & data extraction work and Scrivener MCP for knowledge & memory.
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. Scrivener 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.
Yes. MCP clients support multiple servers: add web-metadata-opengraph-contact-extractor and writerslogic-scrivener-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. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.