remote_mcp
Lets authorized external tools use an MCP connection to offer themselves as tools to the server (and lets them use tools from the server as well!)
Description supplied by the publisher; it is a claim, not verified evidence.
- Name
- github:AuraFriday/remote_mcp
- Listed in
- GitHub
- Publisher
- @aurafriday
- Published
- 2025-12-02
- License
- Apache-2.0
- Evidence
- Listed only, not analyzed yet
Source: https://github.com/aurafriday/remote_mcp
What a full analysis of remote_mcp checks
Not checked yet. About 60 tools are analyzed every hour; each check links to its source when it runs:
- Publisher identity: not checked yet
- Repository ownership: not checked yet
- Organization verification: not checked yet
- Artifact provenance: not checked yet
- Source availability: not checked yet
- Version evidence: not checked yet
- Known vulnerabilities: not checked yet
- Install scripts: not checked yet
- Maintenance: not checked yet
- License: not checked yet
Before you install it
- Open the repository and confirm the account is the one you expect: look-alike names are common.
- Read what it asks for: files, accounts, network access and credentials it needs.
- Prefer a version from a verified publisher when one exists.