Niche
✓ Verifiedhttps://nicheangle.com/api/mcp ↗
Description
Editorial intelligence for creators and their agents. Most tools help you write, Niche helps you decide what's worth writing. It reads primary-source signal, discovers emerging stories, ranks the strongest angle, and turns that signal into publishable, platform-native content that's grounded in real sources, in your voice. 25 tools across discovery, drafting, render, and brand. Remote (Streamable HTTP), OAuth 2.1 + PAT.
What our measurements say
Niche is a remote MCP server published at nicheangle.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 656 ms, a delay an agent will notice. It exposes a broad tool surface of 25 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Some tools (e.g., niche_session_state) provide clear session tracking capabilities.
- Brand and voice profile tools (niche_brand_profile_set, niche_voice_profile_ingest) address customization needs.
Weaknesses
- Tool names like 'niche_draft_direct' and 'niche_draft_create' are functionally similar but not clearly differentiated.
- Descriptions are frequently truncated (e.g., 'clust' in niche_signal_scan) or overly technical without use-case context.
- Parameter schemas and required/optional fields are not explicitly defined in tool descriptions.
- Multiple tools (e.g., niche_draft_revise, niche_add_output) handle draft modifications without clear boundaries.
niche_signal_scan— Description truncated mid-sentence ('clust')niche_draft_direct— Functionally similar to niche_draft_create but lacks clear differentiationniche_draft_revise— Parameter fields listed ambiguously without required/optional clarificationniche_render_image_card— Scope options ('full', 'recomposite') not clearly explained in descriptionniche_session_export— Output format ('standard editorial-calendar shape') lacks concrete examples
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — Era changed from 'auth-gated' to 'legacy'; compliance score set to 100 · Stability confirmed, but initial compliance score was undefined
- 2026-09-11T05:44:28.819Z — Compliance score stabilized at 100 · Consistent performance achieved, no further changes detected
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 243ms → warm 202ms (penalty 41ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 0.1.0
- Supported versions: — → 2025-03-26
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/sailquery-niche)<a href="https://mcpmetrics.io/servers/sailquery-niche"><img src="https://mcpmetrics.io/badge/sailquery/niche/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see