ChatGPT MCP
Envoyez un prompt à ChatGPT de manière anonyme et lisez la réponse au format Markdown, accompagnée de toutes les sources Web consultées, sous forme de JSON structuré. Aucun compte ni clé OpenAI requis. Hébergé par HasData : HTTP en streaming, OAuth ou clé API, sans installation.
Serveur MCP hébergé
npx add-mcp 'https://mcp.hasdata.com/mcp?apis=chatgpt'S’installe dans Claude Code, Codex, Cursor et plus
Documentation

See the answer and the sources behind it
Compare uptime tools for a small team or find public markets near downtown Seattle. Each example includes the agent’s reply and an abridged tool result.
ChatGPT · 1 tool Enter to send
Ask ChatGPT which uptime tools it recommends for a small team, and list the brands.
hasdata_chatgpt_chat_getChatgptAnswer · 200 OK sample call Answer JSON
I’d start with UptimeRobot for downtime alerts, Better Stack if the team shares on-call duty, or Uptime Kuma if you want to host it yourself.
UptimeRobot checks websites and alerts you when one goes down. Better Stack also gives the team a status page, on-call scheduling and incident management.
Uptime Kuma is open source and can send notifications to Slack or Discord. You maintain the server it runs on.
For API checks and browser tests, look at Checkly. StatusCake adds SSL and domain-expiration monitoring.
Site24x7 also covers infrastructure. Pingdom combines uptime checks with website performance monitoring.
Sources
UptimeRobot · https://uptimerobot.com/
Better Stack · https://betterstack.com/
Checkly · https://www.checklyhq.com/
hasdata_chatgpt_chat_getChatgptAnswer {"prompt":"Which tools can a small team use to monitor website uptime? Include sources."}
{
"status": 200,
"json": {
"conversation": {
"answer": "Small teams have several good options for monitoring website uptime, ranging from free tools that send downtime alerts to more advanced platforms with incident management, team notifications, and public status pages.\n\nFor a small team, I'd prioritize **ease of setup, affordable pricing, Slack/Teams integration, multiple monitoring locations, and reliable alerts.**\n\n## 7 website uptime monitoring tools worth considering\n\n### 1. UptimeRobot\nUptimeRobot official website\n\n**Best for: Small teams looking for simple, affordable monitoring.**\n\n- Free plan includes 50 monitors.\n- Checks websites every 5 minutes on the free plan.\n- Supports HTTP, ping, port, and keyword monitoring.\n- Sends downtime notifications.\n- Paid plans offer faster monitoring intervals and team collaboration features.\n\n**Why choose it:** A straightforward starting point if your primary goal is knowing when your website becomes unavailable.\n\nSource:\n\n### 2. Better Stack\nBetter Stack official website\n\n**Best for: Teams that need uptime monitoring and incident management.**\n\n- Free plan includes 10 monitors and heartbeats.\n- Includes a status page.\n- Supports Slack and email notifications.\n- Offers incident management and on-call scheduling.\n- Supports logs, metrics, and broader observability.\n\n**Why choose it:** Particularly useful when several team members need to know about outages and coordinate responses.\n\nSource:\n\n### 3. StatusCake\nStatusCake official website\n\n**Best for: Small businesses monitoring multiple websites.**\n\n- Free plan available.\n- Paid Superior plan supports up to two team members.\n- Includes 100 uptime monitors on the Superior plan.\n- Offers one-minute monitoring intervals on paid plans.\n- Supports SSL, domain expiration, and page-speed monitoring.\n\n**Why choose it:** A good option if you want uptime monitoring alongside SSL and website performance checks.\n\nSource:\n\n### 4. Site24x7\nSite24x7 official website\n\n**Best for: Teams monitoring websites and infrastructure together.**\n\n- Free plan available.\n- Paid website monitoring starts at approximately $9/month with annual billing.\n- Supports multiple monitoring locations.\n- Provides transaction monitoring.\n- Includes status pages and integrations.\n\n**Why choose it:** Useful if your team wants to monitor website availability, server infrastructure, and application performance from one platform.\n\nSource:\n\n### 5. Uptime Kuma\nUptime Kuma GitHub repository\n\n**Best for: Teams that prefer free, self-hosted solutions.**\n\n- Free and open-source.\n- Supports HTTP, HTTPS, TCP, DNS, and ping monitoring.\n- Supports monitoring intervals as short as 20 seconds.\n- Integrates with Slack, Discord, Telegram, and email.\n- Provides customizable status pages.\n\n**Why choose it:** Excellent if your team has someone comfortable managing a server and wants to avoid recurring subscription costs.\n\nSource:\n\n### 6. Checkly\nCheckly official website\n\n**Best for: Development teams and technical monitoring.**\n\n- Supports uptime monitoring.\n- Offers API monitoring.\n- Supports browser-based synthetic monitoring.\n- Integrates with developer workflows.\n- Useful for monitoring critical user journeys, not just whether a website responds.\n\n**Why choose it:** Particularly useful if your team wants to verify that important website functionality works, rather than simply checking whether the homepage loads.\n\n### 7. Pingdom\nPingdom official website\n\n**Best for: Website availability and performance monitoring.**\n\n- Website uptime monitoring.\n- Real-user performance monitoring.\n- Synthetic transaction monitoring.\n- Alerts when availability or performance deteriorates.\n- Historical performance reporting.\n\n**Why choose it:** A good option if website performance is just as important as uptime.\n\n---\n\n## Quick comparison\n\n| Tool | Free plan | Team collaboration | Best use case |\n|---|---|---|---|\n| UptimeRobot | Yes | Paid plans | Basic uptime monitoring |\n| Better Stack | Yes | Yes | Monitoring and incident response |\n| StatusCake | Yes | Paid plans | Multiple websites |\n| Site24x7 | Yes | Yes | Website and infrastructure |\n| Uptime Kuma | Yes | Self-managed | Open-source monitoring |\n| Checkly | Yes | Developer-oriented | API and browser monitoring |\n| Pingdom | Free trial | Yes | Uptime and performance |\n\n*Free-plan limits and paid features can change. Check the linked pricing pages before subscribing.*\n\n## My recommendations for a small team\n\nI'd narrow the selection down to these three:\n\n| Requirement | Recommended tool |\n|---|---|\n| Simple, affordable uptime monitoring | UptimeRobot |\n| Team notifications and incident management | Better Stack |\n| Free, self-hosted monitoring | Uptime Kuma |\n\n**My first choice would be Better Stack** if multiple people need to receive alerts and coordinate responses.\n\nIf you only need to know when a website goes down, **UptimeRobot** is probably the simplest starting point.\n\n## What should a small team monitor?\n\nRegardless of which tool you select, I'd recommend monitoring:\n\n1. **Website availability:** Is the website accessible?\n2. **HTTP response codes:** Is the server returning errors such as 500 or 503?\n3. **Response time:** Is the website becoming unusually slow?\n4. **SSL certificate expiration:** Is the HTTPS certificate valid?\n5. **API availability:** Are critical backend services responding?\n6. **Domain expiration:** Is the domain registration approaching its expiration date?\n\n### One additional recommendation\n\nConfigure notifications to reach at least two team members through Slack, Microsoft Teams, or email.\n\nAlso, use monitoring from multiple geographic locations where possible. This helps distinguish a genuine website outage from a regional connectivity issue.\n\n**The goal is to make sure that someone on the team knows about an outage quickly, even when nobody is actively checking the website.**",
"title": "Uptime Monitoring Tools Sources",
"model": "gpt-6",
"usedWebSearch": true,
"complete": true,
"sources": [
{
"title": "UptimeRobot official website",
"url": "https://uptimerobot.com/",
"domain": "uptimerobot.com"
},
{
"title": "Better Stack official website",
"url": "https://betterstack.com/",
"domain": "betterstack.com"
},
{
"title": "StatusCake - Uptime monitoring, Page speed monitoring, and more",
"url": "https://www.statuscake.com/",
"domain": "www.statuscake.com"
},
{
"title": "Checkly official website",
"url": "https://www.checklyhq.com/",
"domain": "www.checklyhq.com"
}
]
}
}
}
Ask ChatGPT which uptime tools it recommends for a small team, and list the brands.
hasdata_chatgpt_chat_getChatgptAnswer · 200 OK sample call
I’d start with UptimeRobot for downtime alerts, Better Stack if the team shares on-call duty, or Uptime Kuma if you want to host it yourself.
UptimeRobot checks websites and alerts you when one goes down. Better Stack also gives the team a status page, on-call scheduling and incident management.
Uptime Kuma is open source and can send notifications to Slack or Discord. You maintain the server it runs on.
For API checks and browser tests, look at Checkly. StatusCake adds SSL and domain-expiration monitoring.
Site24x7 also covers infrastructure. Pingdom combines uptime checks with website performance monitoring.
Sources
UptimeRobot · https://uptimerobot.com/
Better Stack · https://betterstack.com/
Checkly · https://www.checklyhq.com/
hasdata_chatgpt_chat_getChatgptAnswer {"prompt":"Which tools can a small team use to monitor website uptime? Include sources."}
{
"status": 200,
"json": {
"conversation": {
"answer": "Small teams have several good options for monitoring website uptime, ranging from free tools that send downtime alerts to more advanced platforms with incident management, team notifications, and public status pages.\n\nFor a small team, I'd prioritize **ease of setup, affordable pricing, Slack/Teams integration, multiple monitoring locations, and reliable alerts.**\n\n## 7 website uptime monitoring tools worth considering\n\n### 1. UptimeRobot\nUptimeRobot official website\n\n**Best for: Small teams looking for simple, affordable monitoring.**\n\n- Free plan includes 50 monitors.\n- Checks websites every 5 minutes on the free plan.\n- Supports HTTP, ping, port, and keyword monitoring.\n- Sends downtime notifications.\n- Paid plans offer faster monitoring intervals and team collaboration features.\n\n**Why choose it:** A straightforward starting point if your primary goal is knowing when your website becomes unavailable.\n\nSource:\n\n### 2. Better Stack\nBetter Stack official website\n\n**Best for: Teams that need uptime monitoring and incident management.**\n\n- Free plan includes 10 monitors and heartbeats.\n- Includes a status page.\n- Supports Slack and email notifications.\n- Offers incident management and on-call scheduling.\n- Supports logs, metrics, and broader observability.\n\n**Why choose it:** Particularly useful when several team members need to know about outages and coordinate responses.\n\nSource:\n\n### 3. StatusCake\nStatusCake official website\n\n**Best for: Small businesses monitoring multiple websites.**\n\n- Free plan available.\n- Paid Superior plan supports up to two team members.\n- Includes 100 uptime monitors on the Superior plan.\n- Offers one-minute monitoring intervals on paid plans.\n- Supports SSL, domain expiration, and page-speed monitoring.\n\n**Why choose it:** A good option if you want uptime monitoring alongside SSL and website performance checks.\n\nSource:\n\n### 4. Site24x7\nSite24x7 official website\n\n**Best for: Teams monitoring websites and infrastructure together.**\n\n- Free plan available.\n- Paid website monitoring starts at approximately $9/month with annual billing.\n- Supports multiple monitoring locations.\n- Provides transaction monitoring.\n- Includes status pages and integrations.\n\n**Why choose it:** Useful if your team wants to monitor website availability, server infrastructure, and application performance from one platform.\n\nSource:\n\n### 5. Uptime Kuma\nUptime Kuma GitHub repository\n\n**Best for: Teams that prefer free, self-hosted solutions.**\n\n- Free and open-source.\n- Supports HTTP, HTTPS, TCP, DNS, and ping monitoring.\n- Supports monitoring intervals as short as 20 seconds.\n- Integrates with Slack, Discord, Telegram, and email.\n- Provides customizable status pages.\n\n**Why choose it:** Excellent if your team has someone comfortable managing a server and wants to avoid recurring subscription costs.\n\nSource:\n\n### 6. Checkly\nCheckly official website\n\n**Best for: Development teams and technical monitoring.**\n\n- Supports uptime monitoring.\n- Offers API monitoring.\n- Supports browser-based synthetic monitoring.\n- Integrates with developer workflows.\n- Useful for monitoring critical user journeys, not just whether a website responds.\n\n**Why choose it:** Particularly useful if your team wants to verify that important website functionality works, rather than simply checking whether the homepage loads.\n\n### 7. Pingdom\nPingdom official website\n\n**Best for: Website availability and performance monitoring.**\n\n- Website uptime monitoring.\n- Real-user performance monitoring.\n- Synthetic transaction monitoring.\n- Alerts when availability or performance deteriorates.\n- Historical performance reporting.\n\n**Why choose it:** A good option if website performance is just as important as uptime.\n\n---\n\n## Quick comparison\n\n| Tool | Free plan | Team collaboration | Best use case |\n|---|---|---|---|\n| UptimeRobot | Yes | Paid plans | Basic uptime monitoring |\n| Better Stack | Yes | Yes | Monitoring and incident response |\n| StatusCake | Yes | Paid plans | Multiple websites |\n| Site24x7 | Yes | Yes | Website and infrastructure |\n| Uptime Kuma | Yes | Self-managed | Open-source monitoring |\n| Checkly | Yes | Developer-oriented | API and browser monitoring |\n| Pingdom | Free trial | Yes | Uptime and performance |\n\n*Free-plan limits and paid features can change. Check the linked pricing pages before subscribing.*\n\n## My recommendations for a small team\n\nI'd narrow the selection down to these three:\n\n| Requirement | Recommended tool |\n|---|---|\n| Simple, affordable uptime monitoring | UptimeRobot |\n| Team notifications and incident management | Better Stack |\n| Free, self-hosted monitoring | Uptime Kuma |\n\n**My first choice would be Better Stack** if multiple people need to receive alerts and coordinate responses.\n\nIf you only need to know when a website goes down, **UptimeRobot** is probably the simplest starting point.\n\n## What should a small team monitor?\n\nRegardless of which tool you select, I'd recommend monitoring:\n\n1. **Website availability:** Is the website accessible?\n2. **HTTP response codes:** Is the server returning errors such as 500 or 503?\n3. **Response time:** Is the website becoming unusually slow?\n4. **SSL certificate expiration:** Is the HTTPS certificate valid?\n5. **API availability:** Are critical backend services responding?\n6. **Domain expiration:** Is the domain registration approaching its expiration date?\n\n### One additional recommendation\n\nConfigure notifications to reach at least two team members through Slack, Microsoft Teams, or email.\n\nAlso, use monitoring from multiple geographic locations where possible. This helps distinguish a genuine website outage from a regional connectivity issue.\n\n**The goal is to make sure that someone on the team knows about an outage quickly, even when nobody is actively checking the website.**",
"title": "Uptime Monitoring Tools Sources",
"model": "gpt-6",
"usedWebSearch": true,
"complete": true,
"sources": [
{
"title": "UptimeRobot official website",
"url": "https://uptimerobot.com/",
"domain": "uptimerobot.com"
},
{
"title": "Better Stack official website",
"url": "https://betterstack.com/",
"domain": "betterstack.com"
},
{
"title": "StatusCake - Uptime monitoring, Page speed monitoring, and more",
"url": "https://www.statuscake.com/",
"domain": "www.statuscake.com"
},
{
"title": "Checkly official website",
"url": "https://www.checklyhq.com/",
"domain": "www.checklyhq.com"
}
]
}
}
}
Ask ChatGPT for two public markets near downtown Seattle and their websites.
hasdata_chatgpt_chat_getChatgptAnswer · 200 OK sample call
Two public markets near downtown Seattle are Pike Place Market and Capitol Hill Farmers Market.
Pike Place Market
85 Pike Street, downtown. You’ll find seafood, produce and crafts from independent sellers.
https://www.pikeplacemarket.org/
Capitol Hill Farmers Market
E Barbara Bailey Way, Capitol Hill. It’s a year-round neighborhood market for local produce, flowers and artisan foods.
https://seattlefarmersmarkets.org/
hasdata_chatgpt_chat_getChatgptAnswer {"prompt":"Which two public markets are near me? Give their names, neighborhoods and official websites.","lat":47.6062,"lon":-122.3321}
{
"status": 200,
"json": {
"conversation": {
"answer": "Based on your location in **Downtown Seattle**, these are two nearby public markets:\n\n### 1. Pike Place Market\n- **Neighborhood:** Downtown / Pike Place\n- **Address:** 85 Pike Street, Seattle\n- **Distance:** Approximately 800 metres\n- **Official website:** Pike Place Market\n\nA historic public market featuring fresh produce, seafood, flowers, local crafts and independent shops.\n\n### 2. Capitol Hill Farmers Market\n- **Neighborhood:** Capitol Hill\n- **Address:** E Barbara Bailey Way, Seattle\n- **Distance:** Approximately 1.7 km\n- **Official website:** Neighborhood Farmers Markets Alliance\n\nA year-round neighborhood farmers market offering locally grown produce, artisan foods, flowers and handmade products.\n\n**My recommendation:** Pike Place Market is the closest iconic public-market experience, while Capitol Hill Farmers Market offers a more neighborhood-oriented farmers-market experience.",
"title": "Find Public Markets Nearby",
"model": "gpt-6",
"usedWebSearch": true,
"complete": true,
"location": {
"lat": 47.6062,
"lon": -122.3321
},
"sources": [
{
"title": "Pike Place Market",
"url": "https://www.pikeplacemarket.org/",
"domain": "www.pikeplacemarket.org"
},
{
"title": "Neighborhood Farmers Markets Alliance",
"url": "https://seattlefarmersmarkets.org/",
"domain": "seattlefarmersmarkets.org"
}
]
}
}
}
What the ChatGPT scraper returns
1 tool
Send a question in prompt. For local recommendations, pass lat and lon together. The conversation object contains the answer in Markdown and lists sources when ChatGPT uses web search.
+ hasdata_chatgpt_chat_getChatgptAnswer Capture an anonymous ChatGPT answer and its available web sources 3 params 10 credits Try
| Parameter | Type | Required | Example |
|---|---|---|---|
| prompt | string | required | "Which tools can a small team use to monitor website uptime? Include sources." |
| lat | number | optional | 47.6062 |
| lon | number | optional | -122.3321 |
response
- conversation.answer
- conversation.sources
- conversation.sources[].url
- conversation.sources[].domain
- conversation.title
- conversation.model
- conversation.usedWebSearch
- conversation.complete
- conversation.location
Base calls cost 10 credits. Failed calls are not billed.
Connect Claude, Cursor or your MCP client
Use the hosted URL with a HasData API key, or sign in through OAuth where your client supports it. No OpenAI API key or ChatGPT login is required.
Claude Code
zsh — hasdata-chatgpt
$claude mcp add --transport http hasdata-chatgpt \
> "https://mcp.hasdata.com/mcp?apis=chatgpt" \
· One line, no restart. Run /mcp to confirm 1 tool.
Check the connectionIn the session
/mcp
hasdata-chatgpt · connected · 1 tool
Cursor
~/.cursor/mcp.json
{
"mcpServers": { "hasdata-chatgpt": {
"url": "https://mcp.hasdata.com/mcp?apis=chatgpt",
"headers": { "x-api-key": "YOUR_API_KEY" }
} }
}
· Add this entry to ~/.cursor/mcp.json. Servers already in the file stay as they are.
· Project-level config also works at.cursor/mcp.json
Check the connectionAfter saving the file
Settings → MCP
hasdata-chatgpt · 1 tool enabled
Claude Desktop
*1.*Settings → Connectors → Add custom connector
*2.*Paste https://mcp.hasdata.com/mcp?apis=chatgpt
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": { "hasdata-chatgpt": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.hasdata.com/mcp?apis=chatgpt",
"--header", "x-api-key:YOUR_API_KEY"]
} }
}
· Add this entry to ~/Library/Application Support/Claude/claude_desktop_config.json. Servers already in the file stay as they are.
· The config file only takes stdio servers, so a static key rides the mcp-remote bridge. On Windows the file lives at %APPDATA%\Claude\claude_desktop_config.json.
Check the connectionReopen the app
Settings → Connectors
hasdata-chatgpt · connected · 1 tool
VS Code / Copilot
.vscode/mcp.json
{
"servers": { "hasdata-chatgpt": {
"type": "http",
"url": "https://mcp.hasdata.com/mcp?apis=chatgpt",
"headers": { "x-api-key": "YOUR_API_KEY" }
} }
}
· Add this entry to.vscode/mcp.json. Servers already in the file stay as they are.
· Agent mode picks the server up on save.
Check the connectionAgent mode
Ctrl/⌘ + Shift + P → MCP: List Servers
hasdata-chatgpt · running · 1 tool
Windsurf
~/.codeium/windsurf/mcp_config.json
{
"mcpServers": { "hasdata-chatgpt": {
"serverUrl": "https://mcp.hasdata.com/mcp?apis=chatgpt",
"headers": { "x-api-key": "YOUR_API_KEY" }
} }
}
· Add this entry to ~/.codeium/windsurf/mcp_config.json. Servers already in the file stay as they are.
Check the connectionIn Cascade
Cascade → MCP servers
hasdata-chatgpt · 1 tool
Cline
cline_mcp_settings.json
{
"mcpServers": { "hasdata-chatgpt": {
"type": "streamableHttp",
"url": "https://mcp.hasdata.com/mcp?apis=chatgpt",
"headers": { "x-api-key": "YOUR_API_KEY" }
} }
}
· Add this entry to cline_mcp_settings.json. Servers already in the file stay as they are.
· Header auth only. The type field tells Cline this is a remote server, not a command.
Check the connectionIn the MCP panel
MCP Servers → Installed
hasdata-chatgpt · 1 tool
Codex CLI
~/.codex/config.toml
[mcp_servers.hasdata-chatgpt]
url = "https://mcp.hasdata.com/mcp?apis=chatgpt"
env_http_headers = { "x-api-key" = "HASDATA_API_KEY" }
· Add this entry to ~/.codex/config.toml. Servers already in the file stay as they are.
· TOML, not JSON. Export HASDATA_API_KEY in the shell that starts Codex, then open a new session and use /mcp to inspect its tools.
Check the configurationConfigured servers
codex mcp list
Confirm hasdata-chatgpt, its URL and enabled status.
Gemini CLI
~/.gemini/settings.json
{
"mcpServers": { "hasdata-chatgpt": {
"httpUrl": "https://mcp.hasdata.com/mcp?apis=chatgpt",
"headers": { "x-api-key": "YOUR_API_KEY" }
} }
}
· Add this entry to ~/.gemini/settings.json. Servers already in the file stay as they are.
· httpUrl, not url: Gemini keeps url for SSE servers. Header auth only.
Check the connectionIn the session
/mcp
hasdata-chatgpt · 1 tool
Raw HTTP / curl
zsh — hasdata-chatgpt
$curl -N "https://mcp.hasdata.com/mcp?apis=chatgpt" \
> -H "x-api-key: YOUR_API_KEY" \
> -H "Content-Type: application/json" \
> -H "Accept: application/json, text/event-stream" \
> -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
· Fallback for any client not listed. Streamable HTTP wants both Accept types, and leaving one out returns 406.
Check the connectionCall it yourself
curl … tools/list
{ "tools": [ … 1 item ] }
Compare ChatGPT answers with search results
Add Google Search to inspect the pages alongside a ChatGPT answer. Your client receives only the tools for the selected services, using the same HasData account.
ChatGPT 1 tool Google SERP 8 tools Google Maps 6 tools Amazon 4 tools TikTok 4 tools YouTube 5 tools Yelp 3 tools Airbnb 2 tools Booking.com 2 tools Glassdoor 2 tools Indeed 2 tools Instagram 4 tools Redfin 2 tools Shopify 2 tools Yellow Pages 2 tools Zillow 2 tools Bing 1 tool DuckDuckGo 1 tool Google Flights 1 tool Google Hotels 1 tool Google Images 1 tool Google Trends 1 tool Web Scraping 1 tool Facebook 1 tool Gemini 1 tool Google Finance 1 tool Google Flights Deals 1 tool Google Scholar 3 tools Tripadvisor 3 tools Walmart 3 tools See the full MCP server →
https://mcp.hasdata.com/mcp?apis=chatgpt,google\_serp
9 active tools in your server
Free code, paid in hours
Getting an answer is only the start. Someone still has to keep sessions, response capture and parsing working. HasData handles that collection work for your ChatGPT research.
Self-hosted costs and hours are illustrative budgets for one custom scraper. Engineering time is separate from infrastructure spend.
Scenario A script I run onceA weekly reportA pipeline in productionA feature in my product
A script I run once
Your own scraper example budget
$0 runs locally
+ 3–6 h setup once
Adapt a script and run it 3–6 h once
Parser upkeep No recurring work
Request handling Basic retries
Proxy and hosting $0, local run
A one-off run on your machine. Keep full control over field selection.
mcp.hasdata.com Free tier
$0 / month
Included parser maintenance
Setup one line
Proxies and source-side retries Included
Concurrent requests 5
25 calls at 10 credits 250 of 1,000 credits
Free credits renew every month. No credit card.
leans self-hosted
Keep the free script
If a working scraper already gets the result, keep it. Use HasData when the job becomes recurring.
A weekly report
Your own scraper example budget
$0–40 / month
+ 2–4 h / mo upkeep
Setup 3–6 h once
Parser fixes 1–2 h / mo
Run checks and retries 1–2 h / mo
Proxy and hosting $0–40 / mo
A scheduled report with occasional parser fixes and checks when a run fails.
mcp.hasdata.com Free tier
$0 / month
Included parser maintenance
Setup one line
Proxies and source-side retries Included
Concurrent requests 5
100 calls at 10 credits 1,000 of 1,000 credits
Keep your report schedule and storage. HasData runs the scraper.
leans hosted
Skip the upkeep
A free script still needs an owner. Use HasData to collect the data without making parser fixes part of your reporting routine.
A pipeline in production
Your own scraper example budget
$40–120 / month
+ 6–10 h / mo upkeep
Setup 3–6 h once
Parser fixes 2–4 h / mo
Recovery and monitoring 4–6 h / mo
Proxy and hosting $40–120 / mo
Regular collection through proxies, with time budgeted for failed runs and source changes.
mcp.hasdata.com Startup, billed yearly
$49 / month
Included parser maintenance
Setup one line
Proxies and source-side retries Included
Concurrent requests 5
5,000 calls at 10 credits 50,000 of 200,000 credits
Hosted extraction, with headroom left in the plan for other calls.
leans hosted
Use the hosted server
A pipeline needs data every run. Use HasData instead of owning proxy setup, parser fixes and source-side retries.
A feature in my product
Your own scraper example budget
$300+ / month
+ On-call plus parser upkeep
Setup 3–6 h once
Parser fixes 2–4 h / mo
Extraction incidents Your team responds
Proxy and hosting $300+ / mo
A customer-facing feature with a larger proxy budget and extraction incidents to support.
mcp.hasdata.com Basic, billed yearly
$99 / month
Included parser maintenance
Setup one line
Proxies and source-side retries Included
Concurrent requests 15
50,000 calls at 10 credits 500,000 of 1,000,000 credits
Your app still owns field mapping and error handling. The scraper is on us.
leans hosted
Ship the feature
Put engineering time into the feature customers use. HasData maintains the extraction behind it.
Plans for your prompt workflow
Calls use your HasData account balance. Choose a plan for the request volume your workflow needs, and use the same credits across MCP and REST.
Free
$0 /mo
Free forever
100 tool calls / month
1,000 credits / month
5 concurrent requests
Every MCP tool on every plan
Failed calls are not billed
One balance across MCP and REST
Community support
Startup
$49 /mo
$2.46 / 1k tool calls
20K tool calls / month
200K credits / month
5 concurrent requests
Every MCP tool on every plan
Failed calls are not billed
One balance across MCP and REST
Email support
Basic
Recommended
$99 /mo
$0.99 / 1k tool calls
100K tool calls / month
1M credits / month
15 concurrent requests
Every MCP tool on every plan
Failed calls are not billed
One balance across MCP and REST
Priority email support
Growth
$208 /mo
$0.69 / 1k tool calls
3M credits / month
50 concurrent requests
Every MCP tool on every plan
Failed calls are not billed
One balance across MCP and REST
Dedicated account manager
Monthly tool call volume
Free 20K 100K 300K 500K 1M 2M
Best fit
Basic
tool calls / mo
100K
Concurrency
15
$ / 1k tool calls
$0.99
$99 /mo
Enterprise
Custom price based on required volume
Past 20M credits a month, or need terms the self-serve plans do not cover? We shape the contract, concurrency, and support around your workload.
Credits rollover
Unused credits carry into the next billing period.
Concurrency 2000+
Parallel request limits set to your peak load.
#1 request priority
Highest speed, always first in the queue.
Personal manager
A direct line to the founding team.
SSO
SAML single sign-on for the whole team.
Security review
Security questionnaire, DPA, and controls overview.
Talk to sales Quote within one business day
Use the same scraper through REST
Before you connect
Is this a server for adding tools to ChatGPT?
No. This server retrieves ChatGPT answers for an MCP client such as Claude or Cursor. To use HasData's web-data tools inside ChatGPT, choose the ChatGPT integration instead.
Is this the official OpenAI API?
No. HasData provides an independent ChatGPT scraper that sends an anonymous prompt and captures the answer. It is not a drop-in replacement for OpenAI's developer API, and it does not require your OpenAI API key or ChatGPT login.
Can I use it for brand mentions and AI visibility research?
Yes. Your agent can inspect the returned answer for brand mentions and recommendations, then group the available source URLs by domain. Save captures in your own workflow if you want comparisons over time. Scheduling, scores and alerts are not built into this tool.
Does every answer include sources or citations?
No. Check conversation.usedWebSearch and the available conversation.sources. These records describe pages ChatGPT consulted, not a guaranteed citation map for every sentence. The request has no separate switch to force web search.
Can I choose a model, continue a conversation or read my chat history?
Each call starts a fresh anonymous conversation. The tool does not expose model selection, private chat history or conversation continuation. The returned model label identifies the model that answered.
Can I choose the location and language for an answer?
Pass the location’s latitude and longitude together as lat and lon. The response echoes them in conversation.location. For the answer language, write your prompt in that language or ask for it explicitly.
Do I need to run a browser or local server?
No. Connect to the hosted Streamable HTTP endpoint using your HasData account. The client configurations above cover supported formats. Your agent sends tool arguments, and HasData handles the request and parsing.
What should my agent do if a request fails?
Check for a successful API status, a non-empty conversation.answer and conversation.complete before using a capture. Treat an error response as a failed request, not an empty answer. Failed requests consume no credits. Verify the sources before treating an answer as fact.
What happens when my credits run out?
Requests stop when your balance cannot cover the next call. HasData does not charge overages. Wait for the next billing cycle or renew your paid subscription early to restore credits.
Is HasData affiliated with OpenAI?
No. HasData is an independent service and is not affiliated with, endorsed by, or sponsored by OpenAI. ChatGPT is a trademark of its respective owner.