Clients cache both the credentials and the tool list at connect time, so a new token or a new tool only appears after a restart or a new thread — and `niche_whoami` will enumerate what you are missing. The claim worth checking is the grounding: every response ships a source-faithfulness score and an ungrounded-claim list, so you can see what is not backed rather than take it on trust. Publishing is a dry run unless you say otherwise.
An editorial intelligence server. It reads primary-source signal, surfaces emerging stories in a subject area, ranks the strongest angle, and carries that through to a draft and the visuals — grounded in real sources rather than generated from the model's own recall.
- 25 tools. Discovery: `niche_signal_scan` returns a ranked story slate with provenance, `niche_intelligence_query` answers analyst-shaped questions with narratives and patterns, `niche_session_state` polls a run, and `niche_angle_propose` ranks the angles worth publishing
- Drafting: `niche_draft_create`, `niche_draft_revise` and `niche_draft_publish`, which dry-runs by default, plus `niche_draft_direct` to skip research and write from your own take or a URL
- Rendering: `niche_render_image_card`, `niche_render_reel`, `niche_attach_image` and `niche_reuse_asset`, with four background modes — `photo`, `design`, `svg` and `brand_color`
- Brand and voice profiles, a brand kit ingest with guided setup, and session operations — list, revert, cancel, export
- `niche_whoami` returns the full tool catalogue with the live count, plus your plan, credit balance, the capability map and brand state, in one read-only call
- Every response carries a trust block: verifier audit, source-faithfulness score, the list of ungrounded claims, and source-diversity and recency checks
A remote server at `https://api.nicheangle.com/mcp`, version 1.4.0, with nothing to install. Claude Desktop and Claude Code add it as an HTTP connector and sign in over OAuth. For headless or scripted use, issue a Personal Access Token in your account settings — it starts with `niche_sk_` — and pass it as a bearer token; in Codex, `bearer_token_env_var` takes the name of the environment variable holding it, not the token itself. Discovery metadata is published under `/.well-known` so compliant clients can self-configure.
One command — npx -y mcp-remote https://api.nicheangle.com/mcp