com.ashtonforge/directory
REMOTE · ASHTONFORGE.COM · SCANNED SEP 24
Read-only directory of vetted AI implementation agencies from the Ashton & Forge marketplace.
Available components
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. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · ashtonforge.com
claude mcp add --transport http com-ashtonforge-directory 'https://ashtonforge.com/mcp/directory'
{
"mcpServers": {
"com-ashtonforge-directory": {
"url": "https://ashtonforge.com/mcp/directory"
}
}
} {
"servers": {
"com-ashtonforge-directory": {
"type": "http",
"url": "https://ashtonforge.com/mcp/directory"
}
}
} [mcp_servers.com-ashtonforge-directory] url = "https://ashtonforge.com/mcp/directory"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ashtonforge-directory": {
"type": "remote",
"url": "https://ashtonforge.com/mcp/directory",
"enabled": true
}
}
} openclaw mcp add com-ashtonforge-directory --url 'https://ashtonforge.com/mcp/directory' --transport streamable-http
mcp_servers:
com-ashtonforge-directory:
url: "https://ashtonforge.com/mcp/directory" {
"McpServers": {
"com-ashtonforge-directory": {
"Transport": "http",
"Url": "https://ashtonforge.com/mcp/directory"
}
}
} assistant mcp add com-ashtonforge-directory -t streamable-http -u 'https://ashtonforge.com/mcp/directory'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 12 Sept 26 +19
- TLS certificate: unverified → pass ▲ security
- 11 Sept 26 −18
- TLS certificate: pass → unverified ▼ security
- 10 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://ashtonforge.com/mcp/directory
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ashtonforge.com | CN=WE1,O=Google Trust Services,C=US | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | a9ba8500dbeaa4e30e6d1a4f5adfc7b7 |
| SANs: ashtonforge.com, *.ashtonforge.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of ashtonforge.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ashtonforge.com. | present | 56206 | 8 | Verified |
| ashtonforge.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; |
| x-content-type-options | nosniff |
| x-frame-options | deny |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ashtonforge.com/mcp/directory | Verified | 200 | |
| http (plaintext) | http://ashtonforge.com/mcp/directory | HTTPS enforced | 301 | https://ashtonforge.com/mcp/directory |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
directory_summary Directory Summary Tool ~90
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
get_matched Get Matched Tool ~101
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
search_agencies Search Agencies Tool ~314
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.