Other · Remote MCP server
Toolforest
Hosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.toolforest/toolforest- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-06-12
- Updated
- 2026-06-12
- Publisher
- io.toolforest
- Namespace
- Namespace verified by the MCP Registry via the domain toolforest.io · how
- Website
- www.toolforest.io
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.toolforest.io/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Toolforest
Toolforest is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.toolforest.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| ToolBudget Router MCPPaid remote MCP for context-budget routing, schema cost estimates, usage audits, and readiness. | Remote · HTTPLive check: ✗ no handshake |
| Toolcairn MCPMCP server for tool discovery: find, compare, and verify tools across 35+ registries. | Local · stdio |
| Toolchain Lens MCPLocal explanation of reproducibility signals and toolchain contradictions without exact versions... | Local · stdio |
| ToolfactoryBuild an agent tool once; ship it as Agent Skills, MCP servers, Agent Plugins / Claude / Codex. | Local · stdio |
| Toolkit MCP ServerGenerate IDs, QR codes, and hashes, encode values, geolocate IPs, plus gated host diagnostics. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| ToolpinCheck whether an MCP server answers, what its tools claim, and whether that claim has changed. | Remote · HTTPLive check: ✓ handshake |
| ToolRouterThe OpenRouter for tools. One MCP connection gives any AI agent 254 hosted tools, pay per call. | Remote · HTTPLive check: ✓ handshake |
| Tools for AgentsDecision Layer for AI Agents - 58+ tools, Advisor, MCP. Free key: POST /v1/register {}. | Remote · HTTPLive check: ✓ handshake |