# CapabilityWire (remote · api-production-22727.up.railway.app)

A live, curated feed of new AI agent capabilities across MCP, SDKs, models, and APIs.

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

## Components

- remote · `api-production-22727.up.railway.app`: 69/100 (this document), [markdown](https://verifymcp.io/servers/jawauntb-capabilitywire/api-production-22727.md), [page](https://verifymcp.io/servers/jawauntb-capabilitywire/api-production-22727)

## Channel facts

- Endpoint: `https://api-production-22727.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## 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-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 223 tokens (~55/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 14% of tool parameters carry a description.
- **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**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the CapabilityWire MCP server?

CapabilityWire is a hosted endpoint at https://api-production-22727.up.railway.app/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 jawauntb-capabilitywire 'https://api-production-22727.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jawauntb-capabilitywire": {
      "url": "https://api-production-22727.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jawauntb-capabilitywire": {
      "type": "http",
      "url": "https://api-production-22727.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jawauntb-capabilitywire]
url = "https://api-production-22727.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jawauntb-capabilitywire": {
      "type": "remote",
      "url": "https://api-production-22727.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jawauntb-capabilitywire --url 'https://api-production-22727.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jawauntb-capabilitywire:
    url: "https://api-production-22727.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jawauntb-capabilitywire": {
      "Transport": "http",
      "Url": "https://api-production-22727.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jawauntb-capabilitywire -t streamable-http -u 'https://api-production-22727.up.railway.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jawauntb-capabilitywire": {
      "type": "http",
      "url": "https://api-production-22727.up.railway.app/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-09-20 (score 69, +1)

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

### 2026-09-17 (score 68, +1)

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

### 2026-09-15 (score 67, +1)

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

### 2026-09-13 (score 66, +1)

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

### 2026-09-11 (score 65, +1)

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

### 2026-09-09 (score 64, +1)

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

### 2026-09-07 (score 63, +1)

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

### 2026-09-05 (score 62, +1)

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

## MCP tools (4)

### `list_recent_capabilities` (~69 tokens)

List the most recent CapabilityWire events (SDKs, MCP servers, models, tools, libraries). Optionally filter by category or a since timestamp.

Input parameters:

- `category` (string)
- `limit` (integer)
- `since` (string): ISO8601 lower bound on published_at.

### `get_capability` (~26 tokens)

Fetch a single capability event by id or slug.

Input parameters:

- `id` (string, required)

### `search_capabilities` (~43 tokens)

Full-text-ish search over capability titles / summaries / tags. Returns up to `limit` matches.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `mark_seen` (~33 tokens)

Mark a capability event as delivered to the calling subscriber. Records a delivery for analytics.

Input parameters:

- `event_id` (string, required)

## Diagnostics

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

## Score history

- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 63
- 2026-09-07: 63
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 61
- 2026-09-03: 61
- 2026-09-02: 61
- 2026-09-01: 60
- 2026-08-31: 60
- 2026-08-30: 59
- 2026-08-29: 59

## Common questions

### What is the CapabilityWire MCP server?

CapabilityWire is an MCP server listed in the public MCP registry as io.github.jawauntb/capabilitywire. A live, curated feed of new AI agent capabilities across MCP, SDKs, models, and APIs. This page covers its hosted endpoint (https://api-production-22727.up.railway.app/mcp).

### Is the CapabilityWire MCP server safe to use?

CapabilityWire scores 69 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 CapabilityWire MCP server expose?

CapabilityWire exposes 4 tools: list_recent_capabilities, get_capability, search_capabilities, mark_seen. Their descriptions and schemas cost roughly 171 tokens of context every time the server is loaded.

### Does the CapabilityWire MCP server require authentication?

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

### Is the CapabilityWire MCP server still maintained?

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

## Links

- Remote endpoint: https://api-production-22727.up.railway.app/mcp
- Website: https://web-production-65186c.up.railway.app/
- Changelog RSS feed: https://verifymcp.io/servers/jawauntb-capabilitywire/api-production-22727.xml
- Changelog JSON feed: https://verifymcp.io/servers/jawauntb-capabilitywire/api-production-22727.json
- HTML version of this page: https://verifymcp.io/servers/jawauntb-capabilitywire/api-production-22727