mcpbeat

Jampolls MCP Server

com.jampolls.hub/mcp-server
answering

Jampolls is answering right now. Last checked 3 min ago.

Real-time polls, surveys, quizzes, trivia, Q&A, and word clouds for teams, educators, and creators.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
389 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add mcp-server --transport http https://hub.jampolls.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://hub.jampolls.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-server]
url = "https://hub.jampolls.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://hub.jampolls.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://hub.jampolls.com/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://hub.jampolls.com/mcp streamable-http answering 395 ms 3 min ago

Jampolls — questions

Answers built from our own checks of this server.

Is Jampolls 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 389 ms. The bar chart above shows every period we have measured.
How do I connect Jampolls?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Jampolls need an API key?
No. Jampolls completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How fast is Jampolls?
It answers our handshake in 389 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.