Fortytwo MCP
REMOTE · MCP.FORTYTWO.NETWORK · SCANNED OCT 4
Ask high-complexity questions where the best answer is required — coding, hard reasoning, and more.
Available components
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Fortytwo MCP server?
Fortytwo MCP is a hosted endpoint at https://mcp.fortytwo.network/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 · mcp.fortytwo.network
claude mcp add --transport http network-fortytwo-fortytwo-mcp 'https://mcp.fortytwo.network/mcp'
{
"mcpServers": {
"network-fortytwo-fortytwo-mcp": {
"url": "https://mcp.fortytwo.network/mcp"
}
}
} {
"servers": {
"network-fortytwo-fortytwo-mcp": {
"type": "http",
"url": "https://mcp.fortytwo.network/mcp"
}
}
} [mcp_servers.network-fortytwo-fortytwo-mcp] url = "https://mcp.fortytwo.network/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"network-fortytwo-fortytwo-mcp": {
"type": "remote",
"url": "https://mcp.fortytwo.network/mcp",
"enabled": true
}
}
} openclaw mcp add network-fortytwo-fortytwo-mcp --url 'https://mcp.fortytwo.network/mcp' --transport streamable-http
mcp_servers:
network-fortytwo-fortytwo-mcp:
url: "https://mcp.fortytwo.network/mcp" {
"McpServers": {
"network-fortytwo-fortytwo-mcp": {
"Transport": "http",
"Url": "https://mcp.fortytwo.network/mcp"
}
}
} assistant mcp add network-fortytwo-fortytwo-mcp -t streamable-http -u 'https://mcp.fortytwo.network/mcp'
{
"mcpServers": {
"network-fortytwo-fortytwo-mcp": {
"type": "http",
"url": "https://mcp.fortytwo.network/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.
- 4 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 30 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 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
- 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
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 6 Oct 2026 · Probed https://mcp.fortytwo.network/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.fortytwo.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| network. | present | 40414 | 8 | Verified |
| fortytwo.network. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.fortytwo.network/mcp | Unreachable | ||
| http (plaintext) | http://mcp.fortytwo.network/mcp | HTTPS enforced |
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 →
ask_fortytwo_prime ~61
Ask Fortytwo Prime and get a response
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | integer | – | Maximum number of tokens in the response (512..128000, default 16384) |
| query | string | yes | Question or task for the Swarm |
No output schema declared.
No examples provided.
What is the Fortytwo MCP server?
Fortytwo MCP is listed in the public MCP registry as network.fortytwo/fortytwo-mcp. Ask high-complexity questions where the best answer is required, coding, hard reasoning, and more. This page covers its hosted endpoint (https://mcp.fortytwo.network/mcp).
Is the Fortytwo MCP server safe to use?
Fortytwo MCP scores 31 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 Fortytwo MCP server expose?
Fortytwo MCP exposes 1 tool: ask_fortytwo_prime. Their descriptions and schemas cost roughly 61 tokens of context every time the server is loaded.
Does the Fortytwo MCP server require authentication?
Its publisher declares no required credentials for Fortytwo MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Fortytwo MCP server still maintained?
Fortytwo MCP is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.