MCP servers › io.github.anilcancakir › tapir
MCP server · registry snapshot 2026-11-18 · last checked 2026-11-18
tapir MCP server
Registry name io.github.anilcancakir/tapir
by anilcancakir · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗
Drive a live Flutter app from an AI agent: snapshot the Semantics tree, tap, type and screenshot. — the publisher's description
Summary
io.github.anilcancakir/tapir 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/tapir, 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: 3 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-18 snapshot)
- First listed version
- 2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-11-16 to 2026-11-18; 3 in the 90 days before the 2026-11-18 snapshot.(versions still listed in the registry only)
Most recent 3 versions
1.1.0· 2026-11-181.0.2· 2026-11-161.0.1· 2026-11-16
- Registry data
- snapshot 2026-11-18
- Package and repository
- checked 2026-11-18
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.2 (published 2026-11-16) → 1.1.0 (published 2026-11-18), between the registry lists of 2026-11-17 and 2026-11-18.
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, cut at 4,000 characters)
### Added - **`tapir:console` takes `--grep` and `--logger`, and says when the capture buffer has dropped older lines.** `--limit=200` returned at most 50 entries because the `debugPrint` buffer holds 50, and one chatty source filled every slot. `--grep` (case-insensitive message substring) and `--logger` (exact logger name) now apply to both sources before `--limit` clips, and search only what is still in the buffer. The reply gains `capped: true` once the buffer has dropped older `debugPrint` lines, so older output exists that no `--limit` and no filter can reach; it stays on every later reply and does not say that this reply was bounded by the buffer, and it is absent until then. `ConsoleRequest` gains matching `grep` and `logger` fields (default null); while a filter is active the handler asks `recentLogsReader` for a large `limit` and filters the merged list itself, so a reader that clips to `limit` or ignores the filters stays correct. Fixes #97. (`lib/src/extensions/ext_console.dart`, `lib/src/tapir_log_capture.dart`, `lib/src/commands/tapir_console_command.dart`, `lib/src/tapir_dowel_provider.dart`) - **`tapir:screenshot --strict` fails instead of writing a possibly stale frame.** While the app is not producing frames the extension still answers, so a script got a plausible image of an old frame; with the flag the command exits 1 and does not create or overwrite the file. Without it the behaviour is unchanged, and on a web (CDP) session it only covers `--ref` captures. Closes #98. (`lib/src/commands/tapir_screenshot_command.dart`, `lib/src/commands/frame_warning_output.dart`) ### Changed - **tapir requires `dowel ^1.0.5`.** On a web-server session (`dowel start --cdp-port`) dowel 1.0.4 and older returned an extension error as an ordinary result, so `tapir:tap` with an unknown ref printed `✓ Tapped e99` and exited 0 (reported as #94); dowel 1.0.5 throws it as an error, so the floor moves up from `^1.0.0`. (`pubspec.yaml`) - **`tapir:console` orders the merged list newest first by `time`.** Crumbs entries used to follow the capture buffer in the order the reader returned them (oldest first), so a `--limit` clip could keep the oldest crumbs entries and a repeated entry kept its oldest occurrence. The merge now sorts newest first (an entry with no parseable `time` follows the dated ones), keeps the newest occurrence of a repeat, and lets the capture buffer win a cross-source duplicate. (`lib/src/extensions/ext_console.dart`) ### Fixed - **A tap that opens or closes a dialog, sheet, menu or page reports the route change.** `effect.changed` measures only the label, value, enabled and checked flags of the target's own semantics subtree and its enclosing route name, and a dialog is a new route over the target, so the tap answered `changed: false` and the summary said "no observable change"; the effect now adds `routeChanged: true` when the top route of the root navigator or of the navigator holding the tapped widget changed (absent otherwise, independent of `changed` so both can be true, and `changed` keeps its meaning; a route on another nested navigator is not seen). The `tapir:tap` summary prints `(route changed; run tapir:snap to see it)` whenever `routeChanged` is true, otherwise `(target unchanged)` on no measured change. Fixes #95. (`lib/src/extensions/ext_pointer.dart`, `lib/src/utils/effect_report.dart`, `lib/src/commands/tapir_tap_command.dart`, `lib/src/tapir_dowel_provider.dart`) - **`tapir:snap` keeps one node on one line when a label or value holds a line break.** A semantics label such as `Have an account?\nSign in` printed as two lines with the `[ref=eN]` token after the second, which broke the one-node-per-line shape that agents and the snapshot diff key on. `\n` and `\r` in a printed label, value or text line are now escaped as the two characters `\n` and `\r`; ref resolution still binds the raw label, and a label copied from the printed form needs its escapes undone before it is passed to a matching co
Source: the official MCP Registry list on 2026-11-17 and on 2026-11-18; release notes from the GitHub Releases API, checked 2026-11-18.
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-18. 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-18. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-18. Source: read 2026-11-18.
- Cline marketplace. Not in the Cline marketplace on 2026-11-18. Source: read 2026-11-18.
Own host
- security.txt. No security.txt at https://anilcancakir.com/.well-known/ (HTTP 404, 2026-11-18). Source: anilcancakir.com/.well-known/security.txt · read 2026-11-18.
- A2A agent card. No A2A agent card at https://anilcancakir.com/.well-known/ (HTTP 404, 2026-11-18). Source: anilcancakir.com/.well-known/agent-card.json · read 2026-11-18.
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 #6The 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 says | We found | Result | Source · date |
|---|---|---|---|
| Repository github.com/anilcancakir/tapir | Opens publicly | matches | api.github.com · 2026-11-18 |
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/tapir
- Stars
- 3
- 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-18; 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 rating4 of 5 record checks met · 4 do not apply
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: 3 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-18 (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/tapir
Answered from the data aboveWho publishes io.github.anilcancakir/tapir?
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/tapir, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.anilcancakir/tapir 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/tapir been security tested?
No. The registry entry declares no package and no remote endpoint, so there is nothing to run.
Does io.github.anilcancakir/tapir publish a security policy?
Yes: its repository has a public security policy (github.com/anilcancakir/tapir/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/tapir?
In github.com/anilcancakir/tapir, which opens publicly.
Found this page useful?
Anonymous · no sign-inA 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 #1The 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.
“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/tapir: MCP server record.” Data checked 2026-11-18. https://protocolprobe.com/mcp/servers/io.github.anilcancakir/tapir
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
[](https://protocolprobe.com/mcp/servers/io.github.anilcancakir/tapir)
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