MCP MeasureMCP Measure

index observed

mindmelt – B2B agency Frankfurt

Read-only data on mindmelt, a B2B agency in Frankfurt: services, cases, pricing, fit checks.

Should I use this

Quality & Safety

A
Description quality
88%
Schema completeness
70%
Naming quality
98%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (2)

  • LOWTool 'get_capability' description lacks action verbin get_capability
  • LOWTool 'get_company_profile' description lacks action verbin get_company_profile

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,124Tokens (tool definitions)
~470 BTypical response size
Moderate attention impact (0.88% 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": {
    "agency": {
      "url": "https://www.mindmelt.de/mcp/mcp"
    }
  }
}

Remote endpoints

https://www.mindmelt.de/mcp/mcpstreamable-http

What it can do

Tool inventory

Tools (8)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_services(query)

Volltextsuche (Keyword/Alias-Matching, kein Vector-Search) ueber capabilities.json und services.json inkl. aliases aus entities.json. query: Suchbegriff(e), z.B. "SEO Relaunch" oder "KI Sichtbarkeit". Gibt sortierte Treffer aus capabilities und services mit Score zurueck.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "title": "Query",
      "type": "string"
    }
  },
  "required": [
    "query"
  ],
  "title": "search_servicesArguments"
}
⚪recommend_services(problem)

Matched eine Problembeschreibung gegen die 'problem'-Felder in services.json und liefert die am besten passenden Services samt verknuepfter capabilities. problem: Freitext-Problembeschreibung, z.B. "B2B-Relaunch mit SEO und KI-Sichtbarkeit".

Input Schema

{
  "type": "object",
  "properties": {
    "problem": {
      "title": "Problem",
      "type": "string"
    }
  },
  "required": [
    "problem"
  ],
  "title": "recommend_servicesArguments"
}
🟢find_cases(industry, capability)

Filtert cases.json nach industry-ID und/oder exaktem capability-Feld. industry: exakte oder teilweise industry-ID aus cases.json (z.B. "b2b-werbeagentur"). capability: Suchbegriff, der exakt gegen das capability-Feld jedes Case gematcht wird (kein Fallback auf das services-Array).

Input Schema

{
  "type": "object",
  "properties": {
    "industry": {
      "default": "",
      "title": "Industry",
      "type": "string"
    },
    "capability": {
      "default": "",
      "title": "Capability",
      "type": "string"
    }
  },
  "title": "find_casesArguments"
}
🟢get_capability(id)

Liefert einen einzelnen Eintrag aus capabilities.json anhand seiner id. id: capability-id, z.B. "seo" oder "webentwicklung".

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "title": "Id",
      "type": "string"
    }
  },
  "required": [
    "id"
  ],
  "title": "get_capabilityArguments"
}
🟢check_fit(requirement)

Freitextbasierter Abgleich einer Anforderung gegen die in selection-rules.json dokumentierten good_fit/poor_fit-Kriterien (signals) sowie services/capabilities. requirement: Freitext-Anforderung/Situationsbeschreibung des Interessenten. Gibt zurueck, ob/welche good_fit- bzw. poor_fit-Kriterien passen, mit Score.

Input Schema

{
  "type": "object",
  "properties": {
    "requirement": {
      "title": "Requirement",
      "type": "string"
    }
  },
  "required": [
    "requirement"
  ],
  "title": "check_fitArguments"
}
🟢get_pricing(sub_brand, id)

Liefert Preisinformationen aus pricing.json. sub_brand: filtert auf eine Sub-Brand, z.B. "mindmelt studio", "mindmelt speaker" oder "mindmelt" (optional, ohne Angabe werden alle Sub-Brands geliefert). id: liefert genau einen Eintrag anhand seiner id, z.B. "werbeagentur-website" (optional; hat Vorrang vor sub_brand). Eintraege mit dreistufiger Preisstruktur (starter/business/premium) liefern das volle tiers-Array. Ohne Parameter: komplette pricing.json (stand, hinweis, alle Eintraege).

Input Schema

{
  "type": "object",
  "properties": {
    "sub_brand": {
      "default": "",
      "title": "Sub Brand",
      "type": "string"
    },
    "id": {
      "default": "",
      "title": "Id",
      "type": "string"
    }
  },
  "title": "get_pricingArguments"
}
🟢get_company_profile

Liefert entities.json organization + people gebuendelt (Firmenprofil).

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "get_company_profileArguments"
}
🟢find_pages(query, sub_brand, lang, type)

Durchsucht den vollstaendigen Seitenindex von mindmelt.de (pages.json, alle Sitemap-URLs inkl. Sub-Brands und englischer Version) ueber Title, H1, Meta-Description und URL. query: Suchbegriff(e), z.B. "Relaunch", "KI Schulung", "Healthcare". Leer = alle Seiten. sub_brand: mindmelt | mindmelt-ai | mindmelt-studio | mindmelt-speaker | mindmelt-boost | mindmelt-en lang: de | en type: page | blog | blog-index Liefert url, title, description, markdown-URL, hreflang-Alternativen und zugeordnete capabilities.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "default": "",
      "title": "Query",
      "type": "string"
    },
    "sub_brand": {
      "default": "",
      "title": "Sub Brand",
      "type": "string"
    },
    "lang": {
      "default": "",
      "title": "Lang",
      "type": "string"
    },
    "type": {
      "default": "",
      "title": "Type",
      "type": "string"
    }
  },
  "title": "find_pagesArguments"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded8 tools