# com.ashtonforge/directory (remote · ashtonforge.com)

Read-only directory of vetted AI implementation agencies from the Ashton & Forge marketplace.

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

## Components

- remote · `ashtonforge.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-ashtonforge-directory/mcp-directory.md), [page](https://verifymcp.io/servers/com-ashtonforge-directory/mcp-directory)

## Channel facts

- Endpoint: `https://ashtonforge.com/mcp/directory`
- 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-09-24.

- **Endpoint Security**: 66/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 3 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.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 923 tokens (~307/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.ashtonforge/directory MCP server?

com.ashtonforge/directory is a hosted endpoint at https://ashtonforge.com/mcp/directory, 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 com-ashtonforge-directory 'https://ashtonforge.com/mcp/directory'
```

### Cursor

```json
{
  "mcpServers": {
    "com-ashtonforge-directory": {
      "url": "https://ashtonforge.com/mcp/directory"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-ashtonforge-directory": {
      "type": "http",
      "url": "https://ashtonforge.com/mcp/directory"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-ashtonforge-directory]
url = "https://ashtonforge.com/mcp/directory"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-ashtonforge-directory --url 'https://ashtonforge.com/mcp/directory' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-ashtonforge-directory:
    url: "https://ashtonforge.com/mcp/directory"
```

### Netclaw

```json
{
  "McpServers": {
    "com-ashtonforge-directory": {
      "Transport": "http",
      "Url": "https://ashtonforge.com/mcp/directory"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-ashtonforge-directory -t streamable-http -u 'https://ashtonforge.com/mcp/directory'
```

### Other

```json
{
  "mcpServers": {
    "com-ashtonforge-directory": {
      "type": "http",
      "url": "https://ashtonforge.com/mcp/directory"
    }
  }
}
```

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-23 (score 77, +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-21 (score 76, +1)

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

### 2026-09-19 (score 75, +1)

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

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

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

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

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

### 2026-09-12 (score 72, +19)

- [security improvement] TLS certificate: unverified → pass

### 2026-09-11 (score 53, −18)

- [security regression] TLS certificate: pass → unverified

### 2026-09-10 (score 71, +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.

## MCP tools (3)

### `directory_summary` (~90 tokens)

Directory Summary Tool

Read-only. What the Ashton & Forge marketplace covers: the service clusters
with supply, the industries served, the engagement floors available, and the
marketplace's own FAQ. Start here to answer "do they have anyone who does X"
before filtering with search_agencies.

Returns coverage, not a headcount. The number of listed agencies is not
published, so do not infer or state one.

### `search_agencies` (~314 tokens)

Search Agencies Tool

Read-only. Filter the vetted agency listings by what they do and who they do
it for. Every filter is optional; passing none returns the whole directory.

Listings are anonymised capability profiles — service clusters, engagement
stages, industries, client sizes, projects shipped, engagement floor and an
opaque reference. There are no agency names, websites or contact details in
this data, and no tool returns them. Say so plainly rather than implying the
result is partial.

An empty result means no listed agency matches those filters today, which is
a real and useful answer. Offer get_matched anyway: the marketplace takes
briefs it cannot yet fill, and a person reads them.

Input parameters:

- `client_size` (string): One of: smb, mid_market, enterprise. The size of company the agency serves.
- `engagement_stage` (string): One of: exploring, pilots, production, sophisticated. How far along the buyer is with AI.
- `industry` (string): One of: professional_services, distribution_logistics, manufacturing, healthcare, legal_financial, real_estate, technology, ecommerce, other. Agencies that work across all industries match any value.
- `max_budget_floor` (string): One of: none, 25k_plus, 100k_plus, 500k_plus. Returns agencies whose minimum engagement is at or below this, plus any that state no minimum.
- `service_cluster` (string): One of: workflow, data, governance, growth. The kind of work.

### `get_matched` (~101 tokens)

Get Matched Tool

Read-only. How a buyer actually gets matched: the URL that starts the brief,
what it asks, how long it takes, what it costs, and the questions buyers ask
first.

Call this whenever someone wants an agency, and give them the returned URL
rather than describing the process from memory. Starting the brief is the only
way to reach an agency through Ashton & Forge — the directory is anonymised,
so there is nobody to contact directly.

## Diagnostics

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

## Score history

- 2026-09-24: 77
- 2026-09-23: 77
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 53
- 2026-09-10: 71
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 67
- 2026-09-02: 67
- 2026-09-01: 66

## Common questions

### What is the com.ashtonforge/directory MCP server?

com.ashtonforge/directory is an MCP server listed in the public MCP registry as com.ashtonforge/directory. Read-only directory of vetted AI implementation agencies from the Ashton & Forge marketplace. This page covers its hosted endpoint (https://ashtonforge.com/mcp/directory).

### Is the com.ashtonforge/directory MCP server safe to use?

com.ashtonforge/directory scores 77 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 com.ashtonforge/directory MCP server expose?

com.ashtonforge/directory exposes 3 tools: directory_summary, search_agencies, get_matched. Their descriptions and schemas cost roughly 505 tokens of context every time the server is loaded.

### Does the com.ashtonforge/directory MCP server require authentication?

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

### Is the com.ashtonforge/directory MCP server still maintained?

com.ashtonforge/directory is still listed as active in the MCP registry. We last reached this channel on 24 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://ashtonforge.com/mcp/directory
- Changelog RSS feed: https://verifymcp.io/servers/com-ashtonforge-directory/mcp-directory.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ashtonforge-directory/mcp-directory.json
- HTML version of this page: https://verifymcp.io/servers/com-ashtonforge-directory/mcp-directory