anythingmcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Connect LLM clients to a connector gateway and service integrations

What we know

🔌 #1 MCP Gateway on GitHub — Connect Claude, ChatGPT, Copilot and any AI client to 200+ ready-to-use connectors, existing MCP servers, and any REST, SOAP, GraphQL or SQL system. Self-hosted, no-code and open source. Automatically builds Knowledge Graphs and AI Skills from how your systems connect, with SSO, governance and enterprise access control Connect LLM clients to a connector gateway and service integrations.

Maintenance / activity evidence

GitHub REST pushed_at 2026-10-09T15:58:55Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Reported action classes: potential connected-service writes (not verified). Complete write authority is not verified.
Self-hosting and connected-app credentials
Sensitive access: Credentials and connected-system data

Connector gateway may grant wide cross-service access; SSO/governance claims need deployment-specific verification.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

714 repository stars

Stars observed Oct 9, 2026.

Repository total for HelpCode-ai/anythingmcp.

All limitations / Review context

Has anythingmcp changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

Connector gateway may grant wide cross-service access; SSO/governance claims need deployment-specific verification.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Self-hosting and connected-app credentials
Credentials and connected-system data
Reviewed write actions: potential connected-service writes (not verified)
Sensitive access: Credentials and connected-system data
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No exhaustive advisory or runtime review performed; never infer installation safety.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Upstream project advertises AGPL-3.0 licensing and self-hosted authentication; review obligations before redistribution.
Repository pushed_at explicitly observed

Original activity observations

GitHub REST pushed_at 2026-10-09T15:58:55Z

Technical identity

github.com/HelpCode-ai/anythingmcp

Exact implementation source: https://github.com/HelpCode-ai/anythingmcp ↗
Reviewed resource type: Gateway
Repository identity: HelpCode-ai/anythingmcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
helpcode-ai/anythingmcp
Recorded repository material and project history.

Setup · Watchlist

Self-hosted gateway service setup

Publisher instructions.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Requires Docker 24+, Docker Compose and openssl. Inspect the mutable published docker-compose.quickstart.yml before launching; create and protect JWT_SECRET and ENCRYPTION_KEY in .env, then start the stack only in a controlled environment.
Advanced configuration · self hosted install or run
self hosted install or run · Review before use
mkdir anythingmcp && cd anythingmcp curl -fsSLo docker-compose.yml https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env docker compose up -d
Configure / authenticate
Publisher instructions
Requires Docker Compose; generated secrets stay in .env; configure upstream connectors inside platform.
Check connection
MCP100 setup guide
After the Docker Compose stack starts, inspect docker compose ps and the container logs to determine whether the gateway is up; then use a deliberately limited, non-production upstream connector to test MCP discovery. Container running does not prove upstream API authorization.
docker compose ps
docker compose logs --tail=100
Remove / uninstall / revoke
From the original Compose directory, use `docker compose down` to stop the stack; remove any client entry that targets its MCP endpoint. Do not append `-v` because that would remove named volumes.

Official Documentation & Sources

What it does

🔌 #1 MCP Gateway on GitHub — Connect Claude, ChatGPT, Copilot and any AI client to 200+ ready-to-use connectors, existing MCP servers, and any REST, SOAP, GraphQL or SQL system. Self-hosted, no-code and open source. Automatically builds Knowledge Graphs and AI Skills from how your systems connect, with SSO, governance and enterprise access control Connect LLM clients to a connector gateway and service integrations.

Capability: Cloud & DevOps
Resource type: Gateway
Best fit: Connect LLM clients to a connector gateway and service integrations

Representative uses

Connect multiple upstream MCP tools
Control access and server management
Configure local or remote client integrations
Connect LLM clients to a connector gateway and service integrations

Limitations

Connector gateway may grant wide cross-service access; SSO/governance claims need deployment-specific verification.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Upstream project advertises AGPL-3.0 licensing and self-hosted authentication; review obligations before redistribution.
Repository pushed_at explicitly observed

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Self-hosting and connected-app credentials
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: Credentials and connected-system data
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: Connector gateway may grant wide cross-service access; SSO/governance claims need deployment-specific verification.

Access scope and cautions

Write actions: Not verified potential connected-service writes (not verified)
Sensitive access: Credentials and connected-system data
Risk level: high
Security notes: Connector gateway may grant wide cross-service access; SSO/governance claims need deployment-specific verification.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Connect multiple upstream MCP tools; Control access and server management; Configure local or remote client integrations; Connect LLM clients to a connector gateway and service integrations.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. Installation/authentication detail is incomplete; do not infer settings from package name. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Self-hosting and connected-app credentials

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: potential connected-service writes (not verified). Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

Credentials and connected-system data Recorded sensitive-access context: Credentials and connected-system data.

What limitations and risks should I check before use?

Connector gateway may grant wide cross-service access; SSO/governance claims need deployment-specific verification. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. Upstream project advertises AGPL-3.0 licensing and self-hosted authentication; review obligations before redistribution. Repository pushed_at explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.