Learning Resources

tmk.ai

Facilitates engagement with Tinman Kinetics for questions, workshops, and conversations about AI education and advisory services.

1 endpoint3 known toolsFirst detected August 4, 2026Last detected August 4, 2026

ENDPOINT 1

https://tmk.ai/mcp

No auth detected

MCP server metadata

Name: tinman-contact
Version: 1.0.0

Capabilities

tools

Server instructions

Non-agentive contact tools for the Tinman Kinetics team. Each tool requires a name and a reply-to email; a human replies by email. Site content for grounding: https://tmk.ai/llms.txt

Known tools 3

ask_a_question

Ask the Tinman Kinetics team a question.

Inferred read-only

request_a_workshop

Request a Tinman Kinetics workshop or team training on practical, human-first AI.

Inferred read-only

request_a_conversation

Request a conversation with the Tinman Kinetics team about advisory, education, or bespoke software.

Inferred read-only

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.tinman-contact]
url = "https://tmk.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "tinman-contact": {
      "type": "http",
      "url": "https://tmk.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: tinman-contact
Remote MCP URL: https://tmk.ai/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": {
    "tinman-contact": {
      "url": "https://tmk.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "tinman-contact": {
      "type": "http",
      "url": "https://tmk.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "tinman-contact",
  "transport": "streamable-http",
  "url": "https://tmk.ai/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.