# Fiskmas (remote · mcp.fiskmas.dev)

Hosting for AI agents: your AI client deploys Docker apps to live HTTPS URLs over MCP.

- Trust score: 59/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.fiskmas.dev`: 59/100 (this document), [markdown](https://verifymcp.io/servers/dev-fiskmas-fiskmas/mcp.md), [page](https://verifymcp.io/servers/dev-fiskmas-fiskmas/mcp)

## Channel facts

- Endpoint: `https://mcp.fiskmas.dev/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 21 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1277 tokens (~58/item across 22 items; 21 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_account" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Fiskmas MCP server?

Fiskmas is a hosted endpoint at https://mcp.fiskmas.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-fiskmas-fiskmas 'https://mcp.fiskmas.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-fiskmas-fiskmas": {
      "url": "https://mcp.fiskmas.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-fiskmas-fiskmas": {
      "type": "http",
      "url": "https://mcp.fiskmas.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-fiskmas-fiskmas]
url = "https://mcp.fiskmas.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-fiskmas-fiskmas": {
      "type": "remote",
      "url": "https://mcp.fiskmas.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-fiskmas-fiskmas --url 'https://mcp.fiskmas.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-fiskmas-fiskmas:
    url: "https://mcp.fiskmas.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-fiskmas-fiskmas": {
      "Transport": "http",
      "Url": "https://mcp.fiskmas.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-fiskmas-fiskmas -t streamable-http -u 'https://mcp.fiskmas.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-fiskmas-fiskmas": {
      "type": "http",
      "url": "https://mcp.fiskmas.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 58, +1)

- [functional regression] Schema quality: 1128 → 1277
- [functional] New tool “reissue_token”

### 2026-09-16 (score 57, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-15 (score 56)

First indexed and scored.

## MCP tools (21)

### `whoami` (~92 tokens)

Return the identity of the current token holder (account + provider) plus its subscription plan (free | plus) and the plan's limits: max running projects, per-project memory/CPU caps, log windows, and the project-database fair-use guide. Free plans include an upgrade_url for Plus ($9.99/mo: 5 projects, 256 MB / 0.5 CPU per project, always-on).

### `create_account` (~104 tokens)

Start onboarding: require an email, create a pending account, and email a human verify link. Does NOT return an API token. The human must click the link; the verify page shows the token once. Then configure Authorization: Bearer <token> on this MCP client (also docker login -u <token> registry.fiskmas.dev). If you already have a token, call whoami instead.

Input parameters:

- `display_name` (string)
- `email` (string, required)

### `account_status` (~40 tokens)

Poll onboarding state for an email (pending | active | unknown). Use after create_account while waiting for the human to verify.

Input parameters:

- `email` (string, required)

### `reissue_token` (~149 tokens)

Re-issue the API token for an existing account. Provide the email the account was registered with; Fiskmås emails a fresh one-time verify link to that address. The human clicks it; the verify page shows the new token once (old tokens are revoked immediately). This is the self-service recovery path when a token was lost, rotated, or is being rejected as "invalid or expired". It does not create a new account — for a brand-new account use create_account. Rate-limited: a few requests per hour per email. If you already have a valid token and just want to rotate it, use rotate_token (follows in a later release).

Input parameters:

- `email` (string, required)

### `delete_account` (~43 tokens)

Delete the caller's account. Stops and removes all projects (containers, routes, MariaDB) first, then deletes the account. Refuses to leave orphaned runtimes.

### `create_project` (~99 tokens)

Create a project and reserve <slug>-app.fiskmas.dev. Slug must match ^[a-z0-9][a-z0-9-]{1,48}$ and is not reserved. Subject to the plan's running-project quota (Free: 1, Plus: 5) — on quota the error tells the human how to upgrade or free a slot.

Input parameters:

- `name` (string)
- `slug` (string)

### `list_projects` (~18 tokens)

List the caller's projects with status and URL.

### `get_project` (~24 tokens)

Fetch a single project by id or slug.

Input parameters:

- `project` (string)

### `delete_project` (~27 tokens)

Stop and delete a project (free the slug after quarantine).

Input parameters:

- `project` (string)

### `set_env` (~37 tokens)

Set environment variables on a project. Requires a restart before they take effect.

Input parameters:

- `env` (object)
- `project` (string)

### `list_env` (~29 tokens)

List a project's env keys with masked values (never returns full secrets).

Input parameters:

- `project` (string)

### `deploy_project` (~135 tokens)

Pull an image by digest and run one container with the plan's cpu/memory caps (Free: 128 MB / 0.2 CPU, Plus: 256 MB / 0.5 CPU). Only registry.fiskmas.dev images are accepted. Rate-limited to 1 deploy per 5 minutes per account (429 with a retry-seconds hint); use restart_project for a transient crash - it does not count against the limit. Re-deploying a running project is always allowed; starting a second one on Free is blocked until one stops.

Input parameters:

- `image` (string)
- `project` (string)

### `start_project` (~21 tokens)

Start a stopped project's container.

Input parameters:

- `project` (string)

### `stop_project` (~25 tokens)

Stop a running project's container (keep the image).

Input parameters:

- `project` (string)

### `restart_project` (~21 tokens)

Restart a running project's container.

Input parameters:

- `project` (string)

### `get_status` (~29 tokens)

Return project status, url, image digest, and last deploy error.

Input parameters:

- `project` (string)

### `get_logs` (~96 tokens)

Return recent container log lines. `tail` = line count (plan default 200; plan max 2000), `since` = time window in seconds (plan window: free 24 h, plus 7 d — logs are live-pod streams, not stored history). When both are given, `since` wins.

Input parameters:

- `project` (string)
- `since` (number)
- `tail` (number)

### `get_stats` (~98 tokens)

Account-wide or per-project stats for debugging: live CPU/mem vs the plan caps (Free: 128 MB / 0.2 CPU, Plus: 256 MB / 0.5 CPU) and deploy history. Omit `project` for all of the caller's projects; pass a project id or slug for a single project. The account rollup also reports the plan and per-project caps.

Input parameters:

- `project` (string)

### `send_feedback` (~136 tokens)

Report a problem with the Fiskmås toolset so it can be fixed. Use it when a tool errored or misbehaved, you got stuck and can't proceed, or the instructions/skill were unclear. Do NOT use it for praise. kind=bug means it broke, kind=suggestion means it was unclear or could be better, kind=other is anything else that didn't work. Name the `tool` and, if relevant, the `project`. At most one call per session.

Input parameters:

- `kind` (string, required)
- `message` (string, required)
- `project` (string)
- `tool` (string)

### `list_skills` (~18 tokens)

List the platform skills available to the caller.

### `get_skill` (~25 tokens)

Return the bytes of a platform skill by name.

Input parameters:

- `name` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-fiskmas-fiskmas/mcp#diagnostics

## Score history

- 2026-09-20: 59
- 2026-09-19: 58
- 2026-09-18: 58
- 2026-09-17: 58
- 2026-09-16: 57
- 2026-09-15: 56

## Common questions

### What is the Fiskmas MCP server?

Fiskmas is an MCP server listed in the public MCP registry as dev.fiskmas/fiskmas. Hosting for AI agents: your AI client deploys Docker apps to live HTTPS URLs over MCP. This page covers its hosted endpoint (https://mcp.fiskmas.dev/mcp).

### Is the Fiskmas MCP server safe to use?

Fiskmas scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Fiskmas MCP server expose?

Fiskmas exposes 21 tools: whoami, create_account, account_status, reissue_token, delete_account, and 16 more. Their descriptions and schemas cost roughly 1,266 tokens of context every time the server is loaded.

### Does the Fiskmas MCP server require authentication?

No. We connected to Fiskmas without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Fiskmas MCP server still maintained?

Fiskmas is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.fiskmas.dev/mcp
- Authorisation metadata: https://mcp.fiskmas.dev/.well-known/oauth-protected-resource/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-fiskmas-fiskmas/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-fiskmas-fiskmas/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-fiskmas-fiskmas/mcp