Skip to content

MCP servers › io.github.anilcancakir › dowel

MCP server · registry snapshot 2026-11-19 · last checked 2026-11-19

dowel MCP server

Registry name io.github.anilcancakir/dowel

by anilcancakir · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

CLI framework and stdio MCP server for Flutter: scaffolding, hot reload, REPL, codegen. — the publisher's description

4 of 5 record checks metversion 1.1.0Dart

Summary

io.github.anilcancakir/dowel is an MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the GitHub account anilcancakir. Its linked repository, github.com/anilcancakir/dowel, belongs to the same GitHub account.

Record checks

4 of 5 record checks met · 4 do not apply

  • not met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 2 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Repository
public
Last tested
not tested

Tool list

Not read: The registry entry declares no package and no remote endpoint, so there is nothing to run. So there is no tool-list size and no result from the three APIs.

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
1.1.0, published 2026-11-18 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
Version history
4 versions listed, 2026-11-16 to 2026-11-18; 4 in the 90 days before the 2026-11-19 snapshot.
Most recent 4 versions
  • 1.1.0 · 2026-11-18
  • 1.0.5 · 2026-11-18
  • 1.0.4 · 2026-11-16
  • 1.0.3 · 2026-11-16
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.5 (published 2026-11-18) → 1.1.0 (published 2026-11-18), between the registry lists of 2026-11-18 and 2026-11-19.

The publisher’s GitHub release note for 1.1.0, published 2026-11-18.

Read the release note (the publisher’s text, shown as plain text)
### Added

- **`test:bundle` groups the test suite into a few `flutter test` entries.** `flutter test` compiles every test file on its own; `dowel test:bundle` writes `test/bundle_<n>.g.dart` entries that import every `*_test.dart` under `test/` and run each inside a group named after its path, dealt heaviest first (by line count) onto `--shards=N` entries (default 3), with files carrying a `// shard: alone` line in `test/bundle_alone.g.dart`. `--only=LISTFILE` bundles just the listed paths. A file a bundle cannot run as written (a library annotation such as `@TestOn`, a `main` other than one `void main() {`, a `flutter_test_config.dart` below `test/`, an unsafe path character, a path listed twice) is refused rather than skipped: the command names every offending file and its rule, exits 1 and writes nothing. Fixes #102. (`lib/src/commands/test_bundle_command.dart`, `lib/src/console/run_dowel.dart`, `doc/commands/test-bundle.md`, `doc/commands/index.md`, `README.md`, `llms.txt`, `skills/dowel/`)

### Fixed

- **`ConfigEditor.addImportToFile` treats a multi-line import as one directive.** The new import went after the last line that began with `import `, so a directive wrapped over several lines (`show`, `hide`, `as`, `deferred as` or an `if (dart.library...)` clause) was split and the file no longer compiled; and an import already present in that wrapped form was inserted a second time, because the duplicate check only looked for the single-line text. The helper now reads the file's header, the run of `library`, `import`, `export` and `part` directives before the first declaration, with a small tokenizer: a directive ends at its `;` outside any string or comment, the new import lands after the last import (and after a trailing comment, even a block comment that runs onto later lines), after the `library` directive of a file with no import, or at the top of a file with neither, and it stays above a header `export` or `part`. A directive counts as present when its tokens match, whatever its whitespace (around `,`, `(`, `)` and `.` and before `;` included), line wrapping or comments, and two directives on one line are both read; text inside a declaration, such as a string holding an `import` line, and inside nested block comments is never read. `import'x.dart';` without a space is a directive, and the same directive as `import 'x.dart';`. The scan skips a shebang and metadata (`@deprecated library x;` is still a library directive), does not mistake a function called `library` for one, takes a comment between `import` and its URI, and writes an import before a `part` that shares its line. A statement that is not exactly one import directive (two directives, an `export`, an empty one, `import bogus;`) now throws `ArgumentError` instead of being dropped, duplicated or written as a bare `;`, and an install transaction refuses it before it stages anything, so nothing is half-installed; the directive's own grammar (an alias, a `show` list, a conditional) is left to the analyzer. Every caller (`injectImport`, `MainDartEditor.addImport`, `make:command`, `RouteRegistryEditor.addRouteImport`) shares the fix. Fixes #101. (`lib/src/helpers/config_editor.dart`)

The release on GitHub

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.

What it is

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/anilcancakir/dowelOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.anilcancakir · 3 servers
GitHub owner
a personal account (anilcancakir)
Repository
github.com/anilcancakir/dowel
Stars
2
Repository age
181–365 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-16.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 2 stars (ranked from 10)
  • Not metRegistry entry is active and says how to run itThe entry lists no package and no remote address, so a client cannot run it.What changes this check: This check reads the registry entry's status and whether it lists a package or a remote address. Marking an entry deprecated is the publisher's own choice. The registry's documentation says a published version's metadata cannot be changed; a new server.json with a unique version string is how an entry is updated. Versioning published MCP servers
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • Does not applyPackage names its licence with a standard (SPDX) identifierThe entry lists no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnThe entry lists no package.
  • Does not applynpm package carries build provenance (attestation)The entry lists no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesThe entry lists no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-16). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.anilcancakir/dowel

Answered from the data above

Who publishes io.github.anilcancakir/dowel?

The registry ties the namespace io.github.anilcancakir to the GitHub account anilcancakir; only its owner can publish under it. Its linked repository, github.com/anilcancakir/dowel, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.anilcancakir/dowel safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.anilcancakir/dowel been security tested?

No. The registry entry declares no package and no remote endpoint, so there is nothing to run.

Does io.github.anilcancakir/dowel publish a security policy?

Yes: its repository has a public security policy (github.com/anilcancakir/dowel/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of io.github.anilcancakir/dowel?

In github.com/anilcancakir/dowel, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

The registry entry declares no package and no remote endpoint, so there is nothing to run. — the server's own choice

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-19
Hosting type
not stated
entry declares neither packages[] nor remotes[], so no delivery method is stated
MCP capability
not checked
not read (no session)
Transport
not stated
no packages[] or remotes[] to carry a transport
Required credentials
not stated
no packages[] or remotes[] to carry credential declarations
Package registry
not stated
no packages[] and no remotes[], so no delivery method is stated
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
not stated
server declares no packages[], so no package registry can be queried
Integrity hash
not stated
server declares no packages[], so no package registry can be queried
Signature / provenance
not stated
server declares no packages[], so no package registry can be queried
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
not stated
server declares no packages[], so no package registry can be queried
Publisher signals
owner: a personal account · repository age: 181–365 days · stars: 0–9
api.github.com · 2026-11-19
Maintenance
api.github.com · 2026-11-19
Environment
not stated
entry declares neither packages[] nor remotes[], so no delivery method is stated

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.anilcancakir/dowel: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.anilcancakir/dowel

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.anilcancakir/dowel)](https://protocolprobe.com/mcp/servers/io.github.anilcancakir/dowel)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology