Ashby

Name: Ashby
Author: pipeworx-io

Server Details

Ashby MCP Pack — wraps the Ashby ATS API

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status: Unhealthy
Uptime: 34.0% over 50 days
Last Tested: 2026-10-06 10:49
Transport: Streamable HTTP
URL
Repository: pipeworx-io/mcp-ashby
GitHub Stars: 0
Server Listing: ashby

TDQS

A3.8/5.0

Scored 2026-09-27 00:15 across 41 tools

Disambiguation2/5

Multiple tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and discover_tools all route or search across the same data catalog, and the beta variant is intentionally identical to the stable router. The prediction-market cluster (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, bet_research) and company tools (entity_profile, company_facts, compare_entities) also blur together despite lengthy descriptions. An agent would frequently need to read several descriptions carefully before picking the right call.

Naming Consistency4/5

Nearly all tools use lowercase snake_case and mostly follow a verb_noun (ask_pipeworx, resolve_entity, validate_claim) or noun pattern (company_facts, entity_profile). The polymarket_* and ashby_* prefixes provide strong family consistency, and memory verbs (remember/recall/forget) are predictable. Minor deviations exist (scan_dependency vs scan_competitor_ai_presence) but the overall convention is coherent.

Tool Count2/5

41 tools is excessive for a single server, especially one that appears to bundle two unrelated domains (Ashby ATS plus a Pipeworx data platform). The count is inflated by redundant meta-tools (six variants of routing/discovery) and several thin wrappers. This feels like two or three servers merged into one rather than a well-scoped single purpose.

Completeness3/5

The data/research side is quite complete with lookups, comparisons, grounding, subscriptions, memory, and resolution auditing. However, the Ashby ATS side is read-only — candidates, jobs, and applications can be listed/fetched but there are no create, update, or delete operations, leaving obvious dead ends for any ATS workflow. The overall domain is ambiguous, which makes true coverage hard to assess.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

29 tool updatesSep 27, 2026

Changedai_visibility_check1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "entity": "Tesla"
+  }
+]
```

Changedask_pipeworx3 fields changed

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Changedask_pipeworx_beta4 fields changed

addedInput schema / examples

Added value: +[
+  {
+    "question": "What is the current US unemployment rate?"
+  }
+]

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Changedask_pipeworx_grounded4 fields changed

addedInput schema / examples

Added value: +[
+  {
+    "question": "What was Apple's fiscal 2023 revenue?"
+  }
+]

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Your question in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Addedcompany_facts

Changedcompare_entities1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "type": "company",
+    "values": [
+      "AAPL",
+      "MSFT"
+    ]
+  }
+]

Changeddeep_research9 fields changed

addedInput schema / examples

Added value: +[
+  {
+    "depth": "quick",
+    "question": "What is the current US unemployment rate and how has it changed over the past year?"
+  }
+]

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / input

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / prompt

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / q

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"The research question, in natural language. Broad/multi-part is fine — decomposition is the point."New value: +"The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases."

addedInput schema / properties / text

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Changedentity_profile1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Changedforget4 fields changed

addedInput schema / properties / k

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

changedInput schema / properties / key / description

Previous value: -"Memory key to delete"New value: +"Memory key to delete. Accepts name, k, label as aliases."

addedInput schema / properties / label

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Changedgenerate_llms_txt1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "url": "https://pipeworx.io"
+  }
+]

Addedkalshi_weather_edge

Changedpipeworx_feedback1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "message": "Fleet #2184 smoke test: verifying pipeworx_feedback example call returns non-empty.",
+    "type": "other"
+  }
+]

Changedpipeworx_trending1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "window": "7d"
+  }
+]
```
Changedpolymarket_arbitrage1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "topic": "Fed rate decision"
+  }
+]
```
Changedpolymarket_edge_tracker1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "days": 14,
+    "window": "1wk"
+  }
+]
```

Changedpolymarket_edges3 fields changed

addedInput schema / examples

Added value: +[
+  {
+    "limit": 5,
+    "window": "1wk"
+  }
+]

changedInput schema / properties / min_edge_pp / description

Previous value: -"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage."New value: +"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage and Polymarket's own taker fee."

changedInput schema / properties / slippage_pp / description

Previous value: -"Assumed execution slippage in percentage points per leg (default 0.3). Subtracted from raw |edge| before ranking and Kelly sizing. Polymarket has zero trading fees as of 2024 but bid/ask + thin depth typically eats 20-50bp per trade. Bump for very thin partitions; drop to 0 if you have a smarter fill model."New value: +"Assumed execution slippage in percentage points per leg (default 0.3), for bid/ask + thin depth cost that a last-trade price does not show. Subtracted from raw |edge| before ranking and Kelly sizing, ON TOP OF Polymarket's own taker fee — which is NOT zero (rate 0.04-0.07 depending on category, read off each market's own published fee schedule; see fees_pp_applied on every row and fees.ts for the full schedule). Bump slippage for very thin partitions; drop to 0 if you have a smarter fill model — the fee still applies regardless."

Changedpolymarket_fill_risk1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "market": "will-the-fed-increase-interest-rates-by-25-bps-after-the-december-2026-meeting-20260729232808636",
+    "side": "buy_yes",
+    "size_usd": 1000
+  }
+]

Changedrecall4 fields changed

addedInput schema / properties / k

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

changedInput schema / properties / key / description

Previous value: -"Memory key to retrieve (omit to list all keys)"New value: +"Memory key to retrieve (omit to list all keys). Accepts name, k, label as aliases."

addedInput schema / properties / label

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Changedrecent_changes1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "since": "30d",
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Addedrelease_calendar_markets

Changedremember10 fields changed

addedInput schema / examples

Added value: +[
+  {
+    "key": "target_ticker",
+    "value": "AAPL"
+  }
+]

addedInput schema / properties / content

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

addedInput schema / properties / data

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

addedInput schema / properties / k

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

changedInput schema / properties / key / description

Previous value: -"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\")"New value: +"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\"). Accepts name, k, label as aliases."

addedInput schema / properties / label

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / text

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

addedInput schema / properties / v

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

changedInput schema / properties / value / description

Previous value: -"Value to store (any text — findings, addresses, preferences, notes)"New value: +"Value to store (any text — findings, addresses, preferences, notes). Accepts content, text, data, v as aliases; a non-string value is stored as JSON."

Addedresolution_audit
Addedresolution_diff

Changedresolve_entity1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Changedscan_competitor_ai_presence1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "entities": [
+      "Pipeworx",
+      "Zapier"
+    ]
+  }
+]

Changedscan_dependency1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "package": "left-pad"
+  }
+]
```

Changedsearch_within1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "query": "supply-chain risk",
+    "text": "Apple Inc. reported fiscal 2023 revenue of $383.285 billion, driven by strong iPhone and Services growth. Net income was $96.995 billion. The company faced supply-chain risk in China during the quarter."
+  }
+]

Changedsuggest_questions1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "topic": "finance"
+  }
+]
```

Changedvalidate_claim1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "claim": "Apple's fiscal 2023 revenue was $383 billion"
+  }
+]

1 tool updateSep 11, 2026

Changedbet_research2 fields changed

changedInput schema / examples

Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]

changedInput schema / properties / market / description

Previous value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."

2 tool updatesSep 11, 2026

Changedbet_research2 fields changed

changedInput schema / examples

Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]

changedInput schema / properties / market / description

Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."

Changedpolymarket_kalshi_spread2 fields changed

changedInput schema / examples

Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]

changedInput schema / properties / topic / description

Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Greenhouse A
io.github.pipeworx-io
Greenhouse MCP Pack — wraps the Greenhouse Harvest API v1
CRM
2
Bamboohr B
io.github.pipeworx-io
BambooHR MCP Pack — wraps the BambooHR API v1
ERP Systems
2
Airtable A
io.github.pipeworx-io
Airtable MCP Pack — wraps the Airtable REST API v0
Databases App Automation Workplace & Productivity
2
Calendly A
io.github.pipeworx-io
Calendly MCP Pack — wraps the Calendly API v2 for scheduling data.
Calendar Management Workplace & Productivity
412

Related MCP Servers

MCP Ashby Connector
App Automation Developer Tools Project Management
MCP-Mirror
A
license
Not graded
quality
Not graded
maintenance
An MCP server that enables LLMs to interact with Ashby's Applicant Tracking System for managing candidates, jobs, applications, and interviews. It supports data operations, batch processing, and access to pipeline analytics and reporting.
Updated a year ago (2025-06-25 18:50 UTC)
MIT
ashby-mcp
CRM
dewierwan
A
license
A
quality
A
maintenance
MCP server for Ashby ATS that enables AI agents to review candidates, read application details, and write evaluation notes through the Model Context Protocol.
Updated 18 days ago (2026-09-18 20:35 UTC)
24
68 npm
1
MIT
MCP Ashby Connector
Project Management App Automation
thnico
A
license
Not graded
quality
D
maintenance
A server implementation that enables LLMs to interact with Ashby's Applicant Tracking System, allowing management of candidates, jobs, applications, interviews, and analytics through the Model Context Protocol.
Updated a year ago (2025-04-25 10:19 UTC)
16
MIT
Ashby MCP
CRM Project Management
JakeTeagle
A
license
Not graded
quality
D
maintenance
Connects your Ashby recruiting data to Claude, enabling natural language queries and management of candidates, applications, jobs, interviews, offers, and team information.
Updated 4 months ago (2026-06-16 11:10 UTC)
68 npm
MIT

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Server Details

TDQS

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

MCP Ashby Connector

ashby-mcp

MCP Ashby Connector

Ashby MCP

Glama MCP Gateway

Resources