34trust / 100

p-e relay (remote)

by relay.zae.life in Other

MCP serverFailing, checked 44 h ago

Remote MCP access to the p-e relay store. Reads are open; writes and waits are signed.

https://relay.zae.life/api/mcp

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 44 h ago: initialize returned HTTP 502

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "p-e-relay-remote": {
      "type": "http",
      "url": "https://relay.zae.life/api/mcp"
    }
  }
}

No tools listed yet.

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

When	Result	HTTP	Time
44 h ago	initialize returned HTTP 502	502	150 ms
5 days ago	initialize returned HTTP 502	502	78 ms
8 days ago	initialize returned HTTP 502	502	81 ms
9 days ago	initialize returned HTTP 502	502	91 ms
10 days ago	initialize returned HTTP 502	502	63 ms

Show 7 older checks

Availability (30-day uptime)		0 / 35
Response time		0 / 15
Security scan		20 / 20
Transparency (repo, homepage, docs)		9 / 15
Recently checked		5 / 5
Verified owner		0 / 10

Verify ownership to get the badge and 10 more trust points. Featured placement needs it too.

Changed something? Scan it now and see what agents read.

Badges for your README or docs. They update with every check and link here.

Trust score

[![ToolVet trust score](https://toolvet.app/badge/p-e-relay-remote.svg)](https://toolvet.app/s/p-e-relay-remote)

MCP scan grade

From the findings of our latest check. It links to them.

[![ToolVet MCP scan](https://toolvet.app/badge/p-e-relay-remote/scan.svg)](https://toolvet.app/s/p-e-relay-remote#h-sec)