uk.co.ashleypayne/ashley-payne

Est-ce que uk.co.ashleypayne/ashley-payne est sûr ?

Au dernier audit MCP Hub, le serveur MCP « uk.co.ashleypayne/ashley-payne » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 12 outils

• assess_fit≈ 413 tokens

  Compares a description of a project, business or problem against a fixed published rule and returns a verdict: good_fit, mixed, poor_fit or insufficient_information. Wording alone never produces poor_fit. Where the text touches one of the things Ashley turns down, the result lists questions in ask_these_then_call_again, and the three named fields take the person's own answers on a later call. poor_fit needs an explicit yes in one of those fields; good_fit needs an explicit no in all three. Having a development team is not the same as wanting Ashley to supply one.

  Paramètres, retour & exemple (4)

  Paramètres

  • situation · string · requis
    What the person is trying to build or solve, their stage, team and constraints. Free text.
  • wants_a_delivery_team · string · optionnel · yes | no | unsure
    Does the person want Ashley to SUPPLY a team? Leading a team they already have is 'no'.
  • must_start_within_a_week · string · optionnel · yes | no | unsure
    Does the work have to start within a week? Starting within two weeks is the normal target, so that alone is 'no'.
  • wants_spec_built_without_challenge · string · optionnel · yes | no | unsure
    Do they want a finished spec built exactly as written, with no room to challenge it? A complete brief to quote from is 'no'.

  Exemple d'appel

  {"name": "assess_fit", "arguments": {"situation": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_ai_capability≈ 121 tokens

  Which AI techniques he has built in production (prompting, retrieval, fine-tuning, MCP servers, local inference) and when each one is the right choice. Use this for questions about AI, automation or data privacy.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_ai_capability", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_case_study≈ 146 tokens

  Full detail for one engagement: the situation, what was built, the engineering decisions and why they were made, the stack, and where there is one, the commercial outcome in indexed figures.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Case study slug from list_work, e.g. 'coding-education'.

  Exemple d'appel

  {"name": "get_case_study", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_contact≈ 94 tokens

  How to reach Ashley: email, the contact page, and a booking link when one is live. Use when the person wants to make contact.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_contact", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_evidence≈ 163 tokens

  Where the numbers on the site come from, for when someone asks whether they can be trusted. Returns one statement of provenance: the figures are counts from live systems, self-reported with a stated method and not independently audited, and Ashley will run any of them in front of someone who asks. Per-figure detail (the collections, queries and returned values) is not published.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_evidence", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_faqs≈ 118 tokens

  The questions buyers ask, with his answers. Pass a query to get the relevant ones; omit it to list every question without the answers.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · optionnel
    Keywords, e.g. 'price', 'team', 'ill', 'equity'.

  Exemple d'appel

  {"name": "get_faqs", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_insight≈ 126 tokens

  The complete text of one article, by slug. Use after search_insights, and only when the summary is not enough to answer the question.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    The article slug, from search_insights.

  Exemple d'appel

  {"name": "get_insight", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_overview≈ 86 tokens

  Positioning, background and what makes him different from other fractional CTOs. Start here.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_overview", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_privacy≈ 112 tokens

  What this connector and the website do with data, and what they do not. Use this if the person asks about privacy, tracking, cookies, GDPR, or what Ashley can see of this conversation.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_privacy", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_services≈ 161 tokens

  The three ways an engagement runs (Build, Partner, Consult), the fixed-price diagnostic most engagements start with, how the process works, and which client surfaces he builds: desktop applications, browser extensions, chat-platform integrations and web. Use this for any question about platforms, apps, pricing or how an engagement is structured.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_services", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_work≈ 80 tokens

  Summaries of the selected work, with the slug needed for get_case_study.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_work", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_insights≈ 136 tokens

  Search his articles on technical leadership, fractional CTO work, AI and building SaaS. Returns titles, summaries and the matching passage. Call get_insight with a slug for the full text of one.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · optionnel
    Keywords to match against title, summary and body.

  Exemple d'appel

  {"name": "search_insights", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://www.ashleypayne.co.uk/mcp