Other · Remote MCP server
Toreva Goals
Durable, user-controlled goals and governed plans for AI agents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.toreva/goals- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-28
- Updated
- 2026-08-28
- Publisher
- toreva (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/toreva) · how
- Website
- toreva.com/connect-claude?utm_source=official_mcp_registry&utm_medium=directory&utm_campaign=first_real_goal&utm_content=toreva_goals
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://gateway.toreva.com/mcp?surface=goals | 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 Toreva Goals
Toreva Goals is a remote MCP server: there is nothing to install. Its endpoint is https://gateway.toreva.com/mcp?surface=goals, 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 from toreva (GitHub)
| Server | Runs |
|---|---|
| KitPolicy-checked Solana wallet actions with user-set limits, unsigned transactions, and receipts. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| TopMessageSend and schedule SMS and WhatsApp messages, manage contacts and templates, and track delivery. | Remote · HTTPLive check: sign-in required |
| TopSMSCzech SMS gateway: send and schedule SMS, OTP verification codes, delivery status and credit. | Local · stdio |
| Torah MCPSource discipline for Torah study in Claude: read the real texts, quote exactly, never fabricate. | Remote · HTTPLive check: ✓ handshake |
| TorchlyAgent-run distribution: find private communities, estimate CPA, launch admin-approved campaigns. | Remote · HTTPLive check: sign-in required |
| Tork GovernanceAI agent governance for MCP: PII detection, policy enforcement, compliance, and kill switch. | Local · stdio |
| Total ParksRead-only MCP tools for Total Parks-listed Australian holiday parks, caravan parks, and campgrounds. | Remote · HTTPLive check: ✓ handshake |
| Total RecallPersistent, verified, cross-session memory for AI agents. 26 tools. SQLite + sync. | Local · stdio |
| TotemTotem - talk to your wearables with AI. Today: full Whoop access (48 tools). | Local · stdio |