Drop2Run MCP server: publishes static output to a live HTTPS URL. Three tools — publish_files, publish_dir, list_sites. Published on npm as @drop2run/mcp, MIT, public repository, run by the user via npx.
The entry described the server as a "security gateway with tool-access
policies"; the README, the site and the Glama listing all lead with
"the policy enforcement plane for MCP". Both are true, but a directory
carrying retired positioning is how copy drifts out of sync in the
first place.
Now byte-identical to README.md line 5, minus the bold markers this list
does not use.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016o7mBbWapnVqDAPRJb4z1K
The badge goes after the repository link and before the emoji tags,
matching the neighbouring entries, rather than after the description as
the bot's instructions word it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016o7mBbWapnVqDAPRJb4z1K
The bot tagged this PR missing-glama. The server is now listed on Glama(glama.ai/mcp/servers/xsf0221/pattern-vista-cli), so the badge URL that the other entries in this section carry now resolves for it too.
Two corrections to the pending entry, both mine.
The corpus line said the texts were written 'before generative models were in
use'. GPT-3's API was in beta from mid-2020, so that is not true of a 2021
revision; the claim that holds is 'before 2022', which is weaker and correct.
It is the wording the project itself uses in Docs/CALIBRATION.md.
And the entry counted tools -- 'ten in all', 'eight of the ten'. An entry that
enumerates goes stale the next time one ships; one that characterises does not.
This now says 'every tool but two runs entirely on the machine', which stays
true without anybody editing it.
Also adds the install command, since the package is on NuGet.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015PEbbiYSNPw7jE3LrPNhyF
The listing requirement is the badge, and the badge needed a Glama release,
and a release needs something in the repository to build. The repository was a
storefront: a README, a licence and two JSON files. It now ships a
standard-library stdio bridge to the hosted endpoint with a Dockerfile, the
server is claimed, and release 0.10.0 is published, so the score is evaluated
and the badge resolves.
The three numbers in the description had also drifted since 2026-09-01 and are
regenerated from production rather than retyped: 95,494 recorded sale
instruments rather than 80,448, eleven of twelve tools free rather than eight,
and the parcel layer now covers New York as well as Massachusetts.
A fleet of 22 hosted MCP servers (160 tools, 110 free) reached through one
dependency-free stdio bridge and a catalog endpoint. Free tier needs no
account or API key.
Requested by the listing bot. The server is already indexed on Glama, which
crawled the public repo on its own; this adds the badge the entry format
expects.
zzzjy765
Jake Barnby
Christian Velasquez
dahshanlabs
flightmasterDast
Khanhz
Marcin PyrkaandClaude Opus 5
webmilmind1
sikcapri
Timur Rakhmatullin
sf.Hsing
Pedro HernándezandClaude Opus 5
Prompeteer
Dominic BussemasandClaude Opus 5
Prateek Singh
Alper San
Andrey Tabakov
mayeu20
Tahir Almas
jgsystemsconsulting
krmisystems
Capital-W-Holdings
GarphenGate
RPER2001andClaude Fable 5.1
nworks3d
setheerwagen
Scott Benson
dockndevai
malikrashidk
Anthony Whitford
Andrii Taran
SHAR Production
DanceNitra
Frank Fiegel
Daniel Francis-Lyon