The server is listed on Glama and passes its automated checks; the badge
currently renders A. Placed after the repo link, before the platform tags,
matching the convention used by every other badged entry in the file.
The listing is both: enterprise search/RAG with permissions, and agents using that over connected workplace apps.
Co-authored-by: Cursor <cursoragent@cursor.com>
The catalog line listed MCP tools. The server's job is giving agents permission-aware context from connected workplace apps.
Co-authored-by: Cursor <cursoragent@cursor.com>
Supersedes #14103 and #14313, which each fixed half of this line and
therefore conflicted with one another. Consolidated into one diff so it
applies cleanly.
- repo moved to the greencalculus org (the old jeremiahsay path still
redirects, so nothing was broken — this just points at the canonical one),
and the Glama badge path follows it
- 13,000+ -> 16,673 factors, counted from the live corpus
- 11 -> 12 tools, counted off tools/list against mcp.greencalculus.com today
- notes the remote endpoint alongside the npx install, since the registry
entry declares both stdio and streamable-http transports
Один сервер в одном PR, как просил мейнтейнер при закрытии #14182.
Сервер оценён Glama, бейдж со score в строке, репозиторий заявлен владельцем.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
One line, placed alphabetically between mordor-forge/trident-mcp and
mutonby/openshorts, now carrying the Glama score badge the list expects.
The badge needed a Glama release, a release needed a build test that
starts the server and answers introspection, and that needed a working
credential -- which for an account-required server used to mean handing
out one that could also spend the account's balance. API keys now carry
a scope, so the build runs with a read-only key that cannot generate
anything. The server is rated B.
Rebased onto current main again; the branch had drifted.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>