Cloudinary Asset Management vs HTTP 507 insufficient-storage
Cloudinary Asset Management lists no tools and runs remotely and HTTP 507 insufficient-storage lists no tools and runs remotely.
| Fact | Cloudinary Asset Managementio.github.cloudinary/asset-management-mcp | HTTP 507 insufficient-storageio.github.sadri-dridi/http-507 |
|---|---|---|
| Score | Not checked yet | Not checked yet |
| Status | Not checked yet | Not checked yet |
| Tools | 0 | 0 |
| Can write data | No tools listed | No tools listed |
| Runs | Remote | Remote |
| Needs first | – | – |
| Licence | MIT | Not stated |
| Latest version | 0.11.5 | 1.0.0 |
| Known advisories | 0 | Not checked yet |
| Works in | Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Goose, LM Studio, Gemini CLI, Codex, oterm, Agenvoy, Amp, AnythingLLM, Bob Shell, ECA, Kiro, Kiro CLI | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, oterm, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI |
| Downloads last week | Not known | Not known |
| Install | Install Cloudinary Asset Management | Install HTTP 507 insufficient-storage |
Scores and status come with our own checks, which have not run on these servers yet. The rest is from the publishers' registry entries, package registries and advisory databases.
Compare Cloudinary Asset Management with othersCompare HTTP 507 insufficient-storage with others