Skip to content

Nifra docs MCP server

io.github.nifrajs/nifra-docsnifrajsstreamable-httpv5.17.0Scanned

Nifra docs, runnable examples, and API types as an MCP server for any AI assistant.

7 tools: 4 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 4 write, 3 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 0
  • 3 findings, 1 high

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Nifra docs MCP server can do

The Nifra docs MCP server is published by the GitHub account nifrajs. It has 7 tools. It can create or change data (4 tools: nifra_types, nifra_learn, nifra_frontend and nifra_gallery), but cannot delete data. 3 tools only read.

2 tools read private data (nifra_docs and nifra_example); 1 tool brings in text other people can write (nifra_docs).

The fixed checks matched 3 findings, 1 of them high severity (annotation-conflict and sensitive-path). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 5.17.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 4Claude Code: ask
  • nifra_frontendDiagnose a client-side Nifra problem by symptom across every adapter (React, Preact, Solid, Vue, Svelte, and vanilla).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Diagnose a client-side Nifra problem by symptom across every adapter (React, Preact, Solid, Vue, Svelte, and vanilla). Returns the likely cause, a concrete fix, and how to verify it. Covers the Nifra server/client seam, hydration mismatches, duplicated framework runtimes, loader-data typing, and adapter-specific reactivity guidance. Call with no args for the index; pass `symptom` (e.g. "hydration mismatch", "value stopped updating") and/or `adapter` to filter.

    Annotations the server declares

    • title: Frontend footgun guidance
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • nifra_learnWalk the guided path to build a nifra app end to end - an ORDERED sequence (create → page route → loader → typed API → typed client → auth → background jobs → deploy), not the rand…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Walk the guided path to build a nifra app end to end - an ORDERED sequence (create → page route → loader → typed API → typed client → auth → background jobs → deploy), not the random-access search of nifra_docs/nifra_example. Call with no args for the step index; pass `step: N` for that step's goal, how to do it (which tool emits the correct artifact), and how to verify it. Use it when scaffolding a new app or learning nifra's flow - each step composes the other nifra_* tools.

    Annotations the server declares

    • title: Guided nifra learning path
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • nifra_typesGet the exact TypeScript declaration of any exported @nifrajs/* symbol - interface, type, class, function, or const.1 finding

    Why it is in this group

    • The name "nifra_types" says "type": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "nifra_types" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "nifra_types" says "type": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Get the exact TypeScript declaration of any exported @nifrajs/* symbol - interface, type, class, function, or const. Each signature is generated from the package's built .d.ts and returns the complete declaration rather than prose. Pass `name` for an exact symbol (e.g. "RateLimitStore", "RouteSchema", "Context", "rateLimit"); pass `query` to search by keyword; omit both for the per-package index of names. A `name` lookup is always the complete declaration; a `query` returns a one-line summary plus the signature, collapsing an oversized body - pass `full: true` to override.

    Annotations the server declares

    • title: Look up nifra API types
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • nifra_docsSearch nifra's framework documentation and get back ONLY the matching sections - auth, uploads, ISR, WebSockets, loaders, deployment, anything.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.

    What it can reach

    • private-dataThe name "nifra_docs" says "doc": it reads documents.
    • untrusted-inputThe description's first sentence says "search" and "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Search nifra's framework documentation and get back ONLY the matching sections - auth, uploads, ISR, WebSockets, loaders, deployment, anything. Call with no query for the cheap section index; pass query (e.g. "isr revalidate") for the top matching sections. Use this instead of reading llms-full.txt (~150 KB) whole. For the EXACT TypeScript of a type/interface/function, call nifra_types instead (don't read .d.ts files).

    Annotations the server declares

    • title: Search nifra docs
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • nifra_exampleGet a verified, copy-pasteable Nifra code example for a task - auth route, file upload, ISR page, loader/action, typed client, SSE, deployment, and more.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "file": it reads files.
    Description, as the server wrote it
    Get a verified, copy-pasteable Nifra code example for a task - auth route, file upload, ISR page, loader/action, typed client, SSE, deployment, and more. Every snippet is typechecked against the installed Nifra version, so it compiles as-is. Returns code as text for direct use. Call with no query for the grouped index; pass query (e.g. "protected route", "upload", "isr revalidate") for matching snippets.

    Annotations the server declares

    • title: Get a verified nifra example
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • nifra_runtimeExplain a behavior that differs between Bun, Node, Deno and Cloudflare Workers by symptom.1 finding

    Why it is in this group

    • The description's first verb is "explain": a word for reading.

    Findings

    • High

      The description refers to ".env".

      Matched text

      description: "...engine error messages, recursion depth, .env loading, and runtime-specific APIs. Ret..."

      What this check looks for
    Description, as the server wrote it
    Explain a behavior that differs between Bun, Node, Deno and Cloudflare Workers by symptom. These are runtime behaviors, not Nifra's: request-target and Host handling, pipelining, JSON content-type, engine error messages, recursion depth, .env loading, and runtime-specific APIs. Returns what each runtime does, the fix (and the Nifra option that decides it when there is one), how to verify it, and the versions it was measured on. Call with no args for the index; pass `symptom` (e.g. "path guard skipped", "env var undefined") and/or `runtime` to filter.

    Annotations the server declares

    • title: Runtime differences
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:08 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.nifra.dev: tools/list returned 7 tools to an anonymous client, including nifra_types (write), nifra_learn (write), nifra_frontend (write), nifra_gallery (write)

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • HTTP status of an anonymous initialize: 530 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 4
    • Protocol version: none to 2025-06-18

Findings

Matches of fixed checks, with the text they matched.

1 high2 warn
  • The description refers to ".env".

    Matched text

    description: "...engine error messages, recursion depth, .env loading, and runtime-specific APIs. Ret..."

    What this check looks for
  • The server marks "nifra_types" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "nifra_types" says "type": a word for a change.

    What this check looks for
  • The server marks "nifra_gallery" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added.+1 addedView diff
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 530 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 4 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 530 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 4
    • Protocol version: none to 2025-06-18

Install

Pinned to version 5.17.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http nifra-docs https://mcp.nifra.dev
claude mcp add --transport http nifra-docs https://mcp.nifra.dev

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__nifra-docs__nifra_docs",
      "mcp__nifra-docs__nifra_example",
      "mcp__nifra-docs__nifra_runtime"
    ],
    "ask": [
      "mcp__nifra-docs__nifra_types",
      "mcp__nifra-docs__nifra_learn",
      "mcp__nifra-docs__nifra_frontend",
      "mcp__nifra-docs__nifra_gallery"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nifra-docs. Review it before you use it.

Capability tags behind 2 rules
  • mcp__nifra-docs__nifra_docs private-data, untrusted-input
  • mcp__nifra-docs__nifra_example private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.nifrajs/nifra-docs/verify?hash=7dbce9a09d2c39f0dda6e111e7edbded1564898edb89669e0f6d0e42a4b50b92" | jq -e '.changed == false'

Pinned hash 7dbce9a09d2c, from Nov 21, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.nifrajs/nifra-docs/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.nifrajs/nifra-docs
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.nifrajs/nifra-docs.svg)](https://radar.anlyon.com/servers/io.github.nifrajs/nifra-docs)

Source: MCP Registry · repository. Synced Nov 21, 2026, 16:18 UTC.

Nifra docs MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Nifra docs MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 3 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Nifra docs MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Nifra docs MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Nifra docs MCP server have?

7 tools: 4 write, 3 read. nifra_types, nifra_learn, nifra_frontend, nifra_gallery, nifra_docs, nifra_example and nifra_runtime.

Does the Nifra docs MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Nifra docs MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Nifra docs MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.