
RustProfit Wiki
Actively maintained
- Is it safe? We have not read the data policy of RustProfit Wiki yet. Read it on the official site before you upload anything.rust.wiki ↗
- Is it free? We have not read the prices of RustProfit Wiki yet; they are next in our queue. Until then, the official site has them.rust.wiki ↗
- What else does this? We have not measured alternatives for this one yet. If you know one, add it below.See ↓
≈ 23visits/mo
Use not read yet · estimate, read Oct 27, 2026
- For
- Rust players and skin traders checking live Steam market prices, item data and servers
- Activity
- Actively maintainedsite updated 10 days ago
- How it runs
- API
- Used for
- look up live Steam market prices for Rust skins
- check crafting and recycle yields for game items
- compare server wipe schedules to pick a server
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsrust.wiki ↗
Price not read
- MCP serverwiki.rust/rust-wikiverified in the MCP registry
- Stateanswers, 56 toolschecked 2026-10-27
- Address to connectrust.wiki/mcp
- OpenAPI spec96 pathsthe spec ↗
- API docsrust.wiki/docsthe vendor's page ↗
- MCP docsrust.wiki/mcpthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use RustProfit Wiki for?
Sign in to leave a noteWhat is RustProfit Wiki?
Independent fan-run reference site that fetches Rust skin prices from Steam's market and catalogues item crafting, salvage and loot data.
Who is RustProfit Wiki for?
Rust players and skin traders checking live Steam market prices, item data and servers
Is RustProfit Wiki still maintained?
Actively maintained: site updated 10 days ago.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.