Remote MCP · Endpoint

3D Texel MCP server

No. 3D Texel answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://3dtexel.com/wp-json/3dtexel-api/v1/mcp

The last check completed an MCP handshake.

Registry name
com.3dtexel/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
470 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search/download 7,000+ PBR materials, HDRIs, decals, 3D assets; generate PBR materials and HDRIs.
Listing
From the official MCP registry (active).
Recent checks of 3D Texel
CheckedResultHandshake
2 hours agoHandshake completed470 ms
2 days agoHandshake completed538 ms
4 days agoHandshake completed523 ms
6 days agoHandshake completed577 ms
8 days agoHandshake completed505 ms
10 days agoHandshake completed753 ms
12 days agoHandshake completed470 ms
14 days agoHandshake completed3.65 s
15 days agoHandshake completed541 ms
16 days agoHandshake completed489 ms
18 days agoHandshake completed453 ms
20 days agoHandshake completed609 ms
22 days agoHandshake completed485 ms
23 days agoHandshake completed539 ms

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

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 3D Texel and makes no claim about it beyond what these checks measured.