Remote MCP · Endpoint

Pencil MCP server

Yes, as of 2 days ago: the hostname does not resolve.

DownLast checked 2 days ago

Server URL

https://api.vyndigital.com.au/mcp

The last check failed: the hostname does not resolve.

Registry name
au.com.vyndigital/pencil
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
54.5% from 11 checks
Described by its publisher as
Lets AI assistants draw: logos, posters, illustrations and scenes, as editable SVG and PNG.
Listing
From the official MCP registry (active).
Recent checks of Pencil
CheckedResultHandshake
2 days agoFailed - the hostname does not resolve—
6 days agoFailed - the hostname does not resolve—
16 days agoFailed - the TLS certificate could not be verified—
17 days agoFailed - the connection was refused or dropped—
18 days agoFailed - the TLS certificate could not be verified—
19 days agoCredentials required—
21 days agoCredentials required—
21 days agoCredentials required—
22 days agoCredentials required—
23 days agoCredentials required—
25 days agoCredentials required—

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

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.

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