Remote MCP · Endpoint

ForensiScope by Evercraft MCP server

No. ForensiScope by Evercraft answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://evercraft-forensiscope.base44.app/functions/forensiScopeMcp

The last check completed an MCP handshake.

Registry name
io.github.jgaethle10/forensiscope
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
194 ms
Tools exposed
4 tools
Uptime, last 30 days
7.1% from 14 checks
Described by its publisher as
Start with classify_media_route to route long or oversized audio/video by size or duration.
Website
https://evercraft-forensiscope.base44.app/functions/forensiScopeAgentGateway?view=docs
Repository
https://github.com/jgaethle10/forge-operator
Listing
From the official MCP registry (active).
Recent checks of ForensiScope by Evercraft
CheckedResultHandshake
1 hour agoHandshake completed194 ms
9 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
24 days agoFailed - the server returned an HTTP error—
26 days agoFailed - the server returned an HTTP error—
28 days agoFailed - the server returned an HTTP error—

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

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 ForensiScope by Evercraft and makes no claim about it beyond what these checks measured.