datemint
https://datemint.mike-tusa.workers.dev
Registry code: 9d926a5d2b98d6d2
DateMint turns natural-language dates and times ("next Friday at 3pm", "in 2 weeks", "Dec 25 to Jan 2") into exact ISO 8601 timestamps in any IANA time zone, DST-aware, relative to a reference time you choose. It also extracts every date mention from a block of text with character offsets, normalizes mixed timestamps (ISO 8601, RFC 2822, Unix s/ms/us/ns, slash dates) to UTC, and returns the current time in a zone. Use it before acting on any date a user typed. Free use needs no key: about 10 calls per minute per IP (REST calls and MCP tools/call), no monthly cap. Rule-based parsing…
- endpoint
- https://datemint.mike-tusa.workers.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 datemint live?
- Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
- Is datemint free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does datemint have?
- 4 tools: extract_dates, resolve_date, normalize_timestamps, current_time.
- Is datemint 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.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
current_time open 14h ago
Current date, time, weekday, UTC offset, ISO week and day of year in an IANA time zone. Useful because models do not know today's date.
{ "type": "object", "properties": { "timezone": { "type": "string", "description": "IANA time zone for reading and reporting local times, e.g. \"America/Denver\". Default UTC." } } }arguments 9 linesextract_dates unknown 14h ago
Find every date/time mention in a text (max 4 KB) and return each with its character index, matched text and resolved ISO timestamps (start and optional end of ranges).
{ "type": "object", "required": [ "text" ], "properties": { "text": { "type": "string" }, "locale": { "enum": [ "en", "en-GB", "de", "fr", "es", "pt", "nl", "it", "sv", "fi", "ru", "uk", "ja", "zh" ], "type": "string", "description": "Language of the text. en reads 03/04 as March 4; en-GB as 3 April. Default en." }, "timezone": { "type": "string", "description": "IANA time zone for reading and reporting local times, e.g. \"America/Denver\". Default UTC." }, "reference": { "type": "string", "description": "ISO 8601 date or date-time that relative phrases are resolved against (e.g. \"2026-11-11T09:00:00-07:00\"). Default: current server time." }, "max_results": { "type": "integer", "default": 20, "maximum": 25, "minimum": 1, "description": "Stop after this many dates (default 20, max 25); truncated is true when more were found (truncated_reason \"max_results\"), or when the scan stopped early in number-dense text after roughly 600 numbers (truncated_reason \"number_budget\": later dates were not read; send the rest separately)." }, "forward_date": { "type": "boolean", "description": "Always pick the future reading of phrases like \"Friday\" or \"October 5\". Default false (closest reading)." } } }arguments 50 linesresolve_date unknown 14h ago
Turn one date/time phrase ("next Friday at 3pm", "in 2 weeks", "tomorrow 9am EST", "Dec 25 to Jan 2") into exact ISO 8601 UTC and local timestamps in an IANA zone, with precision, which parts were stated, DST gap/fold flags and ambiguity flags. found:false when no date is recognized. Use before acting on any date a user typed.
{ "type": "object", "required": [ "text" ], "properties": { "text": { "type": "string", "description": "The phrase (max 512 bytes)." }, "locale": { "enum": [ "en", "en-GB", "de", "fr", "es", "pt", "nl", "it", "sv", "fi", "ru", "uk", "ja", "zh" ], "type": "string", "description": "Language of the text. en reads 03/04 as March 4; en-GB as 3 April. Default en." }, "timezone": { "type": "string", "description": "IANA time zone for reading and reporting local times, e.g. \"America/Denver\". Default UTC." }, "reference": { "type": "string", "description": "ISO 8601 date or date-time that relative phrases are resolved against (e.g. \"2026-11-11T09:00:00-07:00\"). Default: current server time." }, "forward_date": { "type": "boolean", "description": "Always pick the future reading of phrases like \"Friday\" or \"October 5\". Default false (closest reading)." } } }arguments 44 linesnormalize_timestamps unknown 41h ago
Convert up to 100 mixed timestamps (ISO 8601, RFC 2822, Unix seconds/ms/us/ns, slash dates, short date phrases) to UTC and local ISO 8601, flagging ambiguous day/month order.
{ "type": "object", "required": [ "values" ], "properties": { "locale": { "enum": [ "en", "en-GB", "de", "fr", "es", "pt", "nl", "it", "sv", "fi", "ru", "uk", "ja", "zh" ], "type": "string", "description": "Language of the text. en reads 03/04 as March 4; en-GB as 3 April. Default en." }, "values": { "type": "array", "items": { "type": [ "string", "number" ] }, "maxItems": 100, "minItems": 1 }, "timezone": { "type": "string", "description": "IANA time zone for reading and reporting local times, e.g. \"America/Denver\". Default UTC." }, "reference": { "type": "string", "description": "ISO 8601 date or date-time that relative phrases are resolved against (e.g. \"2026-11-11T09:00:00-07:00\"). Default: current server time." } } }arguments 47 lines
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.
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, thenPOST /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-endpointwith this listing's id9d926a5d2b98d6d2.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/9d926a5d2b98d6d2/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/9d926a5d2b98d6d2?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.