Remote MCP · Endpoint

dev.journalize/journalize MCP server

No. dev.journalize/journalize answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://journalize.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.journalize/journalize
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
193 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Agent-native double-entry accounting ledger with x402 micropayments
Website
https://journalize.dev/
Listing
From the official MCP registry (active).
Recent checks of dev.journalize/journalize
CheckedResultHandshake
1 hour agoHandshake completed193 ms
2 days agoHandshake completed194 ms
4 days agoHandshake completed185 ms
6 days agoHandshake completed155 ms
7 days agoHandshake completed142 ms
9 days agoHandshake completed234 ms
10 days agoHandshake completed135 ms
11 days agoHandshake completed166 ms
14 days agoHandshake completed159 ms
15 days agoHandshake completed120 ms
17 days agoHandshake completed1.16 s
18 days agoHandshake completed133 ms
19 days agoHandshake completed142 ms
20 days agoHandshake completed154 ms
21 days agoHandshake completed145 ms
22 days agoHandshake completed162 ms
23 days agoHandshake completed145 ms
24 days agoHandshake completed126 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with dev.journalize/journalize and makes no claim about it beyond what these checks measured.