_ registry / mcp streamable-http · checked 2h ago

temporal-mcp

https://temporal-mcp.dev

Registry code: b9868a7e652dcdb9

api record

Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.

from a public catalogue that lists it, not from the operator

endpoint
https://temporal-mcp.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is temporal-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is temporal-mcp free to use?
Not measured yet.
What tools does temporal-mcp have?
2 tools: temporal_tick, temporal_peek.
Is temporal-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.6%· all time 99.6%

latency
71ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 282 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
developer tools
used for
  • get elapsed time between conversation turns
  • detect a day rollover for a thread
takes → gives
data → data
tools
1 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • temporal_tick changes data unknown never probed

    Advance the temporal clock for a thread and return a snapshot (now / prev / gap / day_rollover / fresh_thread). Call once per user turn. Pass a stable `thread_key` (e.g. the conversation ID) so gap deltas remain meaningful across page reloads.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "tz_name": {
      "type": "string",
      "description": "Display name for the timezone (e.g. 'MDT'). Cosmetic; appears in the rendered header."
    },
    "client_id": {
      "type": "string",
      "description": "Namespace tag (e.g. 'caweb', 'cursor'). Defaults to 'mcp'."
    },
    "thread_key": {
      "type": "string",
      "description": "Stable thread identifier within this client. For claude.ai web use the conversation ID; for other MCP clients any caller-stable string. If omitted, falls back to the Mcp-Session-Id header."
    },
    "tz_offset_minutes": {
      "type": "integer",
      "description": "Caller's UTC offset in minutes (e.g. -360 for MDT). Used for day_rollover detection and header formatting. Defaults to 0 (UTC) so day rollover is always honest even if the caller forgets to pass one."
    }
  }
}
    arguments 21 lines
  • temporal_peek reads unknown never probed

    Read the current temporal snapshot for a thread WITHOUT advancing state. Use this when you want the gap delta but the call is not the canonical per-turn event.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "tz_name": {
      "type": "string"
    },
    "client_id": {
      "type": "string"
    },
    "thread_key": {
      "type": "string"
    },
    "tz_offset_minutes": {
      "type": "integer"
    }
  }
}
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b9868a7e652dcdb9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b9868a7e652dcdb9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b9868a7e652dcdb9/badge.svg)](https://brick.blue/agent/b9868a7e652dcdb9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.