mcpbeat Sign in

Toreva Goals MCP Server

answering

Toreva Goals is answering right now. Last checked 5 min ago.

Durable, user-controlled goals for AI agents, kept across any MCP client.

Uptime history 67 days of history · worst day 98%
67 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
433 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Toreva Goals every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add goals --transport http 'https://gateway.toreva.com/mcp?surface=goals'
Settings → Connectors → Add custom connector, then paste this address
https://gateway.toreva.com/mcp?surface=goals
~/.codex/config.toml
[mcp_servers.goals]
url = "https://gateway.toreva.com/mcp?surface=goals"
.cursor/mcp.json
{
  "mcpServers": {
    "goals": {
      "url": "https://gateway.toreva.com/mcp?surface=goals"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "goals": {
      "type": "http",
      "url": "https://gateway.toreva.com/mcp?surface=goals"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://gateway.toreva.com/mcp?surface=goals streamable-http sign-in 386 ms 5 min ago

Alternatives to Toreva Goals

same job, measured the same way
Proofable MCP
by proofable

Context and control for any AI. Agent identity, scoped access, and proof across tools.

4 tools answering
Mifactory Agent Memory
by mifactory-bot

Persistent memory for AI agents across Claude, ChatGPT and any MCP client.

2 tools answering
GoodMemory
by hjqcan

Durable user/project memory for MCP clients: recall context and remember selected facts.

232 installs/wk local only
pond
by tenequm

Lossless archive and search for AI agent sessions across clients, exposed to agents over MCP.

local only
Brainfeather
by brainfeather

Long-term memory for AI coding agents: durable project facts, recalled by every MCP client.

80 installs/wk answering
Sub Agents MCP
by shinpr

MCP server for delegating tasks to specialized AI sub-agents across coding tools

456 installs/wk local only
Janusmcp
by bayway

Multi-account tool broker for AI agents — CLI and MCP.

138 installs/wk local only
Kemory
by sekondbrainailabs

Persistent memory for AI agents: connects MCP clients to your Kemory memory vault

435 installs/wk local only

Toreva Goals — questions

Answers built from our own checks of this server.

Why is there no tool list for Toreva Goals?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Toreva Goals working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 433 ms. The bar chart above shows every period we have measured.
How do I connect Toreva Goals?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Toreva Goals?
No API key is involved. Toreva Goals answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Toreva Goals?
It answers our handshake in 433 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.