# The2410 Projects (remote · projects.the2410.com)

Plan custom software with The2410: fit check, budget, timeline, inquiry and consultation booking.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `projects.the2410.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/com-the2410-projects/projects.md), [page](https://verifymcp.io/servers/com-the2410-projects/projects)

## Channel facts

- Endpoint: `https://projects.the2410.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit-project-inquiry-tool).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1768 tokens (~196/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the The2410 Projects MCP server?

The2410 Projects is a hosted endpoint at https://projects.the2410.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-the2410-projects 'https://projects.the2410.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-the2410-projects": {
      "url": "https://projects.the2410.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-the2410-projects": {
      "type": "http",
      "url": "https://projects.the2410.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-the2410-projects]
url = "https://projects.the2410.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-the2410-projects": {
      "type": "remote",
      "url": "https://projects.the2410.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-the2410-projects --url 'https://projects.the2410.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-the2410-projects:
    url: "https://projects.the2410.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-the2410-projects": {
      "Transport": "http",
      "Url": "https://projects.the2410.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-the2410-projects -t streamable-http -u 'https://projects.the2410.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-the2410-projects": {
      "type": "http",
      "url": "https://projects.the2410.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 59, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-13 (score 58)

First indexed and scored.

## MCP tools (9)

### `analyze-request-tool` (~195 tokens)

Analyze request

Evaluates whether The2410 can build the custom software project a customer describes. Use it when a customer describes a new project or request. Returns fit, relevant services or solutions, indicative pricing, a project_context_id and next_actions for the project tools. If the request is only a small task, returns route = small_task and the URL of the separate Human Tasks by The2410 connector. This is not a detailed project plan or a contractual estimate.

Input parameters:

- `budget` (object|null): The customer’s approximate budget range.
- `desired_timeline` (string|null): Desired delivery timeframe, for example "4-6 months".
- `project_context_id` (string|null): Omit for a new project. To continue an existing project, send the exact UUID returned by a previous call.
- `request_description` (string, required): The customer's request as written, in any language: what they need, platform, constraints and main requirements.

### `plan-project-tool` (~256 tokens)

Plan project

Create a preliminary project plan, price range and development effort estimate. Use this tool to understand the main functional modules and important unresolved requirements. Provide an existing project_context_id or a project_description for a new project. Module status describes The2410's proposed solution; confirmed does not mean customer approval. Prices and working days are shares of the existing project estimate. This is a preliminary estimate, not a final specification or contractual offer.The customer's name and email are required; phone and company name are optional.

Input parameters:

- `additional_requirements` (string|null): Updated requirements or answers to planning questions. Replaces the saved additional requirements. Omit to keep them; null clears them.
- `company_name` (string|null): Optional company name. Omit to keep the saved value; null clears it.
- `email` (string, required): The customer's email address.
- `name` (string, required): The customer's full name.
- `phone` (string|null): Optional phone number. Omit to keep the saved value; null clears it.
- `project_context_id` (string|null): Existing project UUID. Required when project_description is omitted.
- `project_description` (string|null): Required for a new project. Omit or send null to reuse the saved description.

### `find_case_studies` (~93 tokens)

Find case studies

Find published The2410 case studies relevant to the customer's current software project. Use this tool when the user wants examples of similar work or relevant project experience. The tool uses the existing project context and returns up to five case studies, ordered by relevance. It does not change the project context, plan, or estimate.

Input parameters:

- `project_context_id` (string, required): The exact project context UUID returned by a previous tool call.

### `check_delivery_window` (~137 tokens)

Check delivery window

Check The2410's indicative delivery availability for the customer's software project. Use this tool when the user wants to know when The2410 could start the project and the approximate delivery window. The tool uses the current project context, estimated business days, and the customer's preferred start. Returned dates are indicative and are not a contractual commitment.

Input parameters:

- `preferred_start` (string|null): For example ASAP, 2026-10, or January 2027. Omit to reuse the stored preference. Send ASAP or null for the earliest available start.
- `project_context_id` (string, required): The exact project context UUID returned by a previous tool call.

### `prepare-project-inquiry-tool` (~167 tokens)

Prepare project inquiry

Prepare a project inquiry for review before submission to The2410. Run plan-project-tool first and provide the existing project_context_id. The customer's name and email are required on every call; company and phone are optional. Return the saved project fit, offering, estimate and modules with their price and effort. Delivery dates are indicative; if not calculated, the response explains how to request them. This tool does not submit the inquiry or send an email.

Input parameters:

- `comments` (string|null): Inquiry comments. Replaces saved comments. Omit to keep them; null clears them.
- `contact` (object, required): Customer contact details. Name and email are required; company and phone are optional.
- `project_context_id` (string, required): The exact project context UUID returned by a previous tool call.

### `submit-project-inquiry-tool` (~171 tokens)

Submit project inquiry

Submit the customer's project inquiry to The2410 by email. Use this tool after the customer has reviewed the inquiry and explicitly asked to submit it. Provide the existing project_context_id and the reviewed contact details. Name and email are required; company and phone are optional. The tool uses the saved analysis and plan, then emails the inquiry to The2410. It does not send an automatic confirmation email to the customer. Do not repeat this call after a successful submission.

Input parameters:

- `comments` (string|null): Inquiry comments. Replaces saved comments. Omit to keep them; null clears them.
- `contact` (object, required): Customer contact details. Name and email are required; company and phone are optional.
- `project_context_id` (string, required): The exact project context UUID returned by a previous tool call.

### `get_consultation_slots` (~181 tokens)

Get consultation slots

Get available consultation times with The2410 for the current software project. Use this tool when the user wants to speak with The2410 or choose a consultation time. The tool retrieves current calendar availability and returns up to ten slots, ordered from earliest to latest, in the requested timezone. This tool does not reserve a slot or create a booking.

Input parameters:

- `date_from` (string|null): First date, YYYY-MM-DD, in the requested timezone. Defaults to today.
- `date_to` (string|null): Last date, inclusive, YYYY-MM-DD. Defaults to six days after date_from. Maximum query span: 31 days.
- `project_context_id` (string, required): The exact project context UUID returned by a previous tool call.
- `timezone` (string|null): IANA timezone, for example Europe/Berlin. Defaults to Europe/Riga.

### `book_consultation` (~173 tokens)

Book consultation

Register a consultation with The2410 by sending an email to the team. Use this tool after the user selects a slot from the latest get_consultation_slots response and confirms that they want to book it. Provide the customer's name and email. The consultation language is English. The team will send the customer a separate confirmation with the meeting details. Do not submit the same booking again after a successful response.

Input parameters:

- `comments` (string|null): Optional comments or topics to discuss during the consultation.
- `email` (string, required): The customer’s email address.
- `name` (string, required): The customer’s full name.
- `project_context_id` (string, required): The exact project context UUID returned by a previous tool call.
- `slot_id` (string, required): The selected slot_id from the latest get_consultation_slots response.

### `send-feedback-tool` (~219 tokens)

Send feedback

Send feedback to The2410 team: a problem, a suggestion, praise or any other message about this MCP server, an order or a project. Use only when the customer wants to share feedback. Show the message to the customer and send it after they confirm. Name and email are optional; include them if the customer wants a reply. If the feedback is about a specific project or order, add the project_context_id or order_id returned by an earlier call. Never include passwords, access details or payment card data.

Input parameters:

- `email` (string): Optional customer email, if the customer wants a reply.
- `message` (string, required): The feedback text, in the customer's words.
- `name` (string): Optional customer name.
- `order_id` (string): Optional order id of a fixed-price service order, e.g. ord_8f3k2m9qxa.
- `project_context_id` (string): Optional project context UUID returned by a previous tool call.
- `type` (string): Feedback type. Default: other.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-the2410-projects/projects#diagnostics

## Score history

- 2026-10-18: 61
- 2026-10-17: 60
- 2026-10-16: 60
- 2026-10-15: 59
- 2026-10-14: 59
- 2026-10-13: 58

## Common questions

### What is the The2410 Projects MCP server?

The2410 Projects is an MCP server listed in the public MCP registry as com.the2410/projects. Plan custom software with The2410: fit check, budget, timeline, inquiry and consultation booking. This page covers its hosted endpoint (https://projects.the2410.com/mcp).

### Is the The2410 Projects MCP server safe to use?

The2410 Projects scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the The2410 Projects MCP server expose?

The2410 Projects exposes 9 tools: analyze-request-tool, plan-project-tool, find_case_studies, check_delivery_window, prepare-project-inquiry-tool, and 4 more. Their descriptions and schemas cost roughly 1,592 tokens of context every time the server is loaded.

### Does the The2410 Projects MCP server require authentication?

No. We connected to The2410 Projects without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the The2410 Projects MCP server still maintained?

The2410 Projects is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://projects.the2410.com/mcp
- Website: https://projects.the2410.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-the2410-projects/projects.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-the2410-projects/projects.json
- HTML version of this page: https://verifymcp.io/servers/com-the2410-projects/projects