Search1API vs Web Metadata, OpenGraph & Contact Extractor
A side-by-side look at the Search1API 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 Search1API 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 Search1API when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SEARCH1API_KEY. - You want tools like
search, news, crawl.
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 | 67/100 · Great | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SEARCH1API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 173 | 10 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View Search1API | View Web Metadata, OpenGraph & Contact Extractor |
Tools & capabilities
Search1API tools 7
searchSearch the live public web when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text. Each result includes a URL that can be read in full.newsSearch current news when the user asks about recent events, announcements, or coverage. Returns citable article results with title, URL, snippet, and optional extracted text.crawlExtract the readable title and full text from a public URL supplied by the user or returned by search.sitemapDiscover related public links from a page or domain when the user wants to explore a site's structure or available pages.trendingList currently trending repositories or stories from GitHub or Hacker News when the user asks what is popular now.askDescribe what you are looking for in natural language when you do not know which source to search. Search1API picks up to five engines (web, Hacker News, Reddit, GitHub, X, arXiv, Wikipedia, and more), infers a time window from phrases such as "this week", and returns at most 10 relevant results ranked by relevance. Costs 5 credits; use search when you already know the engine.render_resultsPresent already retrieved source results as source cards when the host supports UI, with a complete readable text list otherwise. Use when the user wants to browse sources or a visual list helps the task. Pass existing results in the desired order; never invent source URLs or factual titles. Does not search, crawl, fetch URLs, verify sources, or consume search credits. Do not call for intermediate research results or when a text answer is sufficient.
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.
Search1API
{
"mcpServers": {
"search1api": {
"command": "npx",
"args": [
"-y",
"search1api-mcp"
],
"env": {
"SEARCH1API_KEY": "YOUR_SEARCH1API_KEY_HERE"
}
}
}
}
Web Metadata, OpenGraph & Contact Extractor
{
"mcpServers": {
"web-metadata-opengraph-contact-extractor": {
"url": "https://mcp.rapidapi.com"
}
}
}
Frequently asked questions
Search1API 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 Search1API 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.
Search1API has no declared pricing — check the project's own site. 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 search1api 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, Search1API has a quality signal of 67/100 (Great) with 1 views, 0 installs and 173 GitHub stars. Web Metadata, OpenGraph & Contact Extractor has 40/100 (Fair) with 0 views, 0 installs and 10 GitHub stars.