Brightdata MCP vs Nefesh — Real Time Human State Awareness
A side-by-side look at the Brightdata MCP and Nefesh — Real Time Human State Awareness MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Brightdata MCP for search & data extraction work as a local process; choose Nefesh — Real Time Human State Awareness for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Brightdata MCP when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
API_TOKEN. - You want tools like
search_engine, scrape_as_markdown, search_engine_batch.
Choose Nefesh — Real Time Human State Awareness when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
get_human_state, ingest, get_trigger_memory.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Developer Tools |
| Quality signal | 73/100 · Great | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | API_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,685 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 11 | 7 |
| Full listing | View Brightdata MCP | View Nefesh — Real Time Human State Awareness |
Tools & capabilities
Brightdata MCP tools 11
search_engineScrape search results from Google, Bing or Yandex. Returns SERP results in JSON or Markdown (URL, title, description),Ideal forgathering current information, news, and detailed search results.scrape_as_markdownScrape a single webpage URL with advanced options for content extraction and get back the results in MarkDown language. This tool can unlock any webpage even if it uses bot detection or CAPTCHA.search_engine_batchRun multiple search queries simultaneously. Returns JSON for Google, Markdown for Bing/Yandex.scrape_batchScrape multiple webpages URLs with advanced options for content extraction and get back the results in MarkDown language. This tool can unlock any webpage even if it uses bot detection or CAPTCHA.discoverSearch the web and rank results by AI-driven relevance. Returns scored results with title, description, and URL. Supports intent-based ranking, geo-targeting, date filtering, and keyword filtering.search_scrapersFind a Bright Data pre-built scraper (Web Scraper API, 1,200+ sites) for a site or data type, e.g. "amazon reviews" or "linkedin.com". Returns dataset_id, name, domain and collection_methods. Next: call get_scraper_details with a dataset_id and one method.get_scraper_detailsShow the scraper description, input fields, example input and main output fields for one method. Call before run_scraper and build the input from sample_input or input_fields. Records may contain more fields than output_fields lists.run_scraperRun a scraper method. input is a list of objects shaped like sample_input from get_scraper_details, one per URL or query. collect_by_url returns one record per input; discover_by_* methods return up to limit_per_input records per input, and every record is billed. Waits up to 45 seconds; if still running it returns snapshot_id with status "running": then poll get_scraper_progress and call get_scraper_results when ready. Records with an "error" field explain failed inputs.get_scraper_progressStatus of a run: starting, running, ready, failed or canceled.get_scraper_resultsRecords of a finished run. Returns status "running" if not ready yet.refresh_scrapersReload the scraper list now instead of waiting for the daily refresh.
Nefesh — Real Time Human State Awareness tools 7
get_human_stateGet current unified human state for a session. Call this before generating important responses. Returns: - state: calm | relaxed | focused | stressed | acute_stress - stress_score: 0-100 (lower = calmer) - confidence: 0.0-1.0 (based on signal quality and device type) - suggested_action: maintain_engagement | simplify_and_focus | de-escalate_and_shorten | pause_and_ground - action_reason: human-readable explanation of why this action was suggested - adaptation_effectiveness (on 2nd+ call): shows whether your previous suggested_action actually reduced stress — contains previous_action, stress_delta, and effective boolean. Use this to self-improve. Use suggested_action to adapt your response: calm/relaxed = full complexity, focused = shorter and structured, stressed = max 2 sentences, acute_stress = one grounding sentence only. Requires a prior ingest call to have data. Not a medical device.ingestSend biometric signals from any sensor, get unified state back. Required: session_id + timestamp (ISO 8601) + at least one signal. Send whatever you have — the API fuses all signals into one state. Common signals (highest impact): - heart_rate (bpm, 30-220) + rmssd (ms) — cardiovascular - tone: calm | tense | anxious | hostile — vocal - sentiment: -1.0 to 1.0 — textual - expression: relaxed | neutral | tense — visual For trigger memory (cross-session psychological tracking): - Include subject_id (consistent per user, hashed) Returns same fields as get_human_state plus signals_received list and topics_detected (if conversation text was included). source_device is optional but improves confidence scoring. Not a medical device.get_trigger_memoryRetrieve psychological trigger profile for a subject. Returns which conversation topics consistently cause stress (active triggers) and which have been resolved over time. - active triggers: topics where stress was elevated across multiple sessions. Tread carefully. - resolved triggers: topics where stress has decreased. Safe to explore deeper. Each trigger includes observation_count, avg_score, peak_score, and last_seen. Requires prior ingest calls with the same subject_id. Not a medical device.get_session_historyGet state history for a session over time. Returns timestamped datapoints with stress_score, state, and heart_rate for each observation. Includes an overall trend: rising | falling | stable. Use minutes parameter to control the lookback window (default: 5, max: 60). Useful for detecting stress patterns during a conversation. Not a medical device.delete_subjectPermanently delete all sessions and trigger memory for a subject. Irreversible. Only call when the user explicitly requests this deletion.request_api_keyStart free API key authorization; no existing API key needed. Returns a verification_url. Ask the user to open that URL in their browser, enter their own email, then open the verification email and confirm access for their agent. This tool does not accept email addresses and does not send email. Do not choose, invent, or submit an email on the user's behalf. Poll check_api_key_status with the returned request_id at the supplied interval. Stop if the request expires. Never create new requests in a loop.check_api_key_statusCheck a pending API key authorization using its request_id. Use request_id exactly as returned by request_api_key, never an email. Poll every 10 seconds. awaiting_user means the user must open the URL; pending means email verification is still required. ready returns the API key once only. Store it and include it in all subsequent HTTP calls. Stop on expired; ask the user before starting another authorization.
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.
Brightdata MCP
{
"mcpServers": {
"brightdata-mcp": {
"command": "npx",
"args": [
"@brightdata/mcp"
],
"env": {
"API_TOKEN": "YOUR_API_TOKEN_HERE"
}
}
}
}
Nefesh — Real Time Human State Awareness
{
"mcpServers": {
"nefesh-real-time-human-state-awareness": {
"url": "https://mcp.nefesh.ai/mcp"
}
}
}
Frequently asked questions
Brightdata MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. Nefesh — Real Time Human State Awareness belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Brightdata MCP for search & data extraction work and Nefesh — Real Time Human State Awareness for developer tools.
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.
Brightdata MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Nefesh — Real Time Human State Awareness 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 brightdata-mcp and nefesh-real-time-human-state-awareness as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Brightdata MCP has a quality signal of 73/100 (Great) with 5 views, 0 installs and 2,685 GitHub stars. Nefesh — Real Time Human State Awareness has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.