Skip to content
frisian-mcp logo

frisian-mcp MCP server

Which servers in the official MCP registry are frisian-mcp's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-15

← Back to frisian-mcp

Whose server it is
  • Registry namecom.frisian-mcp/djangoverified in the MCP registry

The registry name sits under frisian-mcp.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-15
  • Stateanswerschecked 2026-10-15
  • Tools4
  • Server calls itselffrisian-mcp
  • Server version1.1.0
  • Protocol version2025-11-25

On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 277 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: group server tools so agents discover them progressively; paginate large list responses so agents control context cost; run stress and soak tests on MCP servers.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 4 of 4 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-19
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • What an agent can do with it0 of 3 use cases
  • Use6 GitHub stars
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer277 ms
  • Space in an agent's context≈ 1,298 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsC · 67 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 4
  • Not saying whether it only reads or can destroy: 4 of 4

What an agent can do with it

  • cannot · group server tools so agents discover them progressively
  • cannot · paginate large list responses so agents control context cost
  • cannot · run stress and soak tests on MCP servers

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-15
  • docs

    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

    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)…

  • install

    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…

  • troubleshooting

    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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "django": {
      "type": "http",
      "url": "https://mcp.frisian-mcp.com/mcp/"
    }
  }
}

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.frisian-mcp.com/mcp/ as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.