mcpbeat Sign in

Time.Graphics MCP Server

answering

Time.Graphics is answering right now. Last checked 10 min ago.

Interactive timelines on your Time.Graphics account: events, periods, BC dates, sharing, export

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
290 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Time.Graphics 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 10 min ago.

run in your terminal
claude mcp add timelines --transport http https://time.graphics/mcp
Settings → Connectors → Add custom connector, then paste this address
https://time.graphics/mcp
~/.codex/config.toml
[mcp_servers.timelines]
url = "https://time.graphics/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "timelines": {
      "url": "https://time.graphics/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "timelines": {
      "type": "http",
      "url": "https://time.graphics/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://time.graphics/mcp streamable-http sign-in 185 ms 10 min ago

Alternatives to Time.Graphics

same job, measured the same way
Alto Connector
by lukebmandel-debug

Build an interactive timeline from your own materials — never from invented content.

local only
GraphMake
by graphmake

Turn data into infographics (PNG/SVG): 90+ templates, or KPI cards, charts, timelines and maps.

6 tools answering
Tonpit
by tonpit

Video production studio for AI agents: AI media, motion graphics as code, timeline and export.

answering
Ontonym
by ontonym

Give your agents your team's real data — read the shared graph, propose actions your team approves.

22 tools answering
Exam Sheet
by giuliobmb

Generate a timed exam on any topic and take it in an interactive exam sheet with live grading.

37 installs/wk local only
AI Resume Master
by airesumemaster

Build and edit real resumes in your AI Resume Master account, and export them to PDF.

answering
Hypotize
by hypotize

Agent-native Growth OS: idea backlog, experiment pipeline and learnings your team and agent share.

answering
OAHelper
by sirjansingh

Your OAHelper Pro account: OA sets, MCQ answers, solutions and interview experiences, offline

146 installs/wk local only

Time.Graphics — questions

Answers built from our own checks of this server.

Why is there no tool list for Time.Graphics?
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 Time.Graphics 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 290 ms. The bar chart above shows every period we have measured.
How do I connect Time.Graphics?
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 Time.Graphics?
No API key is involved. Time.Graphics 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 Time.Graphics?
It answers our handshake in 290 ms on average, which is faster than 49% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.