Skip to content

Frisian MCP (Django)

com.frisian-mcp/djangofrisian-mcp.comstreamable-httpv1.0.12Scanned

Your DRF API as MCP tools — 1,800 endpoints become 16 dispatchers, permissioned by Django.

4 tools: 4 change things.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the Frisian MCP (Django) can do

The Frisian MCP (Django) is published by frisian-mcp.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (4 tools: docs, demo, install and troubleshooting), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.0.12.

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.

4 tools

Changes things 4Claude Code: ask
  • demoLive working demo of frisian-mcp.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.
    Description, as the server wrote it
    Live working demo of frisian-mcp. Three capability groups: crm (contacts, companies, deals, tasks, memos), ops (automation, infrastructure, notifications, security, compliance), platform (analytics, data, reporting, integrations, users). All reads and writes are real and persistent.
  • docsStart here — frisian-mcp documentation and server guide.No findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    Description, as the server wrote it
    Start here — frisian-mcp documentation and server guide. Actions: about (server identity and links), getting_started (step-by-step adoption guide), integrations (Django/DRF config reference), security (auth model, OAuth, API keys, tiers), demo (explore the live demo endpoints), documents (browse all documentation articles), rag (semantic and full-text doc search).
  • installInstallation guides for frisian-mcp integrations (Django framework tier).No findings

    Why it is in this group

    • The name "install" says "install": a word for a change.
    Description, as the server wrote it
    Installation guides for frisian-mcp integrations (Django framework tier). Actions: nautobot, netbox, paperless, edx. Each action returns the files changed to make the integration work, organised by version. Pass query for semantic search within the section.
  • troubleshootingTroubleshooting guides for frisian-mcp integrations (Django framework tier).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.
    Description, as the server wrote it
    Troubleshooting guides for frisian-mcp integrations (Django framework tier). Actions: nautobot, netbox, paperless, edx. Each action returns diagnostic guides and relevant files for that integration. Pass query for semantic search within the section.

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 private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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, 18:38 UTC, unchanged since Oct 22, 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-11-25
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.frisian-mcp.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://mcp.frisian-mcp.com
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • 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.frisian-mcp.com/mcp/: tools/list returned 4 tools to an anonymous client, including docs (write), demo (write), install (write), troubleshooting (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http django https://mcp.frisian-mcp.com/mcp/
claude mcp add --transport http django https://mcp.frisian-mcp.com/mcp/

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": [],
    "ask": [
      "mcp__django__docs",
      "mcp__django__demo",
      "mcp__django__install",
      "mcp__django__troubleshooting"
    ],
    "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 django. Review it before you use it.

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/com.frisian-mcp/django/verify?hash=88135554276b987dbf7174915327ef04cc33c1cedc85eea1f90c6d5d11e1b55e" | jq -e '.changed == false'

Pinned hash 88135554276b, from Nov 10, 2026, 16:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.frisian-mcp/django/changes.xml

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

Badge

Anlyon Radar badge for com.frisian-mcp/django
[![Anlyon Radar](https://radar.anlyon.com/badge/com.frisian-mcp/django.svg)](https://radar.anlyon.com/servers/com.frisian-mcp/django)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:55 UTC.

Frisian MCP (Django): questions and answers

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

Is the Frisian MCP (Django) safe?

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

Can the Frisian MCP (Django) delete data?

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

Can the Frisian MCP (Django) 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 Frisian MCP (Django) have?

4 tools: 4 write. docs, demo, install and troubleshooting.

Does the Frisian MCP (Django) need sign-in or OAuth?

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

Does the Frisian MCP (Django) send data to outside services?

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

Has the Frisian MCP (Django) changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.