Nifra docs
REMOTE · MCP.NIFRA.DEV · SCANNED AUG 3
Nifra docs, runnable examples, and API types as an MCP server for any AI assistant.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 894 tokens (~149/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 1 day we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.nifra.dev
claude mcp add --transport http nifrajs-nifra-docs https://mcp.nifra.dev/
[mcp_servers.nifrajs-nifra-docs] url = "https://mcp.nifra.dev/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nifrajs-nifra-docs": {
"type": "remote",
"url": "https://mcp.nifra.dev/",
"enabled": true
}
}
} openclaw mcp add nifrajs-nifra-docs --url https://mcp.nifra.dev/ --transport streamable-http
mcp_servers:
nifrajs-nifra-docs:
url: "https://mcp.nifra.dev/" {
"mcpServers": {
"nifrajs-nifra-docs": {
"type": "http",
"url": "https://mcp.nifra.dev/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 0
- Stability: unverified → fail ▼ security
- Tool “nifra_examples_app” was removed ▼ security
- Tool “nifra_example” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- Server version: 2.8.0 → 2.8.1 functional
- Server version: 2.6.1 → 2.8.0 functional
- Server version: 2.5.0 → 2.6.1 functional
- New tool “nifra_gallery” functional
- 2 Aug 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.nifra.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nifra.dev | CN=WE1,O=Google Trust Services,C=US | 19 Jun 2026 | 17 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | fbcb440e259c950913f4b7cea8dbf1ab |
| SANs: nifra.dev, *.nifra.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of mcp.nifra.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| nifra.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.nifra.dev | Verified | 200 | |
| http (plaintext) | http://mcp.nifra.dev | HTTPS enforced | 301 | https://mcp.nifra.dev/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
nifra_docs ~142
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max sections to return (default 3, max 5). |
| query | string | — | Keywords to match against doc sections (omit for the index). |
No output schema declared.
No examples provided.
nifra_example ~172
Get a VERIFIED, copy-pasteable nifra code example for a task - auth route, file upload, ISR page, loader/action, typed client, SSE, deployment, etc. Every snippet is typechecked against the installed nifra version, so it compiles as-is. PREFER THIS over writing nifra code from memory (training data drifts). Returns code as TEXT for direct use; to visually browse the whole example set instead, use nifra_gallery. Call with no query for the grouped index; pass query (e.g. "protected route", "upload", "isr revalidate") for matching snippets.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max examples to return (default 3, max 5). |
| query | string | — | What you want an example of (omit for the index). |
No output schema declared.
No examples provided.
nifra_gallery ~79
Open an interactive, filterable gallery of ALL of nifra's verified code examples (MCP Apps widget) - for browsing and discovering what exists. NOT for fetching one snippet as text: use nifra_example for that. Pass query to pre-filter; the widget also filters client-side.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | — | Pre-filter examples by keyword. |
No output schema declared.
No examples provided.
nifra_learn ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| step | number | — | 1-based step number to expand (omit for the index). |
No output schema declared.
No examples provided.
nifra_types ~286
Get the EXACT TypeScript declaration of any exported @nifrajs/* symbol - interface, type, class, function, const. Each signature is generated from the package's built .d.ts, so it is the LITERAL declaration: complete, authoritative, never prose and never truncated. THIS IS THE SOURCE OF TRUTH for nifra's types - do NOT read node_modules/@nifrajs/**/*.d.ts; call this instead. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | — | Query mode only: return whole declarations instead of collapsed ones. Off by default - a search is for picking a symbol, and one match can be tens of thousands of characters. |
| limit | number | — | Max results for a query/search (default 5, max 8). |
| name | string | — | Exact symbol name - returns its literal declaration (e.g. RateLimitStore). |
| query | string | — | Keyword search over names + signatures (when you don't know the exact name). |
No output schema declared.
No examples provided.