Fjord
MCPB · FJORD-MCP.MCPB
Local kanban boards, markdown notes and Git/GitHub/Azure DevOps work from the Fjord app.
Available components
Last scanned (12 hours ago)
Scores higher than 75% of MCPB servers
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT OR Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1787 tokens (~63/item across 28 items; 28 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 34% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 28 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 23 Oct 26 +1
- Stability: 0.00 → unverified ▼ security
- 22 Oct 26 37
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 23 Oct 2026 · Analysed mcpb/https://github.com/jhtjernsmo/fjord/releases/download/v0.2.32/fjord-mcp.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_note ~91
Add a markdown note — to a project, or to the global notespace if project is omitted. Link with [[Project]], [[#12]] (task) or [[Note title]].
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| folder | string | – | e.g. product/ideas |
| pinned | boolean | – | – |
| project | string | – | Project id or slug |
| title | string | yes | – |
No output schema declared.
No examples provided.
analyze_story ~140
Start a user story analysis for a task: creates a note from the user's own analysis template in the project's Analysis folder, linked to the task, and returns it with the task's context (title, description, acceptance criteria, risk, work item URL). If the task already has one, returns that instead (created = false). Fill in each section from the context with update_note (body replaces the whole note): keep the user's headings, their order and the [[#id]] link, and write in the language the user writes in. Leave a section's placeholder line if there's nothing to say rather than inventing facts.
| Name | Type | Req | Description |
|---|---|---|---|
| task | integer | yes | – |
No output schema declared.
No examples provided.
archive_task ~22
Archive a task (reversible).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
attach_file ~49
Copy a local file into Fjord and attach it to a project or task.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| project | string | yes | Project id or slug |
| task | integer | – | – |
No output schema declared.
No examples provided.
backlinks ~32
Notes that link to a project, task or note.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| kind | string | yes | – |
No output schema declared.
No examples provided.
complete_task ~37
Move a task to the project's done column (its Azure Boards work item follows when writing to Azure is on).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
create_project ~54
Create a project with default columns.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | #rrggbb |
| description | string | – | – |
| icon | string | – | Short glyph, e.g. >_ |
| name | string | yes | – |
No output schema declared.
No examples provided.
create_task ~113
Add a task to a project. Pass parent (a task id in the same project) to create a subtask; subtasks can't have subtasks.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Markdown |
| due | string | – | YYYY-MM-DD |
| parent | integer | – | Parent task id, to create a subtask |
| priority | integer | – | – |
| project | string | yes | Project id or slug |
| status | string | – | Column name or id (default: first) |
| title | string | yes | – |
No output schema declared.
No examples provided.
get_board ~27
Columns and active tasks of a project.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project id or slug |
No output schema declared.
No examples provided.
get_note ~33
Read a note: markdown body plus its [[links]] resolved to projects/tasks/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
get_task ~32
Read one task: its fields and markdown body, its subtasks and attached files.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
git_status ~31
Current branch, branches and recent commits of a project's repository.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project id or slug |
No output schema declared.
No examples provided.
import_azure ~41
Fetch work items assigned to the user in Azure Boards and create or refresh tasks in the mapped Fjord projects (mappings are set in Fjord's Settings).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
link_branch ~58
Link a task to a branch that already exists in the linked repository (or unlink with branch: null), so its pull requests show on the task. Doesn't check anything out.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string|null | yes | – |
| id | integer | yes | – |
No output schema declared.
No examples provided.
link_repo ~49
Link a project to the git repository at a local path (GitHub or Azure DevOps is detected from origin).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| project | string | yes | Project id or slug |
No output schema declared.
No examples provided.
list_new_imports ~64
Tasks imported from Azure Boards that no agent has analyzed yet, with their task and link. Analyze each one (update_task to append a short summary, acceptance criteria and suggested subtasks to the body; create_task for subtasks if useful), then call mark_analyzed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_notes ~58
List notes (without bodies; use get_note). project: only that project's notes; free_only: only notespace notes without a project; otherwise all.
| Name | Type | Req | Description |
|---|---|---|---|
| free_only | boolean | – | – |
| project | string | – | Project id or slug |
No output schema declared.
No examples provided.
list_projects ~23
List projects with progress counts.
| Name | Type | Req | Description |
|---|---|---|---|
| include_archived | boolean | – | – |
No output schema declared.
No examples provided.
list_pull_requests ~43
GitHub pull requests of a project with CI state and linked tasks; moves tasks of merged PRs to done.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project id or slug |
No output schema declared.
No examples provided.
mark_analyzed ~34
Mark an imported task as analyzed so it no longer shows up in list_new_imports.
| Name | Type | Req | Description |
|---|---|---|---|
| task | integer | yes | – |
No output schema declared.
No examples provided.
move_task ~103
Move a task to another column, or to another project (its subtasks and files go with it; without status it lands in the column with the same name). With "Send state changes to Azure" on, a column move also sets the state of the task's Azure Boards work item to the column's name.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| project | string | – | Name or slug of the project to move it to |
| status | string | – | – |
No output schema declared.
No examples provided.
open_pull_request ~42
Push a task's branch and open a GitHub pull request using the task title and description.
| Name | Type | Req | Description |
|---|---|---|---|
| draft | boolean | – | – |
| id | integer | yes | – |
No output schema declared.
No examples provided.
recent_activity ~34
Recent changes, optionally for one project.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| project | string | – | Project id or slug |
No output schema declared.
No examples provided.
search ~25
Full-text search across tasks, notes and file names.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
set_task_pending ~80
Mark a task pending (waiting on someone else, e.g. a reply from the client) or not. It stays in its column. With "Send state changes to Azure" on, a task from Azure Boards moves its work item to the pending state too.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| pending | boolean | yes | false to stop pending |
No output schema declared.
No examples provided.
start_branch ~96
Check out (or create) the git branch for a task, named <type>/<id>-<title>, e.g. feat/12-add-login. type is feat, fix, chore, docs, refactor, test, perf, ci or hotfix (guessed from the task if omitted). Moves the task to in progress when auto-move is on.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
update_note ~111
Edit a note. Only given fields change. append adds text to the end of the body. project: id/slug to move into a project, null to move to the notespace.
| Name | Type | Req | Description |
|---|---|---|---|
| append | string | – | – |
| body | string | – | Replaces the whole body |
| folder | string | – | e.g. product/ideas; empty = none |
| id | integer | yes | – |
| pinned | boolean | – | – |
| project | string|null | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
update_task ~110
Edit a task. Pass due: null to clear the due date. parent: a task id in the same project makes it a subtask of that task (it can't have subtasks of its own); null makes it a regular task.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| due | string|null | – | – |
| id | integer | yes | – |
| parent | integer|null | – | Parent task id, or null for a regular task |
| priority | integer | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
How do I install the Fjord MCP server?
Fjord ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 523464bc4fff7493861c9d6874d500866947c8a7b4ff63a132b8d500cba7cc23; the commands to do that are on this page. If it does not match, do not open it.
mcpb · fjord-mcp.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
523464bc4fff7493861c9d6874d500866947c8a7b4ff63a132b8d500cba7cc23
macOS / Linux
echo "523464bc4fff7493861c9d6874d500866947c8a7b4ff63a132b8d500cba7cc23 fjord-mcp.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\fjord-mcp.mcpb).Hash -eq "523464bc4fff7493861c9d6874d500866947c8a7b4ff63a132b8d500cba7cc23"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the Fjord MCP server?
Fjord is an MCP server listed in the public MCP registry as io.github.jhtjernsmo/fjord. Local kanban boards, markdown notes and Git/GitHub/Azure DevOps work from the Fjord app. This page covers its MCPB bundle (https://github.com/jhtjernsmo/fjord/releases/download/v0.2.32/fjord-mcp.mcpb).
Is the Fjord MCP server safe to use?
Fjord scores 38 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 Fjord MCP server expose?
Fjord exposes 28 tools: list_projects, get_board, create_project, create_task, get_task, and 23 more. Their descriptions and schemas cost roughly 1,632 tokens of context every time the server is loaded.
What licence is the Fjord MCP server under?
Fjord declares the MIT OR Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.