Productivity

scull7.com

An MCP server for a recruiter-agent workflow that starts interview sessions, answers questions from published facts, sends verification emails, creates calendar holds, and returns resume facts.

1 endpoint5 known toolsFirst detected September 10, 2026Last detected September 10, 2026

ENDPOINT 1

https://scull7.com/mcp

No auth detected

MCP server metadata

Name: interview-me
Version: 1.0.0

Capabilities

tools

Known tools 5

start_interview

Start a named recruiter-agent session (company, role, recruiter name, work email).

Potential side effects

ask_nathan

Ask a question against published facts.

Inferred read-only

request_verification

Send a magic-link email to the session work email.

Potential side effects

create_hold

Create a tentative calendar hold.

Potential side effects

get_resume

Return published resume facts from the same corpus as cited answers.

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.interview-me]
url = "https://scull7.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "interview-me": {
      "type": "http",
      "url": "https://scull7.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: interview-me
Remote MCP URL: https://scull7.com/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": {
    "interview-me": {
      "url": "https://scull7.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "interview-me": {
      "type": "http",
      "url": "https://scull7.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "interview-me",
  "transport": "streamable-http",
  "url": "https://scull7.com/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.