mcpsignals vs Append Log MCP
mcpsignals is an MCP server published by zentered-studios. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Append Log MCP is an MCP server published by bobbyhouse. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  mcpsignals | |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 2.5.0 Downloads/month (PyPI): 562 Downloads/week (PyPI): 194 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | mcpsignals | Append Log MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcpsignals) | On your machine (roberthouse224/append-log-mcp:1.0.0) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/zentered-studios/mcpsignals | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
mcpsignals
Drop-in instrumentation for MCP servers. Writes tool-call events to a database you own.
Append Log MCP
A generic append-only log MCP server. Persist timestamped JSON entries and query them by recency.
How to run each
mcpsignals
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Append Log MCP As a local MCP server: Docker image
claude mcp add --env "APPEND_LOG_TOOLS=<YOUR_APPEND_LOG_TOOLS>" --transport stdio append-log-mcp -- docker run -i --rm -e APPEND_LOG_TOOLS run append-log-data:/data roberthouse224/append-log-mcp:1.0.0Requires: APPEND_LOG_TOOLS
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of mcpsignals publish no settings it asks for, so we do not compare settings.
What it can do: mcpsignals · What it can do: Append Log MCP · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.