Content Tools

dfmsolutions.de

MCP server that exposes DFM Solutions website structure, services, and blog posts for browsing and retrieval.

1 endpoint11 known toolsFirst detected October 22, 2026Last detected October 22, 2026

ENDPOINT 1

https://dfmsolutions.de/api/mcp

No auth detected

MCP server metadata

Name: dfm-solutions
Version: 1.0.0

Capabilities

toolsresources

Server instructions

Tools for dfmsolutions.de (German digital agency, Oberhausen). Start with site_map to see the structure, then search_content or the specific getters. Answer in the user's language; prices are indicative until DFM confirms them. Call submit_contact_request only when the user has asked to be contacted and supplied their own name, e-mail and enquiry.

Known tools 11

site_map

Structure of dfmsolutions.de: navigation, static pages, the commercial landing pages, the location pages, service pages, blog categories and the machine-readable endpoints.

Inferred read-only

list_services

All published DFM Solutions services with tagline, tech stack and price entry point.

Inferred read-only

get_service

Full detail of one service: deliverables, process, pricing tiers, metrics and service-specific FAQ.

Inferred read-only

list_blog_posts

Published articles, newest first.

Inferred read-only

get_blog_post

One published article including its full body as markdown.

Inferred read-only

search_content

Keyword search across services, blog posts, FAQ answers and glossary terms.

Inferred read-only

get_faq

Published FAQ entries, optionally filtered by category.

Inferred read-only

get_pricing

Price tiers per service.

Inferred read-only

list_references

Published project references with sector and measured result.

Inferred read-only

get_company_info

Legal and contact details of DFM Solutions (Impressum data).

Inferred read-only

submit_contact_request

Send a project or support enquiry to DFM Solutions.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.dfm-solutions]
url = "https://dfmsolutions.de/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "dfm-solutions": {
      "type": "http",
      "url": "https://dfmsolutions.de/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dfm-solutions
Remote MCP URL: https://dfmsolutions.de/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "dfm-solutions": {
      "url": "https://dfmsolutions.de/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dfm-solutions": {
      "type": "http",
      "url": "https://dfmsolutions.de/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dfm-solutions",
  "transport": "streamable-http",
  "url": "https://dfmsolutions.de/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.