MCP Check
Servers
All serversNewest firstOfficial, by companyMCP server for…

Categories

Search & web2,770Finance & payments1,915Productivity & notes1,474Files & documents1,324AI & media generation1,226Coding & design1,088Analytics & monitoring915Email & messaging814Business data794Cloud & infrastructure787Agent safety & governance737Databases & data692Browser automation548Security541Legal & government357Games & entertainment217Health & science214Marketing & sales185Other2,856
Scan or add
Scan a configAdd your serverGet a private server built

More

Claude skillsHow we check
Scan a config

AlloFlow Document Remediation

io.github.Apomera/alloflow-remediation

Source code

About AlloFlow Document Remediation

AlloFlow Document Remediation is an MCP server published by the GitHub account Apomera. Local-first document accessibility remediation using the canonical AlloFlow app pipeline.

It runs on your own machine: your AI client starts it from the MCP bundle package alloflow-remediation.mcpb, with no version pinned.

It asks for no keys or passwords.

Version 0.3.5 was published on 17 August 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 7 automated checks on registry metadata: 3 pass, 1 warn, 0 fail, 3 info. How we check.

What it asks for

This server declares no environment variables, so it asks for no keys or settings.

Checks

CheckResultDetail
Source repository linkedPasshttps://github.com/Apomera/AlloFlow
Version pinnedWarnNot pinned: https://github.com/Apomera/AlloFlow/releases/download/mcpb-v0.3.5/alloflow-remediation.mcpb
Secrets requestedInfoAsks for no secrets
Known package registryPassAll packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownershipInfoName verified via GitHub account Apomera
Registry text aimed at the AIPassDescription and settings contain no hidden characters or instructions to the AI
Code red flagsInfoPackage could not be read (too large)

Popularity & health: 55 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity7 / 40

4 GitHub stars, no download count, no Hacker News posts found. Best two of the three, each on a log scale.

Activity25 / 25

Last push 2026-10-28, last release 2026-09-14, 2,658 commits in 90 days.

Issue health8 / 15

0 closed of 0 issues, too few to judge. No data, so half marks.

Our checks16 / 20

1 warning, each costing a fifth.

4 forks, 11 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry nameio.github.Apomera/alloflow-remediation
PublisherGitHub account Apomera
How the name is verifiedName verified via GitHub account Apomera. The registry ties the name prefix to that account or domain; it does not check the code.
TypeLocal: runs on your machine from a package
Packagesmcpb https://github.com/Apomera/AlloFlow/releases/download/mcpb-v0.3.5/alloflow-remediation.mcpb no version given (stdio)
Version0.3.5
Published
Last updated
Source repositoryhttps://github.com/Apomera/AlloFlow
WebsiteNone linked
CategoryFiles & documents (assigned by keyword rule, not by hand)

Related servers in Files & documents