General Tools

answered.work

Provides information about Answered Work's services, pricing, and FAQs, and allows users to submit inquiries to contact the company.

2 endpoints2 known tools

ENDPOINT 1

https://answered.work/mcp

No auth detected

MCP server metadata

Name: work.answered/site
Version: 1.0.0

Capabilities

tools

Server instructions

Answered Work: Answered Work is an AI development and consulting firm for any business looking for efficiency. Our forward-deployed engineers find where AI fits, build it into your systems, and keep it running as your managed service provider. Use get_info to answer questions about what we do and how we work. Use submit_inquiry only when the person has asked you to contact us for them. Only send an inquiry when the person has asked you to contact Answered Work for them. Use their real name and email: they get a confirmation email and a reply from a person within one business day. Don't invent details; leave optional fields out if you don't know them. Don't send a phone number or agree to calls or texts for the person: only they can give that consent, on the form at /intake. If the person is already an Answered Work client and wants you to work with their portal, have them connect https://answered.work/mcp/portal instead; it signs in with their portal account.

Known tools 2

get_info

What Answered Work does, who it's for, the ways to work with us (forward-deployed engineering, managed services, custom projects), how it works, our prices and what setup looks like (topic "pricing"), our promises, answers to common questions (topic "faq"), and how to get in touch.

Inferred read-only

submit_inquiry

Start a conversation with Answered Work for a person, the same as filling in the form at https://answered.work/intake.

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.work-answered-site]
url = "https://answered.work/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "work-answered-site": {
      "type": "http",
      "url": "https://answered.work/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: work-answered-site
Remote MCP URL: https://answered.work/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": {
    "work-answered-site": {
      "url": "https://answered.work/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "work-answered-site": {
      "type": "http",
      "url": "https://answered.work/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "work-answered-site",
  "transport": "streamable-http",
  "url": "https://answered.work/mcp"
}

MCP Inspector

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

ENDPOINT 2

https://answered.work/mcp/portal

Auth required

Known tools 0

No tool metadata was available in the registry cache.

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.answered-work]
url = "https://answered.work/mcp/portal"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Code

.mcp.json

{
  "mcpServers": {
    "answered-work": {
      "type": "http",
      "url": "https://answered.work/mcp/portal",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Desktop

Settings → Connectors → Add custom connector

Name: answered-work
Remote MCP URL: https://answered.work/mcp/portal

Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "answered-work": {
      "url": "https://answered.work/mcp/portal",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Visual Studio Code

.vscode/mcp.json

{
  "servers": {
    "answered-work": {
      "type": "http",
      "url": "https://answered.work/mcp/portal",
      "headers": {
        "Authorization": "Bearer ${input:mcp-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "mcp-token",
      "description": "answered-work bearer token",
      "password": true
    }
  ]
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Generic MCP

Client-specific MCP configuration

{
  "name": "answered-work",
  "transport": "streamable-http",
  "url": "https://answered.work/mcp/portal",
  "headers": {
    "Authorization": "Bearer YOUR_BEARER_TOKEN"
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

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.