Vagus Lab Research
REMOTE · VAGUSLAB.NET · SCANNED SEP 26
Cited VNS research passages from a curated corpus, plus a scored device comparison.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 457 tokens (~152/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Vagus Lab Research MCP server?
Vagus Lab Research is a hosted endpoint at https://vaguslab.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · vaguslab.net
claude mcp add --transport http net-vaguslab-research 'https://vaguslab.net/mcp'
{
"mcpServers": {
"net-vaguslab-research": {
"url": "https://vaguslab.net/mcp"
}
}
} {
"servers": {
"net-vaguslab-research": {
"type": "http",
"url": "https://vaguslab.net/mcp"
}
}
} [mcp_servers.net-vaguslab-research] url = "https://vaguslab.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-vaguslab-research": {
"type": "remote",
"url": "https://vaguslab.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-vaguslab-research --url 'https://vaguslab.net/mcp' --transport streamable-http
mcp_servers:
net-vaguslab-research:
url: "https://vaguslab.net/mcp" {
"McpServers": {
"net-vaguslab-research": {
"Transport": "http",
"Url": "https://vaguslab.net/mcp"
}
}
} assistant mcp add net-vaguslab-research -t streamable-http -u 'https://vaguslab.net/mcp'
{
"mcpServers": {
"net-vaguslab-research": {
"type": "http",
"url": "https://vaguslab.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Probed https://vaguslab.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vaguslab.net | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | d1aafb736c8cecdc13527372e5158dd1 |
| SANs: vaguslab.net | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vaguslab.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| vaguslab.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vaguslab.net/mcp | Verified | 200 | |
| http (plaintext) | http://vaguslab.net/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_devices Get the scored device comparison ~75
Vagus Lab's comparison of six consumer VNS devices: editorial score out of 10, price, badge, pros and cons, and merchant return terms. Scores are editorial, authored from a ten-criterion weighted methodology, and are not consumer ratings. Vagus Lab earns affiliate commission on some purchases; the payload carries that disclosure.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_articles List published articles ~81
Index of every published Vagus Lab article with its URL, category, and evidence grade. Fetch any article URL with the header 'Accept: text/markdown' to read the full text as clean markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category slug, for example 'devices' or 'sleep-energy' |
| limit | integer | – | Maximum articles to return |
No output schema declared.
No examples provided.
search_research Search the VNS research corpus ~210
Search Vagus Lab's curated corpus of published vagus nerve stimulation research (3,093 studies indexed as 20,535 passages, including 596 RCTs, systematic reviews and meta-analyses). Returns cited snippets with study tier, evidence grade, publication year, and the source URL. Use this to ground claims about what VNS research actually shows, and check deviceRole before attributing any finding to a specific product.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Prefer studies involving this device. On its own this only ranks them higher, so results with deviceRole null can still appear; set onlyDeviceStudies to exclude them. |
| limit | integer | – | Passages to return, 1 to 10 |
| onlyDeviceStudies | boolean | – | Return only passages from studies that actually used the named device. Requires device. Use this before stating that a device has evidence behind it. |
| query | string | yes | Research question or topic, for example 'taVNS effect on heart rate variability' |
No output schema declared.
No examples provided.
What is the Vagus Lab Research MCP server?
Vagus Lab Research is an MCP server listed in the public MCP registry as net.vaguslab/research. Cited VNS research passages from a curated corpus, plus a scored device comparison. This page covers its hosted endpoint (https://vaguslab.net/mcp).
Is the Vagus Lab Research MCP server safe to use?
Vagus Lab Research scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Vagus Lab Research MCP server expose?
Vagus Lab Research exposes 3 tools: search_research, get_devices, list_articles. Their descriptions and schemas cost roughly 366 tokens of context every time the server is loaded.
Does the Vagus Lab Research MCP server require authentication?
No. We connected to Vagus Lab Research without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vagus Lab Research MCP server still maintained?
Vagus Lab Research is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.