mcpbeat Sign in

SMEme MCP Server

answering

SMEme is answering right now. Last checked 14 min ago.

SMEme is the formal reasoning layer for AI: a symbolic solver over decision trees.

Uptime history 17 hours of history
17 hours agonow
100.0%
Uptime 24h
62 of 62 checks
—
Tools
hidden behind auth
256 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check SMEme 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 14 min ago.

run in your terminal
claude mcp add reasoning --transport http https://app.smeme.ai/api/v1/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.smeme.ai/api/v1/mcp
~/.codex/config.toml
[mcp_servers.reasoning]
url = "https://app.smeme.ai/api/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "reasoning": {
      "url": "https://app.smeme.ai/api/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "reasoning": {
      "type": "http",
      "url": "https://app.smeme.ai/api/v1/mcp"
    }
  }
}

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://app.smeme.ai/api/v1/mcp streamable-http sign-in 194 ms 14 min ago

Alternatives to SMEme

same job, measured the same way
Frugal
by brainsparker

The open routing layer for AI tools: tool calls routed per policy, decision on every result.

74 installs/wk local only
memi
by memi-design

Memi is the design layer for agentic AI.

local only
Agentskin
by shawn5cents

The Semantic Layer for AI Agents. Prunes noisy API data by 70%+ for token-efficient reasoning.

122 installs/wk local only
M
MemoryLayer
by memorylayer

Local-first persistent memory for AI agents, with reasoning and formal verification.

55 installs/wk local only
Engramic
by engramic

Your organisation's decisions, goals and constraints, with the reasoning, for every agent.

answering
Toki Toki
by xfloukiex-lab

A local causality ledger: records decisions and the reasons, for an agent to recall.

139 installs/wk local only
Gatewerk
by gatewerk

The open-source review layer for AI agents. Work done for humans is decided by humans.

39 installs/wk local only
Reasonbook
by aquex

Reasonbook: decisions that survive the session, in a local record AI agents keep.

735 installs/wk local only

SMEme — questions

Answers built from our own checks of this server.

Why is there no tool list for SMEme?
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 SMEme working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 62 of 62 checks got a reply (100.0%), average response time 256 ms. The bar chart above shows every period we have measured.
How do I connect SMEme?
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 SMEme?
No API key is involved. SMEme 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 SMEme?
It answers our handshake in 256 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.