The2410 Projects
REMOTE · PROJECTS.THE2410.COM
Plan custom software with The2410: fit check, budget, timeline, inquiry and consultation booking.
Available components
Last scanned (9 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit-project-inquiry-tool). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +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.
- 16 Oct 26 +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.
- 14 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 58
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://projects.the2410.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=the2410.com | CN=WE1,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | a1aa91854bb4d9ef0e907ac9f996f86b |
| SANs: the2410.com, *.the2410.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of projects.the2410.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| the2410.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://projects.the2410.com/mcp | Verified | 200 | |
| http (plaintext) | http://projects.the2410.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze-request-tool Analyze request ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The customer's request as written, in any language: what they need, platform, constraints and main requirements. |
No output schema declared.
No examples provided.
book_consultation Book consultation ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| comments | string|null | – | Optional comments or topics to discuss during the consultation. |
| string | yes | The customer’s email address. | |
| name | string | yes | The customer’s full name. |
| project_context_id | string | yes | The exact project context UUID returned by a previous tool call. |
| slot_id | string | yes | The selected slot_id from the latest get_consultation_slots response. |
No output schema declared.
No examples provided.
check_delivery_window Check delivery window ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The exact project context UUID returned by a previous tool call. |
No output schema declared.
No examples provided.
find_case_studies Find case studies ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_context_id | string | yes | The exact project context UUID returned by a previous tool call. |
No output schema declared.
No examples provided.
get_consultation_slots Get consultation slots ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The exact project context UUID returned by a previous tool call. |
| timezone | string|null | – | IANA timezone, for example Europe/Berlin. Defaults to Europe/Riga. |
No output schema declared.
No examples provided.
plan-project-tool Plan project ~256
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| string | yes | The customer's email address. | |
| name | string | yes | 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. |
No output schema declared.
No examples provided.
prepare-project-inquiry-tool Prepare project inquiry ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| comments | string|null | – | Inquiry comments. Replaces saved comments. Omit to keep them; null clears them. |
| contact | object | yes | Customer contact details. Name and email are required; company and phone are optional. |
| project_context_id | string | yes | The exact project context UUID returned by a previous tool call. |
No output schema declared.
No examples provided.
send-feedback-tool Send feedback ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Optional customer email, if the customer wants a reply. | |
| message | string | yes | 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. |
No output schema declared.
No examples provided.
submit-project-inquiry-tool Submit project inquiry ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| comments | string|null | – | Inquiry comments. Replaces saved comments. Omit to keep them; null clears them. |
| contact | object | yes | Customer contact details. Name and email are required; company and phone are optional. |
| project_context_id | string | yes | The exact project context UUID returned by a previous tool call. |
No output schema declared.
No examples provided.
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.
remote · projects.the2410.com
claude mcp add --transport http com-the2410-projects 'https://projects.the2410.com/mcp'
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.