Intake notes: listed with facts from the source repo; not yet vetted. A verdict waits on a real hands-on audit (install, run, audit what it injects). Health is checked automatically; the summary is the author’s own description.
grafana-mcp
• Not yet vettedMCP server for Grafana
In the intake queue. Listed with facts only; no verdict until a human runs it.
by grafana MCP server DevOps
Shipped today passing liveness · checked Jul 28, 2026
Commit activity · last 52 weeks
Stars3.3k
LanguageGo
LicenseApache-2.0
Open issues128
Pricingfree
ListedJul 12, 2026
Facts pulled from the source repo and refreshed nightly. Stars are a data point, not our ranking. We don't order by popularity.
Runs in
| Harness | Support | Notes |
|---|---|---|
| Any MCP client | untested | — |
Support levels reflect what we actually ran, not what the README claims. untested means exactly that.
What a vet will check
- Whether it can act or write when told not to (read-only and scope enforcement)
- What it injects per session: token cost and the size of the tool surface
- Where your data goes: any call that leaves your machine, disclosed or not
No verdict is published until a human installs it, runs it, and audits what it injects. How vetting works →
More in DevOps
posthog-mcp MCP server “This is not a read-only tool, and its reach is exactly the scopes of the personal API key you hand it. Of its 44 tools, 26 read and 18 write, and 5 of those delete production objects (delete-feature-flag, insight-delete, dashboard-delete, experiment-delete, survey-delete). The safety is real and server-enforced: every tool declares its required_scopes and PostHog checks them, so a key minted with only :read scopes mechanically blocks every write and delete. So mint one that way. Create a read-scoped personal API key unless you specifically want an agent creating feature flags in your live project. Second thing to know: the default install points at https://mcp.posthog.com/mcp, a hosted Cloudflare Worker, so your key and query results transit PostHog's own infrastructure (you already trust them with this data, and you can self-host by pointing POSTHOG_BASE_URL at your own worker). Two smaller notes: the docs-search tool sends your question to api.inkeep.com, a third party, and the server reports its own tool-call usage back to PostHog via posthog-node. No filesystem access, no other egress.”
sentry-mcp MCP server “Official, and it connects the way you'd hope. On sentry.io you don't paste a token, you approve a device-code login; self-hosted takes a token and a --host. Once connected it reads your org's real issues, errors, and traces. That's the point, and also the thing to be deliberate about. Production error data is where stack traces, user emails, and other PII live, and this pulls it into the model's context. Fine for most work, worth a thought under strict data rules. Two smaller notes. The server reports its own telemetry to Sentry via a built-in DSN (Sentry using Sentry; override it with --sentry-dsn if you'd rather it didn't), and --agent mode collapses the tool surface to a single use_sentry tool, which is the lighter way to run it inside an agent.”
aws-mcp MCP server Open source MCP Servers for AWS
cloudflare-mcp MCP server mcp-server-cloudflare: a Claude Code / MCP tool.