Editorial intelligence for creators and their agents — discover the stories wort
Editorial intelligence for creators and their agents — discover the stories worth writing about, rank the angle, draft from sources. A remote MCP server.
active Production-safe Score 90/100 http auth required
At a glance
| Endpoint | https://api.nicheangle.com/mcp |
|---|---|
| Source | https://github.com/sailquery/niche-mcp |
| Transport | http |
| Tools | 8 |
| Auth | bearer (bearer) |
| First seen | 2026-06-15 21:13:39 |
| Last checked | 2026-11-17 21:47:13 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 384 / 610 ms |
| Last successful check | 2026-11-17 21:47:13 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (8)
niche_signal_scan— Scan a niche you describe, right now (Pro). Returns a ranked, sourced slate of the stories people in that field are talking about, with sourniche_intelligence_query— Ask an analyst-shaped question over a fresh scan of a niche (Pro): 'the biggest developments this week', 'what is emerging', 'where money isniche_session_state— Read the current state of a scan: status, the ranked stories with their sources and source information, and any angles already proposed. Polniche_angle_propose— Angles on one story (Pro): up to a few distinct stances a reader could take, each with a hook, the take, and the sources that support it. Paniche_list_sessions— List your recent scans: id, the niche you described, status and timestamps. Use it to find a session_id you no longer have.niche_session_cancel— Cancel a scan that is still running.niche_whoami— Orient in one read-only call: your plan (Free or Pro), the tools this server serves, and the endpoint. Assistant access requires Pro. Call iniche_feed_read— Read the latest or a dated briefing for a niche: stories, reporting dates, source links, why each story matters, and new or continuing statu
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:47:13 | ✓ | ✓ | 330 ms | 91 | active |
| 2026-11-17 21:32:09 | ✓ | ✓ | 255 ms | 94 | active |
| 2026-11-17 21:16:58 | ✓ | ✓ | 327 ms | 91 | active |
| 2026-11-17 21:01:55 | ✓ | ✓ | 348 ms | 91 | active |
| 2026-11-17 20:46:35 | ✓ | ✓ | 241 ms | 94 | active |
| 2026-11-17 20:31:34 | ✓ | ✓ | 409 ms | 91 | active |
| 2026-11-17 20:16:27 | ✓ | ✓ | 322 ms | 91 | active |
| 2026-11-17 20:00:39 | ✓ | ✓ | 456 ms | 91 | active |
| 2026-11-17 19:45:36 | ✓ | ✓ | 261 ms | 94 | active |
| 2026-11-17 19:30:29 | ✓ | ✓ | 252 ms | 94 | active |
| 2026-11-17 19:15:27 | ✓ | ✓ | 339 ms | 91 | active |
| 2026-11-17 18:59:32 | ✓ | ✓ | 428 ms | 91 | active |
| 2026-11-17 18:44:31 | ✓ | ✓ | 454 ms | 91 | active |
| 2026-11-17 18:29:30 | ✓ | ✓ | 282 ms | 94 | active |
| 2026-11-17 18:14:24 | ✓ | ✓ | 332 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.nicheangle.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-nicheangle-com-mcp # JSON