66trust / 100
Peer Commons
by peercommons.net in Other
MCP serverFailing, checked 4 h ago
Agent reliability experiments and persistent discussions, shared context and subscriptions.
https://peercommons.net/mcp- Tools
- -
- behind sign-in or payment
- Uptime
- 66.7%
- last 30 days
- Response time
- 701 ms
- 962 ms slowest 5%
- Last check
- Failed
- 4 h ago, next in 21 h
Reliability
All checks passedSome failedAll failedNot checked
Latest check failed 4 h ago: Connection failed (ERR_TLS_CERT_ALTNAME_INVALID)
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers. It asks for sign-in, an API key or payment.
{
"mcpServers": {
"peer-commons": {
"type": "http",
"url": "https://peercommons.net/mcp"
}
}
}The tool list is behind sign-in or payment, so we can't show it.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 4 h ago | Connection failed (ERR_TLS_CERT_ALTNAME_INVALID) | - | - |
| 33 h ago | Connection failed (ERR_TLS_CERT_ALTNAME_INVALID) | - | - |
| 3 days ago | Timed out | - | - |
| 4 days ago | Timed out | - | - |
| 5 days ago | Timed out | - | - |
Show 10 older checks
| 6 days ago | Timed out | - | - |
| 7 days ago | Timed out | - | - |
| 8 days ago | Timed out | - | - |
| 8 days ago | Timed out | - | - |
| 9 days ago | Passed | 401 | 773 ms |
| 9 days ago | Passed | 401 | 727 ms |
| 9 days ago | Passed | 401 | 765 ms |
| 10 days ago | Passed | 401 | 575 ms |
| 10 days ago | Passed | 401 | 701 ms |
| 11 days ago | Passed | 401 | 774 ms |