Is mcpcentral-time live?

Yes — it answered the hub's last check (checked 41m ago). It answered 100% of checks over the last 30 days.

Is mcpcentral-time free to use?

Yes — the hub reached it with no key and no payment.

What tools does mcpcentral-time have?

6 tools: relative_time, days_in_month, convert_time, current_time, get_timestamp, get_week_year.

Is mcpcentral-time 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.

_ registry / mcp streamable-http · checked 41m ago

mcpcentral-time

https://mcp.time.mcpcentral.io

Registry code: 3ebab3005158d1cb

api record

MCP server for time-related tools: current time, timezone conversion, relative time calculation, and more.

endpoint: https://mcp.time.mcpcentral.io
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 mcpcentral-time live?: Yes — it answered the hub's last check (checked 41m ago). It answered 100% of checks over the last 30 days.
Is mcpcentral-time free to use?: Yes — the hub reached it with no key and no payment.
What tools does mcpcentral-time have?: 6 tools: relative_time, days_in_month, convert_time, current_time, get_timestamp, get_week_year.
Is mcpcentral-time 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 100%· all time 100%

latency

446ms

last good check

priced tools

of 6 tools

_ answered our checks, 90 days 1 checks · signed record

2026-10-27 16:58 unknown → live

_ 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

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 6 tools

2 open 4 never probed 2 of 6 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.

get_timestamp open 41m ago

Converts a date-time string to a Unix timestamp in milliseconds.

mcp-tool

{
  "type": "object",
  "properties": {
    "time": {
      "type": "string",
      "description": "The time to convert. Format: YYYY-MM-DD HH:mm:ss"
    }
  }
}

arguments 9 lines

get_week_year open 41m ago

Returns the week and ISO week number for a given date.

mcp-tool

{
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "The date to check. e.g., \"2025-03-23\""
    }
  }
}

arguments 9 lines

relative_time unknown never probed

Calculates the relative time from now to a given time string.

mcp-tool

{
  "type": "object",
  "required": [
    "time"
  ],
  "properties": {
    "time": {
      "type": "string",
      "description": "The time to compare. Format: YYYY-MM-DD HH:mm:ss"
    }
  }
}

arguments 12 lines

days_in_month unknown never probed

Returns the number of days in the month of a given date.

mcp-tool

{
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "The date to check. Format: YYYY-MM-DD"
    }
  }
}

arguments 9 lines

convert_time unknown never probed

Converts a time from a source timezone to a target timezone.

mcp-tool

{
  "type": "object",
  "required": [
    "sourceTimezone",
    "targetTimezone",
    "time"
  ],
  "properties": {
    "time": {
      "type": "string",
      "description": "The time to convert. e.g., \"2025-03-23 12:30:00\"."
    },
    "sourceTimezone": {
      "type": "string",
      "description": "The source IANA timezone name (e.g., \"Asia/Shanghai\")."
    },
    "targetTimezone": {
      "type": "string",
      "description": "The target IANA timezone name (e.g., \"Europe/London\")."
    }
  }
}

arguments 22 lines

current_time unknown never probed

Returns the current time in UTC and a specified or guessed timezone.

mcp-tool

{
  "type": "object",
  "properties": {
    "format": {
      "type": "string",
      "default": "YYYY-MM-DD HH:mm:ss",
      "description": "The format for the returned time string. Either a dayjs token string (e.g. \"YYYY-MM-DD HH:mm:ss\") or a named format: \"iso8601\" / \"rfc3339\" (ISO 8601 UTC), \"unix\" (epoch seconds), \"unix_ms\" (epoch milliseconds)."
    },
    "timezone": {
      "type": "string",
      "description": "The IANA timezone name (e.g., \"America/New_York\"). Defaults to the server's guessed timezone."
    }
  }
}

arguments 14 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.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
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.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3ebab3005158d1cb.

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

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/3ebab3005158d1cb/badge.svg)](https://brick.blue/agent/3ebab3005158d1cb?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

100%

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

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.

_ also on mcpcentral.io 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

mcpcentral.io MCP Central - mcpcentral.io a2a · 8 tools
jsoncanvas.mcpcentral.io jsoncanvas.mcpcentral.io mcp · 0 tools