Fortytwo MCP
network.fortytwoPublished by fortytwo.networkOfficial publisherv0.1.0Updated Oct 24, 2026
Ask high-complexity questions where the best answer is required — coding, hard reasoning, and more.
Overview
A remote MCP endpoint that lets an assistant route high-complexity questions, such as coding or hard reasoning tasks, to an external answering service.
- What you can do
- Fortytwo MCP is a remote, streamable HTTP MCP server reached at a hosted endpoint. Its stated purpose is to answer high-complexity questions where the best possible answer is required, including coding and hard reasoning. The manifest does not list individual tools, so the exact tool names and inputs are not documented here. Paid tool calls are indicated by the payment header described in the manifest.
- When to use it
- Consider it when you want an assistant to hand off difficult questions, such as coding problems or demanding reasoning tasks, to a separate hosted service rather than answering locally. It is less relevant for routine queries or for workflows that must stay entirely on your own machine.
- Requirements
- A remote MCP client that supports streamable HTTP, plus network access to the hosted endpoint. No local package or runtime is declared. For paid tool calls, the X-PAYMENT header is required; the manifest describes it as an x402Escrow payment header using USDC on Base or Monad. No accounts, environment variables, or other credentials are declared.
Installation
In SourceWeft
- Open Fortytwo MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/network.fortytwo%2Ffortytwo-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"fortytwo": {
"type": "http",
"url": "https://mcp.fortytwo.network/mcp"
}
}
}Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
28% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.