Meridian MCP server
com.clawhard/meridianclawhard.comstreamable-httpv1.0.0Scanned
Convert times between zones with daylight saving right, see who is awake, find meeting slots.
4 tools: 1 do something that can't be undone and 3 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Meridian MCP server can do
The Meridian MCP server is published by clawhard.com, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (meridian_convert_time) and create or change data (3 tools: meridian_now, meridian_meeting_slots and meridian_zone_info), but cannot delete data. None of its tools only reads.
1 tool can send data out of your system (meridian_convert_time).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Can't be undone 1Claude Code: ask
meridian_convert_timeUse when you need to convert a specific wall-clock time from one place to others, for any date.Can send data out1 finding
Why it is in this group
- The name "meridian_convert_time" says "convert": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "meridian_convert_time" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "meridian_convert_time" says "convert": a word for a change.
Description, as the server wrote it Use when you need to convert a specific wall-clock time from one place to others, for any date. It uses the real tz database, so daylight saving is right for that exact date (the US and Europe switch on different weeks), and it warns when the time does not exist (spring forward) or happens twice (fall back). Time accepts "15:00", "3:30pm", "noon", "now" or an ISO local time like 2026-11-05T15:00 (no Z). Date defaults to today in the source zone. Returns {input, utc, source:{...}, converted:[{place, zone, local, time_12h, date, utc_offset, abbreviation, day_note, hours_ahead_of_source}], warning?, summary, open_url}.
Annotations the server declares
- title: Convert a time between time zones, DST-correct
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Changes things 3Claude Code: ask
meridian_meeting_slotsUse when you need to schedule a call across several places.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use when you need to schedule a call across several places. Scans the day in 15-minute steps and ranks start times so the most people are inside working hours and nobody is at night, using each place's real offset and DST for that date. Returns up to 5 slots with each person's local start and end, and says plainly when no time works for everyone. Defaults: working hours 9 to 17, 60 minutes, date today in the first place.
Annotations the server declares
- title: Find meeting times that work across time zones
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
meridian_nowUse when the user asks what time or date it is right now somewhere.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use when the user asks what time or date it is right now somewhere. Reads the server clock and returns the current time, date, UTC offset, abbreviation and daylight saving status for each place. Places can be cities ("Tokyo"), IANA zones ("Europe/Paris"), abbreviations ("PST") or "UTC+5:30".
Annotations the server declares
- title: Current time in any places or time zones
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
meridian_zone_infoUse when you need to answer "what is the UTC offset of X", "does X observe daylight saving" and "when do the clocks change".No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use when you need to answer "what is the UTC offset of X", "does X observe daylight saving" and "when do the clocks change". Returns the current offset and abbreviation, whether the place observes DST, every clock change in the year with exact local before and after times, and the next change. Abbreviations like IST or CST are ambiguous, so the answer says which zone was used.
Annotations the server declares
- title: Offset, abbreviation and daylight saving changes for a zone
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:24 UTC, unchanged since Nov 3, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://meridian.clawhard.com/mcp: tools/list returned 4 tools to an anonymous client, including meridian_convert_time (irreversible), meridian_now (write), meridian_meeting_slots (write), meridian_zone_info (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "meridian_convert_time" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "meridian_convert_time" says "convert": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:meridian_convert_timeCan't be undonedescription
- Changed:meridian_meeting_slotsChanges thingsdescription
- Changed:meridian_nowChanges thingsdescription
- Changed:meridian_zone_infoChanges thingsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http meridian https://meridian.clawhard.com/mcpclaude mcp add --transport http meridian https://meridian.clawhard.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__meridian__meridian_now",
"mcp__meridian__meridian_convert_time",
"mcp__meridian__meridian_meeting_slots",
"mcp__meridian__meridian_zone_info"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as meridian. Review it before you use it.
Capability tags behind 1 rule
- mcp__meridian__meridian_convert_time outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.clawhard/meridian/verify?hash=ba344ea1e5ee4b4427895bbb81ec6f35b4d8cfd1668b85f48ba5ef0a4a30a29c" | jq -e '.changed == false'Pinned hash ba344ea1e5ee, from Nov 16, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.clawhard/meridian/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.clawhard/meridian)Source: MCP Registry. Synced Nov 2, 2026, 22:17 UTC.
Meridian MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Meridian MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Meridian MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Meridian MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: meridian_convert_time.
What tools does the Meridian MCP server have?
- 4 tools: 1 irreversible, 3 write. meridian_convert_time, meridian_now, meridian_meeting_slots and meridian_zone_info.
Does the Meridian MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Meridian MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): meridian_convert_time.
Has the Meridian MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.