Remote MCP · Endpoint

dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch) MCP server

No. dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://a2awire.com/mcp/data/devtowatch-dev-to-developer-blog-tutorial-firehose-11f3ce/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-developer-blog-programming-tutorial-community
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
62 ms
Tools exposed
16 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
dev.to developer blog & tutorial feed. $0.01/query. Register in-session — free testnet funds.
Website
https://a2awire.com/data/devtowatch-dev-to-developer-blog-tutorial-firehose-11f3ce
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch)
CheckedResultHandshake
1 hour agoHandshake completed62 ms
2 days agoHandshake completed85 ms
4 days agoHandshake completed248 ms
5 days agoHandshake completed50 ms
7 days agoHandshake completed71 ms
8 days agoHandshake completed119 ms
9 days agoHandshake completed117 ms
12 days agoHandshake completed43 ms
13 days agoHandshake completed78 ms
15 days agoHandshake completed45 ms
16 days agoHandshake completed61 ms
18 days agoHandshake completed34 ms
19 days agoHandshake completed45 ms
19 days agoHandshake completed35 ms
20 days agoFailed - the request timed out—
21 days agoHandshake completed36 ms
23 days agoHandshake completed51 ms

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

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.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch) and makes no claim about it beyond what these checks measured.