Public read-only MCP server for CourierPR, a press release wire: browse desks, s
Public read-only MCP server for CourierPR, a press release wire: browse desks, search and read published press releases.
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://courierpr.com/api/mcp |
|---|---|
| Source | https://github.com/aitrainingdatabroker/courierpr-mcp-server |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-11-10 19:51:50 |
| Last checked | 2026-11-17 21:46:09 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 286 / 460 ms |
| Last successful check | 2026-11-17 21:46:09 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
list_desks— The six newsroom desks and the twenty categories under them, with slugs and links. Use it to resolve a topic the user named ('tech', 'healthlatest_releases— The newest published press releases, optionally within one desk or one category. Use it for 'what is new in tech', 'latest funding announcemsearch_releases— Full-text search over every published press release (title and body), optionally within one category. Use it when the user names a company,get_release— One published press release by slug (the last part of its URL) or by its full courierpr.com URL: title, company, category, dateline, date, thow_to_file— What filing a release on CourierPR involves: what is accepted (the press code) and the links to file, for agencies and for journalists. Usesearch— Connector-style search over published press releases. Returns ids for fetch. Prefer search_releases when you can filter by category.fetch— Connector-style fetch of one press release by the id from search. Same summary as get_release.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:46:09 | ✓ | ✓ | 465 ms | 91 | active |
| 2026-11-17 21:31:03 | ✓ | ✓ | 236 ms | 94 | active |
| 2026-11-17 21:15:52 | ✓ | ✓ | 446 ms | 91 | active |
| 2026-11-17 21:00:37 | ✓ | ✓ | 417 ms | 91 | active |
| 2026-11-17 20:45:35 | ✓ | ✓ | 408 ms | 91 | active |
| 2026-11-17 20:30:33 | ✓ | ✓ | 451 ms | 91 | active |
| 2026-11-17 20:15:25 | ✓ | ✓ | 258 ms | 94 | active |
| 2026-11-17 19:59:21 | ✓ | ✓ | 404 ms | 91 | active |
| 2026-11-17 19:44:14 | ✓ | ✓ | 450 ms | 91 | active |
| 2026-11-17 19:29:12 | ✓ | ✓ | 389 ms | 91 | active |
| 2026-11-17 19:14:10 | ✓ | ✓ | 202 ms | 94 | active |
| 2026-11-17 18:58:17 | ✓ | ✓ | 387 ms | 91 | active |
| 2026-11-17 18:43:13 | ✓ | ✓ | 245 ms | 94 | active |
| 2026-11-17 18:28:11 | ✓ | ✓ | 225 ms | 94 | active |
| 2026-11-17 18:13:09 | ✓ | ✓ | 260 ms | 94 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://courierpr.com/api/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/courierpr-com-api-mcp # JSON