Major Labs
REMOTE · MAJORLABS.CO · SCANNED SEP 26
Open agentic-web datasets: Agent Trust Index, MCP stats, incident timeline. Read-only, CC-BY-4.0.
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 Security63
- 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 5 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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
- Tool/resource definitions use about 305 tokens (~61/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 Major Labs MCP server?
Major Labs is a hosted endpoint at https://majorlabs.co/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 · majorlabs.co
claude mcp add --transport http co-majorlabs-major-labs 'https://majorlabs.co/mcp'
{
"mcpServers": {
"co-majorlabs-major-labs": {
"url": "https://majorlabs.co/mcp"
}
}
} {
"servers": {
"co-majorlabs-major-labs": {
"type": "http",
"url": "https://majorlabs.co/mcp"
}
}
} [mcp_servers.co-majorlabs-major-labs] url = "https://majorlabs.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-majorlabs-major-labs": {
"type": "remote",
"url": "https://majorlabs.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-majorlabs-major-labs --url 'https://majorlabs.co/mcp' --transport streamable-http
mcp_servers:
co-majorlabs-major-labs:
url: "https://majorlabs.co/mcp" {
"McpServers": {
"co-majorlabs-major-labs": {
"Transport": "http",
"Url": "https://majorlabs.co/mcp"
}
}
} assistant mcp add co-majorlabs-major-labs -t streamable-http -u 'https://majorlabs.co/mcp'
{
"mcpServers": {
"co-majorlabs-major-labs": {
"type": "http",
"url": "https://majorlabs.co/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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
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://majorlabs.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=majorlabs.co | CN=YE2,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 64e2cd1a9454aac0df551708b8f7969ea2a |
| SANs: majorlabs.co, www.majorlabs.co | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of majorlabs.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| majorlabs.co. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://majorlabs.co/mcp | Verified | 200 | |
| http (plaintext) | http://majorlabs.co/mcp | HTTPS enforced | 301 | https://majorlabs.co/mcp |
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_agent_identity_tracker Agent Identity Tracker ~44
Every announced framework, protocol, standard, and regulation for AI agent identity, delegation, and know-your-agent (KYA) verification, dated and traced to primary sources.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_mcp_ecosystem_stats MCP ecosystem statistics ~51
Aggregate statistics from the Major Labs weekly sweep of the MCP server ecosystem: census size, activity, transport and language breakdowns, and security/identity aggregates. Firsthand, read-only measurement.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_threshold_watch Threshold Watch ~42
Dated, hashed snapshots of the frontier labs' published safety frameworks, with diffs when a framework changes. A change event means a lab edited its safety commitments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trust_index Agent Trust Index ~59
The weekly Agent Trust Index: one composite score (0-100) for how safe the agentic web is to transact on, fused from code-safety, identity, and supply-chain pillars, with the per-pillar numbers and methodology version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_incidents Frontier Incident Timeline ~48
A dated, sourced record of frontier AI control incidents: containment escapes, unsanctioned live-system actions, evaluation incidents, and insider disclosures, with published inclusion criteria and sources for every claim.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Major Labs MCP server?
Major Labs is an MCP server listed in the public MCP registry as co.majorlabs/major-labs. Open agentic-web datasets: Agent Trust Index, MCP stats, incident timeline. Read-only, CC-BY-4.0. This page covers its hosted endpoint (https://majorlabs.co/mcp).
Is the Major Labs MCP server safe to use?
Major Labs 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 Major Labs MCP server expose?
Major Labs exposes 5 tools: get_trust_index, get_mcp_ecosystem_stats, list_incidents, get_agent_identity_tracker, get_threshold_watch. Their descriptions and schemas cost roughly 244 tokens of context every time the server is loaded.
Does the Major Labs MCP server require authentication?
No. We connected to Major Labs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Major Labs MCP server still maintained?
Major Labs 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.