List your agent

Fiskmas

MCP server● Hosted · onlinev1.0.0

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

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: automate CI/CD pipelines.
All AI agents to automate CI/CD pipelines, ranked →

Similar tools

Listed for the same task: automate CI/CD pipelines

Reviews

No review yet. Used Fiskmas? Be the first to help others choose.

What it does

Fiskmas is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: devops automation. That makes it a candidate for tasks such as automate CI/CD pipelines or monitor production incidents.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.0
PriceNot in the registry
First seen26 Sept 2026
Last checked12h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)

Hosted endpoint

  • https://mcp.fiskmas.dev/mcp streamable-http

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "fiskmas": {
      "url": "https://mcp.fiskmas.dev/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 2d ago

ONLINE Fiskmas answered an MCP connection on 14 Nov 2026 and introduced itself as fiskmas-mcp 0.1.0 (MCP protocol 2025-06-18).

23 tools offered to AI assistants

  • whoami · 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. Fr
  • create_account · 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
  • account_status · Poll onboarding state for an email (pending | active | unknown). Use after create_account while waiting for the human to verify.
  • reissue_token · 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 re
  • delete_account · 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 · 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
  • list_projects · List the caller's projects with status and URL.
  • get_project · Fetch a single project by id or slug.
  • delete_project · Stop and delete a project. Its slug goes into quarantine for 7 days: you may re-use it immediately, other accounts get a 409 until it is freed.
  • set_env · Merge environment variables into a project (existing keys are kept). They take effect on the next deploy_project: a restart does NOT re-apply env. The platform-injected DATABASE_URL/MYSQL_* are protected: set_env rejects overriding them and
  • list_env · List a project's env keys with masked values (never returns full secrets).
  • deploy_project · Pull an image by digest and run one container with the plan's cpu/memory caps (Free: 256 MB / 0.2 CPU, Plus: 512 MB / 1 CPU). Only registry.fiskmas.dev images are accepted. Rate-limited to 1 deploy per 5 minutes per account (429 with a retr
Show 11 more
  • start_project · Start a stopped project's container. Waits until it is ready; a pod that fails to become ready returns a named error.
  • stop_project · Stop a running project's container (keep the image).
  • restart_project · Restart a running project's container. Recreates the pod, re-running the injected-DB resolver gate and the app's storage probes, and waits for readiness: a failed start returns a named error (e.g. an unresolvable DB host) and a plain retry
  • get_status · Return project status, url, image digest, and last deploy error.
  • get_logs · 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
  • get_stats · Account-wide or per-project stats for debugging: live CPU/mem vs the plan caps (Free: 256 MB / 0.2 CPU, Plus: 512 MB / 1 CPU) and deploy history. Omit `project` for all of the caller's projects; pass a project id or slug NaNalso returns `re
  • database_dump · Export the project's platform-provisioned database: starts a cluster-side dump Job in your own tenant namespace (mariadb-dump --single-transaction, zstd-compressed; gzip fallback) writing a compressed artifact to your tenant artifact store.
  • dump_status · Report one database_dump job: status pending|running|done|failed. When done, includes the artifact size/compression and the presigned download URL (expires ~24 h after the dump started; null once expired — request a new dump). When failed,
  • send_feedback · 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=suggest
  • list_skills · List the platform skills available to the caller.
  • get_skill · Return the bytes of a platform skill by name.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://mcp.fiskmas.dev/mcpDECLAREDSRC-001 Official MCP Registry12h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry12h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry12h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry12h ago
Version1.0.0DECLAREDSRC-001 Official MCP Registry12h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry12h ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Fiskmas? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor FiskmasLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Fiskmas?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/fiskmas?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/fiskmas/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Fiskmas

How do I connect Fiskmas?

Use the hosted endpoint https://mcp.fiskmas.dev/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Fiskmas need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does Fiskmas offer?

When Electra Index connected on 14 Nov 2026, it listed 23 tools: whoami, create_account, account_status, reissue_token, delete_account, create_project, list_projects, get_project and more. The full list is in "Live check" above.

Is Fiskmas online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.

What can I use Fiskmas for?

Based on its description, it is most relevant to: automate CI/CD pipelines, monitor production incidents.