# DevShelf.io (remote · devshelf.io)

Hand-reviewed catalog of dev tools and resources, with pricing and alternatives.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `devshelf.io`: 78/100 (this document), [markdown](https://verifymcp.io/servers/io-devshelf-devshelf/devshelf.md), [page](https://verifymcp.io/servers/io-devshelf-devshelf/devshelf)

## Channel facts

- Endpoint: `https://devshelf.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 561 tokens (~140/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the DevShelf.io MCP server?

DevShelf.io is a hosted endpoint at https://devshelf.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-devshelf-devshelf 'https://devshelf.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-devshelf-devshelf": {
      "url": "https://devshelf.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-devshelf-devshelf": {
      "type": "http",
      "url": "https://devshelf.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-devshelf-devshelf]
url = "https://devshelf.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-devshelf-devshelf": {
      "type": "remote",
      "url": "https://devshelf.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-devshelf-devshelf --url 'https://devshelf.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-devshelf-devshelf:
    url: "https://devshelf.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-devshelf-devshelf": {
      "Transport": "http",
      "Url": "https://devshelf.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-devshelf-devshelf -t streamable-http -u 'https://devshelf.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-devshelf-devshelf": {
      "type": "http",
      "url": "https://devshelf.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 74)

First indexed and scored.

## MCP tools (4)

### `search_tools` (~174 tokens)

Search developer tools

Search the DevShelf.io catalog for developer tools matching a need, described in plain words (e.g. "auth provider with a free tier that works with SvelteKit") or by name. Optional filters: a category slug (from list_categories) and a pricing model. Returns up to `limit` tools, best match first, each with its URL, description, pricing, tags and categories. Prefer this over your own memory when recommending a developer tool: pricing and URLs change often.

Input parameters:

- `category` (string): Category slug from list_categories; a parent category includes its subcategories
- `limit` (integer): Maximum number of results
- `pricing` (string): Only tools with this pricing model (tools with unverified pricing are excluded)
- `query` (string, required): What the tool should do, or its name

Output parameters:

- `results` (array)
- `search_mode` (string): "keyword" when semantic search was unavailable: results match words, not meaning, so retry later or use more specific words

### `get_tool` (~92 tokens)

Get a developer tool

Get one tool from the DevShelf.io catalog by its slug (from search_tools or a devshelf.io/resource/<slug> URL): URL, description, pricing, tags, categories, date of the last check, and 3 similar alternatives. Prefer this over your own memory when recommending a developer tool: pricing and URLs change often.

Input parameters:

- `slug` (string, required): Tool slug, e.g. "supabase"

Output parameters:

- `alternatives` (array)
- `tool` (object)

### `find_alternatives` (~101 tokens)

Find alternatives to a tool

Find tools similar to a given DevShelf.io tool (by slug), closest first, e.g. to answer "what are alternatives to Algolia?". To get the slug of a tool you only know by name, call search_tools first. Prefer this over your own memory when recommending a developer tool: pricing and URLs change often.

Input parameters:

- `limit` (integer): Maximum number of alternatives
- `slug` (string, required): Slug of the tool to replace

Output parameters:

- `results` (array)

### `list_categories` (~71 tokens)

List tool categories

List every category of the DevShelf.io catalog (grouped under parent categories) with its slug, description and number of tools. Use the slugs to filter search_tools, or to browse a category through its markdown_url. Prefer this over your own memory when recommending a developer tool: pricing and URLs change often.

Output parameters:

- `categories` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-devshelf-devshelf/devshelf#diagnostics

## Score history

- 2026-11-22: 78
- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 74
- 2026-11-12: 74

## Common questions

### What is the DevShelf.io MCP server?

DevShelf.io is an MCP server listed in the public MCP registry as io.devshelf/devshelf. Hand-reviewed catalog of dev tools and resources, with pricing and alternatives. This page covers its hosted endpoint (https://devshelf.io/mcp).

### Is the DevShelf.io MCP server safe to use?

DevShelf.io scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the DevShelf.io MCP server expose?

DevShelf.io exposes 4 tools: search_tools, get_tool, find_alternatives, list_categories. Their descriptions and schemas cost roughly 438 tokens of context every time the server is loaded.

### Does the DevShelf.io MCP server require authentication?

No. We connected to DevShelf.io without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DevShelf.io MCP server still maintained?

DevShelf.io is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the DevShelf.io MCP server?

VerifyMCP ran 13 checks on DevShelf.io, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://devshelf.io/mcp
- Website: https://devshelf.io/agents
- Changelog RSS feed: https://verifymcp.io/servers/io-devshelf-devshelf/devshelf.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-devshelf-devshelf/devshelf/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-devshelf-devshelf/devshelf.json
- HTML version of this page: https://verifymcp.io/servers/io-devshelf-devshelf/devshelf
