directory

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

Should I use this

Quality & Safety

B
Description quality
100%
Schema completeness
50%
Naming quality
93%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~591Tokens (tool definitions)
~918 BTypical response size
Minimal attention impact (0.46% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://ashtonforge.com/mcp/directorystreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢directory_summary

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.

Input Schema

{
  "type": "object",
  "properties": {}
}
🟢search_agencies(service_cluster, industry, client_size, engagement_stage, max_budget_floor)

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 Schema

{
  "type": "object",
  "properties": {
    "service_cluster": {
      "description": "One of: workflow, data, governance, growth. The kind of work.",
      "type": "string"
    },
    "industry": {
      "description": "One of: professional_services, distribution_logistics, manufacturing, healthcare, legal_financial, real_estate, technology, ecommerce, other. Agencies that work across all industries match any value.",
      "type": "string"
    },
    "client_size": {
      "description": "One of: smb, mid_market, enterprise. The size of company the agency serves.",
      "type": "string"
    },
    "engagement_stage": {
      "description": "One of: exploring, pilots, production, sophisticated. How far along the buyer is with AI.",
      "type": "string"
    },
    "max_budget_floor": {
      "description": "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.",
      "type": "string"
    }
  }
}
🟢get_matched

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.

Input Schema

{
  "type": "object",
  "properties": {}
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools
verifiedversion not recorded3 tools