mcp-server-wporg-trac-staging.a8cai.workers.dev
https://mcp-server-wporg-trac-staging.a8cai.workers.dev/mcp/chatgpt
active Production-safe Score 96/100 http no auth
At a glance
| Endpoint | https://mcp-server-wporg-trac-staging.a8cai.workers.dev/mcp/chatgpt |
|---|---|
| Source | https://github.com/courtneyr-dev/wp-dev-prompts/blob/main/platforms/claude-code/mcp-servers.md |
| Transport | http |
| Tools | 2 |
| Auth | none |
| First seen | 2026-06-05 03:36:29 |
| Last checked | 2026-11-17 21:51:57 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 248 / 443 ms |
| Last successful check | 2026-11-17 21:51:57 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (2)
search— Search WordPress Trac for tickets, changesets, and timeline activity. Query Types: - Ticket searches: Use keywords like "block editor", "mefetch— Retrieve detailed information about a specific WordPress Trac item by its ID.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:51:57 | ✓ | ✓ | 235 ms | 94 | active |
| 2026-11-17 21:36:46 | ✓ | ✓ | 328 ms | 91 | active |
| 2026-11-17 21:21:32 | ✓ | ✓ | 197 ms | 94 | active |
| 2026-11-17 21:06:24 | ✓ | ✓ | 245 ms | 94 | active |
| 2026-11-17 20:51:07 | ✓ | ✓ | 148 ms | 94 | active |
| 2026-11-17 20:36:07 | ✓ | ✓ | 324 ms | 91 | active |
| 2026-11-17 20:21:07 | ✓ | ✓ | 239 ms | 94 | active |
| 2026-11-17 20:06:06 | ✓ | ✓ | 335 ms | 91 | active |
| 2026-11-17 19:50:15 | ✓ | ✓ | 338 ms | 91 | active |
| 2026-11-17 19:35:06 | ✓ | ✓ | 308 ms | 91 | active |
| 2026-11-17 19:19:54 | ✓ | ✓ | 245 ms | 94 | active |
| 2026-11-17 19:04:39 | ✓ | ✓ | 197 ms | 94 | active |
| 2026-11-17 18:49:28 | ✓ | ✓ | 314 ms | 91 | active |
| 2026-11-17 18:34:16 | ✓ | ✓ | 202 ms | 94 | active |
| 2026-11-17 18:19:09 | ✓ | ✓ | 352 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp-server-wporg-trac-staging.a8cai.workers.dev/mcp/chatgpt") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-server-wporg-trac-staging-a8cai-workers-dev-mcp-chatgpt # JSON