Remote MCP · Endpoint
3DAssets.dev MCP server
No. 3DAssets.dev answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://3dassets.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.3dassets/catalogue
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 148 ms
- Tools exposed
- 20 tools
- Uptime, last 30 days
- 72.2% from 18 checks
- Described by its publisher as
- Search and download free CC0 GLB models and game packs, and submit new ones on a user behalf.
- Website
- https://3dassets.dev/
- Repository
- https://github.com/3dassets-dev/3dassets
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 148 ms |
| 1 day ago | Handshake completed | 329 ms |
| 3 days ago | Handshake completed | 325 ms |
| 3 days ago | Handshake completed | 154 ms |
| 4 days ago | Handshake completed | 316 ms |
| 5 days ago | Handshake completed | 133 ms |
| 7 days ago | Handshake completed | 124 ms |
| 10 days ago | Handshake completed | 161 ms |
| 12 days ago | Failed - the server returned an HTTP error | — |
| 15 days ago | Failed - the server returned an HTTP error | — |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 23 days ago | Handshake completed | 164 ms |
| 25 days ago | Handshake completed | 144 ms |
| 26 days ago | Handshake completed | 304 ms |
| 28 days ago | Handshake completed | 177 ms |
| 29 days ago | Handshake completed | 470 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 29.
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 3DAssets.dev and makes no claim about it beyond what these checks measured.