Crates Package Info

dev.fly.looper-productsPublished by looper-products.fly.devOfficial publisherv0.1.0Updated Oct 29, 2026

Read-only: public crates.io metadata for a Rust crate. Free, no API key.

The publisher's own server: kosmos.info.pl

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Remote read-only MCP server that lets an assistant look up public crates.io metadata for any Rust crate by name.

What you can do
  • Look up a Rust crate by name and get its latest version, description, license and repository link
  • See download counts, recent downloads, max version and last update time
  • Retrieve documentation and homepage links for the crate
When to use it
Useful when working with Rust dependencies and you want the assistant to check a crate's current version, license, popularity or project links without leaving the conversation.
Requirements
A remote streamable HTTP endpoint; no login, API key, environment variables or headers are needed. Network access to the server and to the public crates.io API is required.
Before you install
Read-only and unauthenticated; it only fetches public crates.io data and does not modify anything. Requests are relayed to the third-party crates.io API.

Installation

In SourceWeft

  1. Open Crates Package Info in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.fly.looper-products%2Fcrates-package-info/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "crates-package-info": {
      "type": "http",
      "url": "https://looper-products.fly.dev/mcp-crates/"
    }
  }
}

Tools

1

get_crate_info

Read-only: fetch public metadata for a Rust crate from the free, unauthenticated crates.io API (https://crates.io/api/v1/crates/<name>). Returns name, latest version, description, license, repository, downloads, recent_downloads, max_version, updated_at, documentation and homepage. No login or API key.

Parametersnamerequired

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Info integrations