Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Follow-up value is specific to ProxyLLM model-catalog and account-provisioning tools: Does human membership activation remain separate from autonomous signup and routing-key creation?
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
LLM proxy/gateway access from MCP clients.
What we know
Radar identity indicates an MCP package for ProxyLLM, but sufficient first-party public documentation was not recovered to safely describe provider routing, auth, logging/retention or configuration-write capabilities.
Maintenance / activity evidence
- proxyllm-mcp 1.0.2 published 2026-07-15T04:42:39.146Z
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: low.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Permissions not yet verified. Complete write authority is not verified.
- Authentication not yet verified.
- Sensitive access: Prompts/responses, Provider credentials
- Gateway may expose sensitive prompts and incur model costs; exact boundaries unresolved.
Full authority, access and evidence limits are available in Review context and Access & risk.
All limitations / Review context
Does human membership activation remain separate from autonomous signup and routing-key creation?
The bounded review of the publisher's documented ProxyLLM model-catalog and account-provisioning tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.
- Gateway may expose sensitive prompts and incur model costs; exact boundaries unresolved.
- Unknown.
- Sensitive access: Prompts/responses, Provider credentials
- 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.
- Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
- Documented tool authority and any remote data handling must be checked before installation or use.
- Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
- official docs/repository
- auth
- provider routing
- retention/logging
- write/config actions
- Prompt/response data may traverse a gateway, but retention/logging policy is unresolved.
- Provider/API-key handling is unresolved.
- Do not assert model list or routing writes without live first-party evidence.
Original activity observations
- proxyllm-mcp 1.0.2 published 2026-07-15T04:42:39.146Z
Technical identity
npm/proxyllm-mcp- Exact implementation source
- https://www.npmjs.com/package/proxyllm-mcp ↗
- Reviewed resource type
- Gateway
- Package identity
- npm:proxyllm-mcp
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- Package registry ↗
proxyllm-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Setup · Watchlist
Gateway setup
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / configure gateway or CLI
Publisher instructionsPublisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Claude Code only · Publisher instructions
claude mcp add proxyllm -- npx -y proxyllm-mcpConfigure / authenticate
MCP100 setup guideTools can be discovered without a token. Optionally PROXYLLM_ACCOUNT_TOKEN for authenticated management (sk_ full or rk_ read only). Signup and checkout are separate user actions.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Check connection
Suggested checkConfirm model catalog and read-only account tools; never provision or pay as smoke test.
Remove / uninstall / revoke
MCP100 setup guideIf registered as `proxyllm-mcp` in Claude Code, remove its exact client entry with `claude mcp remove proxyllm-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Publisher install example registration name(s): proxyllm. The supplied removal example applies only to an existing Claude Code registration named proxyllm-mcp; it does not remove the differently named install example. Confirm the actual host entry before use.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide · Review before use
claude mcp remove proxyllm-mcp
Official Documentation & Sources
What it does
Radar identity indicates an MCP package for ProxyLLM, but sufficient first-party public documentation was not recovered to safely describe provider routing, auth, logging/retention or configuration-write capabilities.
- Capability
- AI & Reasoning
- Resource type
- Gateway
- Best fit
- LLM proxy/gateway access from MCP clients.
Representative uses
- Invoke ProxyLLM gateway/model operations once configured
Limitations
- Prompt/response data may traverse a gateway, but retention/logging policy is unresolved.
- Provider/API-key handling is unresolved.
- Do not assert model list or routing writes without live first-party evidence.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Not documented in the reviewed sources
- Permissions
- Not documented in the reviewed sources
- Data handling
- Unknown.
- Cost
- unknown
- Risk and cautions
- Gateway may expose sensitive prompts and incur model costs; exact boundaries unresolved.
Access scope and cautions
- Write actions
- Not verified
- Sensitive access
- Prompts/responses Provider credentials
- Risk level
- high
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-08. Watchlist tracking is not a recommendation or a security certification.