io.github.jordanburke/temporal-mcp-server
REMOTE · TIME.SOMAMCP.COM · 2 COMPONENTS
Time, timezone and duration tools — IANA zones, conversion, DST-correct date arithmetic.
Available components
Last scanned (12 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 520 tokens (~104/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://time.somamcp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=somamcp.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b33ab94972b8a8c913b8533012ef4611 |
| SANs: somamcp.com, time.somamcp.com, *.time.somamcp.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of time.somamcp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| somamcp.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://time.somamcp.com/mcp | Verified | 200 | |
| http (plaintext) | http://time.somamcp.com/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_duration ~203
Add an ISO-8601 duration to a timestamp, in a timezone. Date units (Y/M/D) are calendar-aware: P1D across a DST boundary keeps the same wall-clock time the next day, and P1M on Jan 31 clamps to the end of February. Time units (H/M/S) are exact elapsed time, so PT24H really is 24 hours. Prefix the duration with '-' to subtract.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | string | yes | ISO-8601 duration, e.g. 'P1D', 'PT30M', 'P1Y2M3DT4H5M6S', or '-P1W'. |
| isoTimestamp | string | yes | ISO-8601 timestamp to shift. |
| timezone | string | – | IANA timezone governing the arithmetic — calendar units are applied to this zone's wall clock, and a timestamp with no 'Z' or offset is read as wall-clock time here. Defaults to UTC. |
No output schema declared.
No examples provided.
convert_timezone ~107
Render an ISO-8601 timestamp as wall-clock time in a target timezone.
| Name | Type | Req | Description |
|---|---|---|---|
| isoTimestamp | string | yes | ISO-8601 timestamp to convert, e.g. '2026-08-17T14:30:00Z'. |
| sourceTimezone | string | – | IANA timezone used to interpret `isoTimestamp` when it carries no 'Z' or offset. Ignored otherwise. Defaults to UTC. |
| targetTimezone | string | yes | IANA timezone identifier to render in. |
No output schema declared.
No examples provided.
get_current_time ~59
Return the current time as an epoch, a UTC ISO-8601 timestamp, and the wall-clock time in a given timezone.
| Name | Type | Req | Description |
|---|---|---|---|
| timezone | string | – | IANA timezone identifier, e.g. 'America/New_York'. Defaults to UTC. |
No output schema declared.
No examples provided.
info ~28
Returns identity and build information for this server (name, version, build commit, runtime, capability counts)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
time_between ~123
Exact elapsed time between two ISO-8601 timestamps, broken into days/hours/minutes/seconds plus a human-readable summary. All components share one sign, so they sum correctly; `direction` is 'past', 'future', or 'same'.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Start of the interval, as an ISO-8601 timestamp. |
| timezone | string | – | IANA timezone used to interpret timestamps that carry no 'Z' or offset. Defaults to UTC. |
| to | string | yes | End of the interval, as an ISO-8601 timestamp. |
No output schema declared.
No examples provided.
How do I install the io.github.jordanburke/temporal-mcp-server server?
io.github.jordanburke/temporal-mcp-server is a hosted endpoint at https://time.somamcp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · time.somamcp.com
claude mcp add --transport http jordanburke-temporal-mcp-server 'https://time.somamcp.com/mcp'
What is the io.github.jordanburke/temporal-mcp-server server?
io.github.jordanburke/temporal-mcp-server is listed in the public MCP registry as io.github.jordanburke/temporal-mcp-server. Time, timezone and duration tools, IANA zones, conversion, DST-correct date arithmetic. This page covers its hosted endpoint (https://time.somamcp.com/mcp).
Is the io.github.jordanburke/temporal-mcp-server server safe to use?
io.github.jordanburke/temporal-mcp-server scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.jordanburke/temporal-mcp-server server expose?
io.github.jordanburke/temporal-mcp-server exposes 5 tools: info, get_current_time, convert_timezone, add_duration, time_between. Their descriptions and schemas cost roughly 520 tokens of context every time the server is loaded.
Does the io.github.jordanburke/temporal-mcp-server server require authentication?
No. We connected to io.github.jordanburke/temporal-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.jordanburke/temporal-mcp-server server still maintained?
io.github.jordanburke/temporal-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.