Timing MCP is answering right now. Last checked 7 min ago.
Is there a materially better time for this call, stream or upload, given where everyone is?
Today is the operative word: we check Timing MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
claude mcp add timing-mcp --transport http https://mcp.kasprdata.com/timing/mcp
https://mcp.kasprdata.com/timing/mcp
[mcp_servers.timing-mcp]
url = "https://mcp.kasprdata.com/timing/mcp"
{
"mcpServers": {
"timing-mcp": {
"url": "https://mcp.kasprdata.com/timing/mcp"
}
}
}
{
"servers": {
"timing-mcp": {
"type": "http",
"url": "https://mcp.kasprdata.com/timing/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.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.kasprdata.com/timing/mcp | streamable-http | sign-in | 583 ms | 7 min ago |
Every Chipp tool in one MCP (large). For one area at a time, use the ai.chipp/chipp-* servers.
82-0 Dream is a browser-based NBA all-time lineup builder where players spin a slot machine for
Marks every line of a Livewire or Blade file that the visitor's browser can call, rewrite or read
MCP server bridging GitHub webhooks via Cloudflare Worker for real-time event streaming
Read-only MCP server for OddsRelay odds data, with a token cap on every call that spends tokens.
Read-only folder triage: what is in a folder, what is stale, and where the space went.
A second opinion, in one call, from a desk where an answer is allowed to be no.
Is this bench result real? Who issued it, at what scope, anchored where? One call answers.
Answers built from our own checks of this server.